would it be possible to attach a patch to this issue ? the dummy implementation is supposed to be replaced by a manual implementation, I have too many higher priorities on my todo list so any help would be appreciated, thanks!

OK, I will try in a few days (I have never tried to modify a cartridge before :) ).

there is documentation regarding this kind of stuff, basically you would just need to use the cartridge but override one or more templates, see this documentation: http://docs.andromda.org/andromda-cartridges/index.html#mergeLocation

to learn what properties you can call on the Velocity variables see these JavaDocs:
(generic: http://galaxy.andromda.org/docs/andromda-metafacades-uml/apidocs/index.html)
(bpm4struts: http://galaxy.andromda.org/docs/andromda-bpm4struts-cartridge/apidocs/index.html)

for example, if you see $action in a bpm4struts template it's most likely an instance of StrutsAction (http://galaxy.andromda.org/docs/andromda-bpm4struts-cartridge/apidocs/org/andromda/cartridges/bpm4struts/metafacades/StrutsAction.html)

good luck! (btw, you'll see it's actually fun to play ith a cartridge like that)

hi Igor,

I'm afraid that detecting all possible cases of value objects would be a bit overkill here .. IMO it's okay to have the generate webapp code not compile in the implementation (you can always safely edit this file), the feature of having the fully deployable webapp is a nice extra for when you want to give a quick demo, but using it on applications that would go into production is bit much I think

handling all possible cases of collections/arrays would overly complicate the template(s)

for that reason I'm closing this issue .. please comment if you disagree or if you think there's a practical solution to this problem