[Frank Weber]

I am interested in the EJB3 development on JBoss. The deployment currently requires a ‘ .ejb3 ‘ suffix for the archive.

Is there any way to define this for an EJB project?

Thanks,

Frank

[Scott Anderson]

Frank,

We’ll be supporting more capabilities like this directly in some upcoming releases. The way to do this now is to name your EJB project with the full name you’d like the archive to have when deployed. When the deployer sees a project name that already includes the suffix, it uses the full project name “as is” when packaging and deploying it to the server. So, just name your EJB project something like myejb.ejb3 and that should do it.

[Paul Baker]

I’m using Eclipse 3.1M4, MyEclipse3.8.4Beta1, and JDK5.0.

my EJB project is named:
eLoadSheetEJB.ejb3

But when the EAR is created it contains:
eLoadSheetEJB.ejb3.jar

Aplication.XML

<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.4" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
   <display-name>eLoadSheet</display-name>
   <module id="myeclipse.1112369587656">
      <web>
         <web-uri>eLoadSheetWeb.war</web-uri>
         <context-root>eLoadShee</context-root>
      </web>
   </module>
   <module id="myeclipse.1112237161283">
      <ejb>eLoadSheetEJB.ejb3</ejb>
   </module>
</application>

How can I get the deployer to not add the “.jar”

[Scott Anderson]

Guys,

I just ran some tests and when you deploy in a *packaged* format, the correct .ejb3 suffix is maintained but in exploded format the .jar is erroneously added. I’ve opened a bug report for the latter case. However, there’s an easy workaround. In the deployment dialog instead of specifying the ‘JBoss 4’ deployment location, specify <Custom Location> and set the path to be the ‘deploy’ directory under your configured JBoss instance. If you want to know where that is, simply copy the location from your JBoss deployment location before you remove it. Once you’ve set up deployment to use the <Custom Location> packager instead of the JBoss-specific one, the suffixes will be respected as you’d like.

[Frank Weber]

Scott,

On Linux M6 this work-aroung seems to work fine for *.ejb3, but not for *.war included as well in exploded enterprise archive !?

Yes both extension are carried through and appear correct in the deploy dir of the AS. However I got an error that the web project “could not be opened, does it exist?” The name shown in the exception does NOT show the .war as one would expect.

Confusing to me is that I got the Calculator EJB3 example deployed initially wrapped in an enterprise project and deployed to <custom location> … with the following project names: calculator linked to Calculator.ejb3 and Calculator. But when I now tried it again it did not work.

Thanks in advance !

Frank

[Frank Weber]

Scott,

let me add to my previous posting that the application.xml in the project is not the same as the one that is deployed into deploy dir via <custom location>.

If I manually change the file, add .war to the project name and restart the jboss4 server then it seems to work fine.

BTW: when do you think the new Milestone for MyEclipse 4 comes out to support eclipse 3.1 on linux? I need the annotations and don’t like to go back to 3.02….

Frank

[Riyad Kalla]

Frank,
We are hoping for M2 in another couple of weeks or sooner and then we will move to doing RCs until everything is nice and stable.

[Author]

Posts