Problems generating multiple services from the same EAR using servicegen

Question

I have a single EJB JAR that contains multiple stateless session beans. I
want to expose each of these individually as a service. So I have defined
the following in my build file:
<servicegen destEar="${ear.file}" warName="${war.file.name}"
contextURI="web_services">
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="AService"
serviceURI="/AService" includeEJBs="AService" generateTypes="True"
expandMethods="True"/>
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="BService"
serviceURI="/BService" includeEJBs="BService" generateTypes="True"
expandMethods="True"/>
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="CService"
serviceURI="/CService" includeEJBs="CService" generateTypes="True"
expandMethods="True"/>
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="DService"
serviceURI="/DService" includeEJBs="DService" generateTypes="True"
expandMethods="True"/>
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="EService"
serviceURI="/EService" includeEJBs="EService" generateTypes="True"
expandMethods="True"/>
</servicegen>
I execute the task and it runs without issue. However, when I attempt to
deploy the EAR I get some odd results (there are multiple jars listed all
with my original name and then a number appended, for example MyApp.ear2).
The deployment fails because each of these JARs contains the same session
beans.
So, I'm wondering if my only option is to package each session bean in a
separate EJB JAR or if there is another way I could get this to work.
Thanks,
Rob

Answer 1

Thanks, Neal. I'll do as you suggest.
Just a little feature enhancement request, as well. It would be nice if the
option existed to break out the webservices for all the session beans in a
ejb rather than creating one all-encompassing interface of all the methods.
I think this would be a useful feature.
Thanks, again,
Rob
"Neal Yin" <[email protected]> wrote in message
news:[email protected]...
I am not sure what can cause this. But I will make servicegen check for
duplicate.
For now, in order to make sure your automatic build process, you can use
ant's build in task "jar" to update your application.xml with a correctone
after servicegen.
-Neal
"Rob Moore" <[email protected]> wrote in message
news:[email protected]...
Neal,
After discussing this issue with a coworker, I found that when he buildsthe
ear on his machine using the servicegen entries I specified previously,the
application.xml is generated correctly. Mine, as you guessed, puts in
multiple module entries all containing references to the same jar. I'm
puzzled because we are apparently running in the same environment. Anyidea
what might be causing it?
Thanks,
Rob
"Neal Yin" <[email protected]> wrote in message
news:[email protected]...
Hi Rob,
There is something wrong during generating application.xml for the
ear.
After servicegen, if you open generated application.xml, you probablycan
see duplicate entries for one module. Please go ahead delete thoseredundant
entries. Let me know if this works.
-Neal
"Rob Moore" <[email protected]> wrote in message
news:[email protected]...
I have a single EJB JAR that contains multiple stateless session
beans.
I
want to expose each of these individually as a service. So I havedefined
the following in my build file:
<servicegen destEar="${ear.file}" warName="${war.file.name}"
contextURI="web_services">
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="AService"
serviceURI="/AService" includeEJBs="AService" generateTypes="True"
expandMethods="True"/>
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="BService"
serviceURI="/BService" includeEJBs="BService" generateTypes="True"
expandMethods="True"/>
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="CService"
serviceURI="/CService" includeEJBs="CService" generateTypes="True"
expandMethods="True"/>
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="DService"
serviceURI="/DService" includeEJBs="DService" generateTypes="True"
expandMethods="True"/>
<service ejbJar="${ejbc.jar.file}"
targetNamespace="http://www.acme.com/xauto" serviceName="EService"
serviceURI="/EService" includeEJBs="EService" generateTypes="True"
expandMethods="True"/>
</servicegen>
I execute the task and it runs without issue. However, when I
attempt
to
deploy the EAR I get some odd results (there are multiple jars
listed
all
with my original name and then a number appended, for exampleMyApp.ear2).
The deployment fails because each of these JARs contains the samesession
beans.
So, I'm wondering if my only option is to package each session bean
in
a
separate EJB JAR or if there is another way I could get this to
work.
>>>>
Thanks,
Rob