Hi,
Can someone tell me the correct way to build an ejb client, and then
reference that from within another module. Currently I'm using the ejb
plugin with the "generateClient" parameter set to true. This results in a
second artifact (the client jar) being built and deployed to the repository
with a "client" prefix. To get my war module to use the ejb client, as
opposed to the implementation, I modified the dependency and added the in a
"classifier" element with the value "client"
i.e
<dependency>
.
.
<classifier>client</classifier>
</dependency>
This seems to work, but I want to make sure I'm doing it the correct way. I
can't create a separate project that just contains the interfaces, dto's
etc, because I use xdoclet to generate most of these from the bean
implementation. As a result, "all" of the jars that the ejb is dependent on
get included in any packaged modules that reference the ejb client. I can't
really see a way around this at the moment given the way dependencies are
expressed.
I'm also having problems trying to deploy an ear build using the ear plugin.
The actual problem is that within my packaged ear, I have a single ejb
module, which gets correctly added the application.xml, however the sessions
beans inside this module, extend an abstract base class that resides in a
dependent jar. This jar gets included in the ear, however it doesn't get
added to either the application.xml or the ear manifiest, causing deployment
to jboss to fail. This might be just a jboss quirk, but can someone tell me
if this is normal behavior for the ear plugin. I noticed in the
documentation for the ear plugin that inside the plugin's configuration I
can add one or "<jarModule>" elements, but shouldn't this be done for me
automatically.
Thanks
Rob
