Eclipse Community Forums: Papyrus for Real Time » setting * as the message of the trigger does not work properly (v0.9)

Home » Eclipse Projects » Papyrus for Real Time » setting * as the message of the trigger does not work properly (v0.9)(setting * as the message of the trigger does not work properly (v0.9))

Show: Today's Messages :: Show Polls :: Message Navigator

setting * as the message of the trigger does not work properly (v0.9) [message #1763922]

Tue, 23 May 2017 03:34

Mojtaba Bagherzadeh

Messages: 36
Registered: April 2016

Member

Hi,
In the previous version of PapyrusRT, I could set * as the message of a trigger, and it worked correctly (i.e., The transition is taken on every message of the related protocol ).
I version 0.9, when I set * for the message, it consumes the incoming message, but the transition is not taken.

The bug easily can be reproduced using a timer and setting the trigger of a specific transition to * which show in the following figure.

index.php/fa/29428/0/

Thanks
Mojtaba

Attachment: Screen Shot 2017-05-22 at 23.32.36.png
(Size: 32.82KB, Downloaded 287 times)

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1763940 is a reply to message #1763922]

Tue, 23 May 2017 08:55

Peter Cigehn

Messages: 49
Registered: September 2014

Member

Hi,

I can confirm that this does no longer work as expected. I wrote bug 517116 to track this issue.

/Peter Cigéhn

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1763966 is a reply to message #1763940]

Tue, 23 May 2017 12:54

Mojtaba Bagherzadeh

Messages: 36
Registered: April 2016

Member

Thanks a lot.

Mojtaba

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1763977 is a reply to message #1763966]

Tue, 23 May 2017 14:27

Ernesto Posse

Messages: 380
Registered: March 2011

Senior Member

Does this happen with any port or just Timing ports?

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1763992 is a reply to message #1763977]

Tue, 23 May 2017 17:48

Mojtaba Bagherzadeh

Messages: 36
Registered: April 2016

Member

It happens with any port.

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1763994 is a reply to message #1763992]

Tue, 23 May 2017 17:55

Ernesto Posse

Messages: 380
Registered: March 2011

Senior Member

I've merged a fix. It should be available in the nightly update site in around half an hour.

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1765148 is a reply to message #1763994]

Wed, 07 June 2017 05:31

Mojtaba Bagherzadeh

Messages: 36
Registered: April 2016

Member

Is this fix available in the test version? I updated my test version but the issue is not resolved, here is my version:
index.php/fa/29575/0/

How can I get this fix on test or user version?

Attachment: Screen Shot 2017-06-07 at 01.26.39.png
(Size: 118.67KB, Downloaded 268 times)

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1765205 is a reply to message #1765148]

Wed, 07 June 2017 14:04

Ernesto Posse

Messages: 380
Registered: March 2011

Senior Member

It looks you do not have the latest nightly in your environment. The bundles show version 0.9.0.20170502nnnn. The 20170502 is the date of that build: 2017-May-02, and as my response, where I indicated that the fix was merged is from May 23, then that change is not in your environment.

To confirm, I have just installed a fresh tester environment, ran a test and it generates code correctly for the * event.

If you created the tester environment with "nightly" as the build type, you can run "Help->Perform Setup Tasks...->[Finish]" to ensure that you get the latest updates from the nightly update site (and dependencies).

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1765211 is a reply to message #1765205]

Wed, 07 June 2017 14:50

Mojtaba Bagherzadeh

Messages: 36
Registered: April 2016

Member

I have updated my tester version again, but it does not get the new version. My Eclipse is Neon3, Is this update available for Eclipse Neon as well?
I can not update my Eclipse to Oxygen because I have some plugins that are not compatible with that.

As you can see, My Eclipsed updated recently, but I do not see the last version.
index.php/fa/29584/0/

Attachment: Screen Shot 2017-06-07 at 10.44.07.png
(Size: 152.54KB, Downloaded 256 times)

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1765217 is a reply to message #1765211]

Wed, 07 June 2017 15:19

Ernesto Posse

Messages: 380
Registered: March 2011

Senior Member

How exactly are you updating? With Help->Perform Setup Tasks? Manually with Help->Check for updates? With the Eclipse Installer? Some other way?

As for Neon v. Oxygen, sorry but we will no longer support Neon. We have moved to Oxygen which is the target for 1.0, and this particular fix was merged after we moved to Oxygen.

What are the plugins/features which are not compatible with Oxygen? If these are from products in the release train, you could probably find milestone update sites for their Oxygen release.

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1765221 is a reply to message #1765217]

Wed, 07 June 2017 15:53

Mojtaba Bagherzadeh

Messages: 36
Registered: April 2016

Member

I used "Perform Setup Tasks", but my version is Neon and I think this is the main issue, I will try the Oxygen to see if it fix the issue.

We are using the Epsilon to perform some transformation and based on previous experiments we had some issues with Oxygen even with their Epsilon last version.
Anyway, It seems that we do not have any choice and we have to use Oxygen for Epsilon as well.

Thanks for the help and support.

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1765227 is a reply to message #1765221]

Wed, 07 June 2017 16:26

Ernesto Posse

Messages: 380
Registered: March 2011

Senior Member

I'm not sure if Epsilon is in the Eclipse simrel, but they do build on Eclipse servers and have an "interim" update site (http://download.eclipse.org/epsilon/interim/) where they seem to publish bug fixes. Perhaps this includes migration to Oxygen. You could ask in their forum/mailing list if they are releasing Epsilon for Oxygen and if they can get it from that interim update site or somewhere else.

Report message to a moderator

Re: setting * as the message of the trigger does not work properly (v0.9) [message #1765236 is a reply to message #1765227]

Wed, 07 June 2017 17:53

Mojtaba Bagherzadeh

Messages: 36
Registered: April 2016

Member

Thanks a lot, We have tested and the Eclipse Oxygen works fine with (new fix and Epsilon).

Report message to a moderator

Previous Topic:	Define a trigger which its signal is set to all incoming messages
Next Topic:	Not able to create Plug-in Project in Papyrus-RT Tester version

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon May 27 05:03:30 GMT 2019

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter