Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364017

Summary:

private Messages

Product:

[Modeling] eTrice

Reporter:

Thomas Jung <tj>

Component:

Core

Assignee:

Project Inbox <etrice.core-inbox>

Status:

CLOSED FIXED

QA Contact:

Severity:

enhancement

Priority:

CC:

hrr

Version:

0.1.0

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

0.2.0M1

Attachments:

Description	Flags
A logging service to demonstrate the need	none

Description Thomas Jung

2011-11-17 06:58:56 EST

it would be handy to have a private message definition in a protocol. On the sender side this message is visible just in the port context (e.g. hook funktion)not in the actor context. This feature would enhance the usage of port hooks and it would be possible to hide messages from the user.

Comment 1 Henrik Rentz-Reichert

2011-11-17 07:07:46 EST

The hook is free to omit delivering to the event receiver.
I think this is sufficient to implement the desired behavior, right?

Comment 2 Thomas Jung

2011-11-17 10:53:37 EST

The behavior can be implemented but it is not very consistent that the message is available for the sender (it will be shown in the message drop down list as well as in the java autocompletion) but will never be sent due to the hook.
In addition, to implement filters and put this filters to operations it would be creat to put port operations to the message list instead of "private" messages. I will attach an example to the bug. A logging Service that implements a filter for the log level.
(In reply to comment #1)
> The hook is free to omit delivering to the event receiver.
> I think this is sufficient to implement the desired behavior, right?

Comment 3 Thomas Jung

2011-11-17 10:58:42 EST

Created attachment 207152 [details]
A logging service to demonstrate the need

Using this Service it would be nice to use the "log" operation the same way as a normal message. But it must be an operation due to the fact that filtering must take place on the sender context. The user should not care about this. On the other hand the "internalLog" message is visible to the user but should never be used due to the missing filter functionality.

Comment 4 Henrik Rentz-Reichert

2012-01-12 12:08:38 EST

Implemented a solution with private Messages and Operations in PortClasses that can send messages (of course also private ones).

This is done with
8401c69d38c05bf1ed5a51f6aac790b1098eadd8

Comment 5 Henrik Rentz-Reichert

2012-03-28 05:12:56 EDT

closing bugs that went into 0.2.0M1