ok. i'm convinced that maintaining the graph info in a separate file is better.
but we only today realized what problems this implies for the designer. when you cut and paste a few nodes in the source view, it's a hell of a job to sync that up in the graphical info view.
but koen will solve that... right koen ? :-)
regards, tom.
Of course I will... ;-)
Regards,
Koen
:-)
"gavin.king@jboss.com" wrote:
I think the current CVS rev of GPD that I have been playing with does it Just Perfect by using:
foo.jpdl.xml
.gpd.foo.jpdl.xml
bar.jpdl.xml
.gpd.bar.jpdl.xml
This is just like the old convention for laying out Hibernate mapping documents next to the mapped classes. It's a good way.
- processdefinition.xml - gpd.xml - forms.xml (coupling between task names in the processdefinition.xml and the form files) - 1 form for each task - deployment.xml - processimage.jpg - ...