[ http://jira.andromda.org/browse/EJB-76?page=comments#action_14750 ]
Olivier THIERRY commented on EJB-76: ------------------------------------ The problem comes from a different default value in the EJB3 cartridge and the Seam profile for the @andromda.seam.component.scope tagged value. It is CONVERSATION in the cartridge, while it is SESSION in the UML profile. Then it looks like AndroMDA has as particular behaviour with default value on EMF/UML2 export : when you select the default value for a tagged value, it doesn't export the value ! I think it would be better to export the default value if you set no value for the tagged value, but that's not the way AndroMDA works. So when you select SESSION for @andromda.seam.component.scope, it exports nothing since SESSION is the default value, and so EJB3 cartridge understands it as CONVERSATION since it applies default value if there is no scope defined for a Seam component in UML model ... So, to solve the problem, the default value in the UML profile should be CONVERSATION, not SESSION. I changed it manually in the XML profile file and it works perfect now. I think the profile is generated from an UML metamodel, but I don't know where this metamodel is and how to correct the default value. Anyone has an idea about it ? I will attach the right XML profile file to this JIRA issue ;) > Seam component scope in the model ignored on generation > ------------------------------------------------------- > > Key: EJB-76 > URL: http://jira.andromda.org/browse/EJB-76 > Project: EJB Cartridge > Type: Bug > Environment: Magic Draw 12.1, EMF / UML2 export > Andromda 3.3-SNAPSHOT > EJB3 cartridge > Reporter: Olivier THIERRY > Assignee: Vance Karimi > Priority: Critical > > When you set SESSION as scope for a Seam component in the UML model, it is > ignored on generation : the components are always in CONVERSATION scope. > See this topic on the forum : > http://galaxy.andromda.org/forum/viewtopic.php?t=4974 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.andromda.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
