[Panagiotis Korros]

I have 1 ear project containing 1 ejb project and 1 war project.
my application xml is:

<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE application PUBLIC ‘-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN’ ‘http://java.sun.com/dtd/application_1_3.dtd’&gt;
<application>
<display-name>Test</display-name>
<description></description>
<module>
<ejb>TestEJB.jar</ejb>
</module>
<module>
<web>
<web-uri>Test.war</web-uri>
<context-root>/test</context-root>
</web>
</module>
</application>

when i deploy to jboss (jboss 3.0.8 with tomcat 4.1.24) my application.xml file in the exploded war is changed to:

<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE application PUBLIC ‘-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN’ ‘http://java.sun.com/dtd/application_1_3.dtd’&gt;
<application>
<display-name>Test</display-name>
<description></description>
<module>
<ejb>TestEJB</ejb>
</module>
<module>
<web>
<web-uri>Test</web-uri>
<context-root>/test</context-root>
</web>
</module>
</application>

This was working ok in the previous MyEclipse Version (my current version is 2.5).

[Scott Anderson]

First, a little bit of background on JBoss and directory suffixes:
In JBoss 2.x, exploded directory names must not be adorned with the archive suffixes. However, for JBoss 3 & 4 in order for exploded deployments to function the directories must end with the appropriate archive suffix.

When we split the JBoss connector in the latest release, we set them up to understand this issue. But, in order to make things easier for our users that are upgrading, we copied their existing JBoss preferences to all JBoss connectors.

What I think may be happening is that you’re actually using the JBoss 2 connector to launch JBoss 3, and this would account for the issue.

Will you please check all your JBoss connector settings and ensure that JBoss 2 & 4 are disabled and that the JBoss 3 connector is configured appropriately?

–Scott
MyEclipse Support

[Panagiotis Korros]

I checked my preferences and both JBoss 2 and JBoss 4 are disabled.

My JBoss 3 seems to be configured appropriately also.

[support-michael]

I just replicated and confirmed this as a bug. I have entered a report into our problem tracking system for development to address. The fix will be available as part of a maintenance release in the very near future.

Thanks for your assistance.

Michael
MyEclipse Support

[dombat]

I’m having the same problem. After updating to 2.5 GA, I can’t run my apps as exploded archives in jboss 3.2.1, I get a “…could not be opened, does it exist?)” error.
What do you mean by “maintenance release in a very near future” ?
I can’t use myeclipseide any more, this a blocking issue !

Dom

[support-michael]

We anticipate a maintenance release next Monday or Tuesday that will include a fix for this problem. We apologize for the inconvience caused by this problem.

Michael
MyEclipse Support

[Scott Anderson]

This issue has been addressed in v2.5.1

–Scott
MyEclipse Support

[Author]

Posts