Deploying ear-files without external jar's

[Former Member]

Hi @ all,

I’ve generated a Web service in the NWDS based on an existing EJB. This EJB needs a jar-file (mdm4j.jar). I linked it as an external jar.

Then I added the service to an EAR Project. There I modified the application-j2ee-engine.xml to define the connection to the already deployed mdm4j on the J2EE Engine:

<reference-target provider-name="sap.com" target-type="library">com.sap.mdm.tech.mdm4j</reference-target>

My Problem is now, that the generated ear-file always includes the external mdm4j.jar from the EJB, instead of just using the already deployed com.sap.mdm.tech.mdm4j on the Engine.

Can anybody help me can’t find a solution.

Regards

Robert

[Former Member]

Hi Amol,

I checked out the archive build info and found no possibility to solve my problem.

Your second hint is solves the problem but not automatically.

I’d like that this is done automatically.

Rgds

Robert

[Former Member]

check out the properties for your EAR project and specifically the archive build info.

Also you can try removing the jar file from your EAR using tools like winzip and then deploying it, making sure that your application-j2ee-engine.xml has refrences to the jar file deployed.

Rgds,

Amol