[forgotit]

If I try to create an ejb project called abc.ejb, the .mymetadata file is wrong: it sez

<project-module
type=”EJB”
name=”abc.ejb”
id=”myeclipse.1107515468868″
j2ee-spec=”1.3″
archive=”abc.ejb” />

when it should clearly be

<project-module
type=”EJB”
name=”abc.ejb”
id=”myeclipse.1107515468868″
j2ee-spec=”1.3″
archive=”abc.ejb.jar” />

(The difference is that the .jar at the end of the archive name is missing)
This does not happen for war projects or ear projects, just for ejb projects.

It not only does this at project creating but every time we check this out of CVS it (un)helpfully replaces the abc.ejb.jar with abc.ejb so we have to constantly keep an eagle eye on this…
Any ideas?
Oh and thanks for all the good work and brilliant support!

Regards
Ngapulay

[Riyad Kalla]

Ngapulay,
This is actually a feature we added a while back because of a handful of JBoss users that wanted to deploy certain projects as specialized JBoss modules (SAR, RAR, HAR, etc files). There was no way for us to keep on top of all the archive types JBoss supports, so we added the feature if a project has an extension in its name, we would archive and deploy that project using the extension in the name. That way users could easily setup:
WebProject
HibernateModules.har
JBossModule.rar

and deploy them all and get the HAR and RAR files correctly deployed to the app server.

The workaround of course is to not name your projects with periods in them.

[Author]

Posts