> I like to think that the job AndroMDA does is akin an engine that aplies > aspects to a UML model. > Don't know though how to explore this concept further. Maybe in future > versions AndroMDA, which today > is stereotype-driven, could explore the metamodel, so one would be able > to trigger code generation from > a metadata expression. > [WZ> ] Actually, we are currently working on metafacade property mapping, there's still a bug Chad is fixing, hopefully this weekend it will be done .. it would mean no more <<FrontEndController>>, <<FrontEndEvent>> and <<Role>> stereotypes in bpm4struts :-) .. for other cartridges development will be simpled too
I'm with you .. I personally am not keen about those stereotypes, I prefer to have the model imply them where possible I invite you (and anyone interested) to post any ideas on our new wiki :-) just create a new page under the 'USER' space http://team.andromda.org/confluence (soon to be http://confluence.andromda.org but the DNS has not been propagated yet) -- Wouter ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
