Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [jwt-dev] Changing toolbar for BPMN

Hi Pierre,

if you just want to replace the labels/icons of the model elements in the
JWT-palette, there is a planned enhancement of the view extension point that
will provide an easy interface to change the palette entries by giving
alternative labels/icons for meta model elements like Action or
DecisionNode.
In order make modifications of the implemented behavior possible, Marc is
currently working on a feature that will allow to extend meta model classes
with custom aspects.

Regards,
Chris

-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Pierre Vigneras
Gesendet: Donnerstag, 4. September 2008 16:42
An: 'Java Workflow Toolbox'
Betreff: [jwt-dev] Changing toolbar for BPMN

Dear all,

I would like to change the toolbar of JWT in order to provide BPMN icons and
concepts.
I have some questions about where to start from (considering the big number
of JWT Eclipse sub-projects,
and their relevant packages). I suppose that the good place to start with is
the jwt.we package.

There, I found the Palette class where the following code :

addPaletteDrawer(activityGroup, ProcessesPackage.Literals.ACTION);
		addPaletteDrawer(activityGroup,
ProcessesPackage.Literals.INITIAL_NODE);
		addPaletteDrawer(activityGroup,
ProcessesPackage.Literals.FINAL_NODE);
		addPaletteDrawer(activityGroup,
EventsPackage.Literals.EVENT);
		addPaletteDrawer(activityGroup,
ProcessesPackage.Literals.FORK_NODE);
		addPaletteDrawer(activityGroup,
ProcessesPackage.Literals.JOIN_NODE);
		addPaletteDrawer(activityGroup,
ProcessesPackage.Literals.DECISION_NODE);
		addPaletteDrawer(activityGroup,
ProcessesPackage.Literals.MERGE_NODE);
		addPaletteDrawer(activityGroup,
ProcessesPackage.Literals.GUARD);

Brings me to the EMF components : ProcessesPackage.Literals interface. My
question is: if we want to modify 
not only the icon (UML to BPMN) but also the behavior (for example: a node
(task) can have multiple incoming/outgoing edges (transitions)) 
how can we implement that behavior? Should we use inheritance, or is there a
standard (EMF) way of extending (means not only adding things, but
also modify/speciale existing things) the JWT model?

Thanks for your help.

-- 
Pierre Vignéras
Bull, Architect of an Open World TM
*BPM Team*, Bull R&D
1, rue de Provence
38130 Echirolles (France)
Direct Line: +33-4-76-29-74-06

*Orchestra*, The BPEL open source project: http://orchestra.ow2.org
*Bonita*, The XPDL open source project: http://bonita.ow2.org
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev




Back to the top