[Panagiotis Korros]

There is very important bug in 4.0 GA regarding the exploded deployment of ejb projects with many dots in the name that made me to return to the 4.0M2.

I have an EJB Project named: test.ejb and it is part of an ear project named testear.
When I deploy the project to jboss the deployed structure is:

testear.ear
META-INF
test.ejb
META-INF

etc.

and the jboss application server can’t deploy this structure.

using the same project the deployed structure using ME4.0M2 is:
testear.ear
META-INF
test.ejb.jar
META-INF

and the jboss application server successfully deploys this structure.

[Riyad Kalla]

pkorros,
Strangely enough this is the intended behavior, to support custom module-extension deployment in MyEclipse we added the ability of MyEclipse to honor project name extensions (.rar, .sar, .ejb3, etc.). This allows user to deploy all sorts of custom modules to app servers like JBoss that support these differently named module types.

The problem here is that we didn’t do a good job of explaining what is happening to our users, so in your case your project is being deployed with the .ejb extension, you can work around this by either renaming your project to not use a dot, or by adding “.jar” to the project name.

[Panagiotis Korros]

I don’t think that this is the correct solution for this problem. You could just respect the archive name in the .mymetadata file and provide a property page to edit the module archive name. Right now the archive attribute is not used at all.

If you use the archive attribute to specify the name of the deployed archive you could support all sorts of custom modules and also provide a greater level of flexibility for the users (like me) that are reliying in the old algorithm to compute archive names (ME 4.0M2).

[Riyad Kalla]

You are exactly right and this is infact the enhancement filed against this behavior right now in our issue tracker.

[Author]

Posts