here's what i would do:
create 1 language that is embedded in the process definition xml.
but design your language in such a way that the amount of information inside the nodes or
other elements is limited. if more information is required, refer to something that is
defined in the process definition level. similarly to e.g. swimlanes.
then you can still define a kind of import of a process archive resource so that most of
the big complex building blocks of the simulation information are potentially defined in
an external file, but that the link between those externally defined entities and the
process definition elements is right inside elements in the processdefinition.xml
makes sense ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092450#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...