For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 8 replies, 3 voices, and was last updated 20 years, 8 months ago by
.
-
Posts
-
I have an ejb project named xxx.yyy. When I deploy it I get an xxx.yyy folder in the application server instead of an xxx.yyy.jar folder.
I notiched that the .mymetadata file is like:
<project-module
type=”EJB”
name=”xxx.yyy”
id=”myeclipse.2059470588235″
j2ee-spec=”1.4″
archive=”xxx.yyy” />The archive attribute is wrong.
Changing the .mymetadata file to
<project-module
type=”EJB”
name=”xxx.yyy”
id=”myeclipse.2059470588235″
j2ee-spec=”1.4″
archive=”xxx.yyy.jar” />Doesn’t solve the problem either.
What can I do?
You need to rename the project to “xxx.yyy.jar”, the reason the extension of the project is honored when deployed is to help support custom archives (for example in JBoss) that some apps ervers supprot, these can be RAR, SAR, MAR, etc. etc. so what we did is implement a universal mechanism to support any extension type for our deployed projects.
You should just respect the archive=… value in the .mymetadata file. I think that this is enough to support any custom extension like rar sar par etc.
+1 for this enhancement, I am facing the same problem and tried to rename the archive value in .mymetadata with no result.
There is more to it…
If I deploy my ejb project xxx.yyy inside an ear then the project is deployed correctly within an xxx.yyy.jar folder but the application.xml is like:
<?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>sampleapplication</display-name> <module id="myeclipse.2059470588235"> <ejb>exodus.ecentric</ejb> </module> </application>Notice that the module name containes the .jar extension!
