maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Newbie trying to understand how to use some plugins
Date Tue, 11 Jun 2013 15:11:42 GMT

Thanks for your response.

I don't really need to make the EJB jar work standalone. I was trying to divide and conquer.
In 4.2.2 I deployed the EJB jar as part of an EAR with 2 WARs. I think that I'd like to deploy
to JBoss AS 7 with an EAR containing the EJB jar, and two separate wars that use the services
of the beans packaged in the EAR. I'm a little concerned though because I read that if I go
this route, the web tier will be forced to use the remote interfaces while they currently
use local interfaces. Do you know if this is correct?  



On Jun 10, 2013, at 1:05 PM, Wayne Fay <> wrote:

>> Anyway, I'm running into issues at deployment time (just starting with the EJB jar
as a
>> standalone deployment) because the EJB jar depends on a 3rd party jar that is not
>> available on the server.
> If you **really** need to make the EJB jar work in standalone
> deployment (which is not especially common IME), you could make this
> work with the shade plugin (or other similar plugins) by packaging the
> contents of your dependencies in alongside your own project files in
> an "uberjar" or "onejar."
>> I'd like to avoid that this time, so I'm thinking, much like WAR and EAR files have
>> META-INF/lib directories, a jar file might have something similar. Does this fall
>> the definition of a jar? Is there no way to package a 3rd party jar upon which one's
>> depends with one's jar, so that at runtime the dependencies can be resolved by the
>> classloader?
> The Java Jar file specification does not allow Jar files to contain
> other Jar files so this is not possible (unless you are using a
> special classloader which does not conform to the spec like
> Classworlds).
> Instead, you should be using dependencies in your WAR and EAR pom
> files to declare "this project depends on these libraries" and Maven
> will automatically pull those Jar files in and include them in the WAR
> or EAR packages when they are constructed.
> Are you sure that you need this EJB jar to work in standalone
> deployment? Or is this just something you're trying for something to
> do, and you will generally deploy the EJB in a WAR/EAR? If the latter,
> I would ignore this "problem" for now and continue working to make the
> WAR/EAR function as you require.
> Wayne
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message