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 ;)

The XML profile file with CONVERSATION as default value for @andromda.seam.component.scope tagged value instead of SESSION

Make sure you took the profile from http://jira.andromda.org/browse/EJB-63, which I still havn't applied.

It's not a big change anyway, so after the profile in EJB-63 is applied, we can manually add this fix.

fixed in cvs