| BPEL Annotations/Extensions [message #6604] |
Tue, 16 January 2007 13:12  |
Eclipse User |
|
|
|
Originally posted by: osterloh.offis.de
Hi!
We would like to extend the given BPEL Elements with annotations (as new
childs for the elements) e.g.:
<wait name="Wait_1">
<annotation>
<it5:expectation name="waitrate">
<ms>4</ms>
</it5:expectation>
</annotation>
</wait>
Where "it5" is our own namespace.
These annotations should be editable in the Properties view of each
element (the annotations may vary from activity to activity, e.g. a
switch has other annotations then a wait).
Can someone here explain how we can achieve this? What's the best way to
get this functionality, without changing your plugin? For compatibility
purposes, we would prefer a solution where we mustn't change your
plugin, but unfortunatly we weren't able to identify how to use the
extension mechanism of your plugin.
How do we model our extensions? With our own ecore model, where we use
your model as base (MyTWait extends TWait). Or do we only model our
extensions as ecore objects? In case one: How is ensured, that if the
user chooses an activity from the palette, that our extended class is
used? In case two: How are the two models integrated, so that our
extensions are properly (de-/)serialized?
I hope you can help us :-)
Bye
Jan-Patrick Osterloh
|
|
|
| Re: BPEL Annotations/Extensions [message #6624 is a reply to message #6604] |
Thu, 18 January 2007 20:17  |
 Michal Chmielewski
Messages: 58
Registered: July 2009 |
Member |
|
|
Jan,
I think you might be off on the syntax a bit, it probably should be
<wait name="Wait_1">
<it5:expectation name="waitrate">
<it:5ms>4</it5:ms>
</it5:expectation>
</wait>
Regardless, the only extensibility element mechanism that we support
currently is the 'extensibleActivity' mechanism. There is nothing in the
code that would make this work magically right now.
However, it would be valid BPEL code and the tool probably at some point
ought to be able to work with it in some way.
I've cc'ed the dev list and see what happens.
-michal
Jan-Patrick Osterloh wrote:
> Hi!
>
> We would like to extend the given BPEL Elements with annotations (as new
> childs for the elements) e.g.:
> <wait name="Wait_1">
> <annotation>
> <it5:expectation name="waitrate">
> <ms>4</ms>
> </it5:expectation>
> </annotation>
> </wait>
> Where "it5" is our own namespace.
>
> These annotations should be editable in the Properties view of each
> element (the annotations may vary from activity to activity, e.g. a
> switch has other annotations then a wait).
>
> Can someone here explain how we can achieve this? What's the best way to
> get this functionality, without changing your plugin? For compatibility
> purposes, we would prefer a solution where we mustn't change your
> plugin, but unfortunatly we weren't able to identify how to use the
> extension mechanism of your plugin.
>
> How do we model our extensions? With our own ecore model, where we use
> your model as base (MyTWait extends TWait). Or do we only model our
> extensions as ecore objects? In case one: How is ensured, that if the
> user chooses an activity from the palette, that our extended class is
> used? In case two: How are the two models integrated, so that our
> extensions are properly (de-/)serialized?
>
> I hope you can help us :-)
>
> Bye
> Jan-Patrick Osterloh
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02996 seconds
] 
Search
Help
Register
Login
Home
