On Fri, 18 Nov 2016 11:17:08 +0100 Stefan Seidel wrote:
> you don't usually depend on EJBs in your WARs.
That's actually right. You depend on the API (interfaces) of the EJBs.
This is usually in separate JAR (but it is not required to be).
> You should depend on
> ejb- client. IIRC you'll have
Hi,
you don't usually depend on EJBs in your WARs. You should depend on ejb-
client. IIRC you'll have to explicitely configure your EJB project to create an
ejb-client artifact.
I just tried that though, and the ejb-client JAR is still kept inside the WAR.
Are you planning to deploy your WAR fi
On 17 Nov 2016, Clemens von Musil wrote:
> We pushed a very minimal example project to a public github repo located
> here:
>
> https://github.com/kr1schan/mavenToy
>
> The project consists of an ear, two war modules, one ejb module and one
> plain jar artifact.
> Both war modules depend on the
We pushed a very minimal example project to a public github repo located
here:
https://github.com/kr1schan/mavenToy
The project consists of an ear, two war modules, one ejb module and one
plain jar artifact.
Both war modules depend on the ejbmodule as well as on the jar artifact.
SkinnyWar is ena
On 16 Nov 2016, Clemens von Musil wrote:
> This is true for jar dependencies.
>
> But if the war file depends on an artifact with type ejb
> (ejb), the skinnywar-option ignores this dependency and let it
> remain in war/lib.
This is not true in general, it works for me!
Did you declare the depen
This is true for jar dependencies.
But if the war file depends on an artifact with type ejb
(ejb), the skinnywar-option ignores this dependency and let it
remain in war/lib.
And if there are two war files WAR1 and WAR2 depending on the same artifact
with type ejb, the ear isn't deployable as the
On 14 Nov 2016, Clemens von Musil wrote:
> Hi again,
>
> thanks a lot for your advice, Martin.
>
> We spent a lot of time into skinny wars but stuck with ejb dependencies.
>
> The EAR contains several WAR modules and these WAR modules share several
> EJB modules.
> Unfortunately, the skinny war
Hi again,
thanks a lot for your advice, Martin.
We spent a lot of time into skinny wars but stuck with ejb dependencies.
The EAR contains several WAR modules and these WAR modules share several
EJB modules.
Unfortunately, the skinny war option seems to ignore transitive EJB
dependencies so that
Hi!
On 08 Nov 2016, Clemens von Musil wrote:
> I am working on a multimodule maven project consisting of several EJB, WAR
> and an EAR module. The EJB modules contain shared functionality.
>
> To increase development speed, I want the WAR modules build in a way that
> allows me to bundle them in
