i have a web application A that call one remote session ejb deployed in a application B
the application A doesn't have any EJB but to call the ejb deployed from application B use a jar client
my problem is that the company that provided my the client jar to call the ejb deployed in the applicationB
contain inside not only the stub and the interfaces, but also the ejb implementation, i mean a class with this annotations
the result is that when i try to deploy the application the container try to deploy the ejb
how ca in solve this problem?
actually my application is bundled in a war.... i deploy directly the war
may be if i create an ear and configure the application.xml to have only the web application and not that ejb could work?
other ways i have to open the jar client and remove ejb implementation
i tryed with the ear solution configuring just the application.xml
that is this
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" id="Application_ID" version="6">
so there is not definition of the ejb
but my applciation continue to publish the ejb contained inside the jar client
I think you're going to have to strip the implementation classes from your "client" jar.
You should consider incorporating this into your build process in case you get updates from this other company. It would be fairly easy to manage using the Unjar and Jar Apache Ant tasks, which are also easily incorporated into an Apache Maven build as well.
If the other company is a vendor I would be asking them to fix it.
that is what I did today to let it to start
unfotunally the company the provided my the client is not the vendor, but the customer!! and they already use this client in other application deployed with websphere
and obviusly doesn't have this problem
anyway my build process is base on maven so i will take your advice to use meven and ant to clear the client.jar for my
As a general rule your better off using specific maven plugins (even if you write your own) rather than generating artifacts using the antrun plugin.