-
1. Re: Avoid Jboss AS7 to deploy ejb
alesky78 May 24, 2012 5:16 AM (in response to alesky78)1 of 1 people found this helpfuli 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">
<display-name>EarTest</display-name>
<module>
<web>
<web-uri>co.web.war.war</web-uri>
<context-root>co</context-root>
</web>
</module>
</application>
so there is not definition of the ejb
but my applciation continue to publish the ejb contained inside the jar client
-
2. Re: Avoid Jboss AS7 to deploy ejb
sfcoy May 24, 2012 10:18 AM (in response to alesky78)1 of 1 people found this helpfulI 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.
-
3. Re: Avoid Jboss AS7 to deploy ejb
alesky78 May 24, 2012 10:43 AM (in response to sfcoy)Thank Stephen
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
thanks again
-
4. Re: Avoid Jboss AS7 to deploy ejb
sfcoy May 24, 2012 11:10 AM (in response to alesky78)If you're using maven it may be easier to use the dependency:unpack goal of the maven dependency plugin to build your client jar. Maven will jar it back up again for you.
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.