[davidwillard]

I’m having a strange issue with an Enterprise Application. The same project worked in 7.5, 8.0M1 and M2, but broke with the 8.0 stable release.

Here’s the deal:
When I deploy to my JBoss server using Exploded mode, my auto-generated application.xml looks like this in the workspace:

<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
  <display-name>JST</display-name>
  <module id="JST_Web_WAR">
    <web>
     <web-uri>JST_Web.war</web-uri>
      <context-root>/cmt</context-root>
    </web>
  </module>
  <module id="JST_Services">
    <ejb>JST_Services.jar</ejb>
  </module>
</application>

And something during exploded deployment strips off the .war and .jar in the web-uri and ejb sections like this:

<module id=”JST_Web_WAR”>
<web>
<web-uri>JST_Web</web-uri>
<context-root>/cmt</context-root>
</web>
</module>
<module id=”JST_Services”>
<ejb>JST_Services</ejb>
</module>

This breaks the deployment. If I use production mode, it deploys the correct, unedited application.xml. If I uncheck the main project’s Deployment builder, it works once until I redeploy and the Deployment Builder is re-enabled.
I notice the same behavior on an upgrade install and clean install from pulse or all-in-one, both Vista and Linux (OpenSuSE 11.2). I recreated the project from scratch and just copied in my src folders… same result.

Anyone else seen this bug or have a workaround?

[support-shalini]

davidwillard,
Can you give some more information?
1. Can you copy paste your installation details form MyEclipse > Installation Summary > Installation details?
2. Is the project created with MyEclipse? If so which version of MyEclipse.

[davidwillard]

Like I said before, this problem only manifests itself on MyEclipse 8.0GA, and the project was originally created in Myeclipse 7.5, but I started from scratch in 8.0GA and the problem was still there.

Installation details follow:
–snipped—

[Loyal Water]

davidwillard,
Can you hit the pm button at the bottom of my post and send me a sample project to help us reproduce this issue at our end. We were unable to reproduce it.

[davidwillard]

Here are the steps to reproduce:
1. create a new enterprise application project named “test” or whatever using J2EE 5.0 and check the add new web and ejb project checkboxes. Click next.

2. Creating the web project in the wizard. (the default names are fine.) Click Next.

3. Create the EJB project, default are fine for the first page, for the persistence setup I put “test” for the JNDI field and you can use whatever DB connector you want, the default derby one is fine, pick whatever schema.

4. Now that the project is created, setup a 1.5.0 JDK (you DO have one….right? 😉 ) and make that the default JRE in window->preferences.

5. Extract a JBoss server somewhere on your machine. I used this for the server: http://sourceforge.net/projects/jboss/files/JBoss/JBoss-4.2.0.GA/jboss-4.2.0.GA.zip/download

6. Set the server up in MyEclipse in the Window->Prefs->Myeclipse->Servers->JBoss->JBoss 4.x by chossing the dir of the server you just extracted and making it use the 1.5 JDK (probably not important since we won’t actually need to run this to see the bug).

7. Once JBoss is enabled make a configuration for it so it appears in the servers tab.

8. right click on the JBoss you created in the servers tab and select “add deployment.” Select “test” under Project and leave Deploy type set to Exploded Archive. Hit Finish.

9. Now, here’s the bug…if you look at the auto-generated application.xml in the test project’s META-INF dir, you will see it references testWeb.war and testEJB.jar. If you look at the deployed ear, (in jboss_4.2.0.GA\server\default\deploy\test.ear\META-INF ) and open the application.xml there, you will see the .jar and .war stripped off the ends of the <web-uri> and <ejb> tag data (testWeb and testEJB).

10. if you undeploy it and re-deploy it in production mode…then unzip the generated EAR, it all looks like it’s supposed to, with the correct extensions appended.

One more thing, it’s probably just the JBoss 4.x connector, because I tried it with a JBoss 5.x server and the application.xml was fine. Too bad I need 4.x!

[support-shalini]

This message has not been recovered.

[davidwillard]

This message has not been recovered.

[Loyal Water]

This message has not been recovered.

[davidwillard]

Bug STILL happens in 8.5 M2 and the “Milestone Stream” version of 8.5 Stable…am I the only guy using JBoss 4.x? Has anyone else seen this?

[Brian Fernandes]

David,

As Shalini stated earlier, we were unable to reproduce this internally. I am queuing this up for further research by our dev team now and will let you know what they find.

[neyanderson]

Morning,

I’ve had same problem using windows 7 pro, MyEclipse Version: 8.6.1 Build id: 8.6.1-20101117 and Jboss 4.2.3GA.

Any news?

Thanks

[davidwillard]

Still happens in MyEclipse 9…It’s been a year and a half…maybe take another stab at it? It is tedious to have to edit application.xml every time I deploy.

[Brian Fernandes]

We are actively looking at this problem right now, I will post any findings back here.
Sorry for the inconvenience caused.

[Brian Fernandes]

David,

We found a bug in our “custom servers” i.e. servers which you can create from an existing server connector in case you need more than one configuration for a server. This bug was causing the application.xml file to be written without suffixes; we have fixed this for 9.0.1.

When going through the steps you posted earlier, I noticed your step 7 – “make a configuration for it so it appears in the servers tab”. Why was this necessary? If you enable JBoss, it would appear in the servers view immediately, and if you used that configuration, you would not run into this problem. Thoughts?

ney, are you using a custom configuration as well instead of the primary server?

[neyanderson]

Yes David

This problem only happens when a I use custom configuration server. I’ve tested with default server configuration and this problem do not happened.

[Author]

Posts