On 16 March 2010 11:04, Wouter van Reeven <wouter_at_van.reeven.nl> wrote:
> On Tue, Mar 16, 2010 at 10:56:38AM +0200, Richard Kolb wrote:
> > You don't think so ? Perhaps.
> > But a EJB does not need a war to function as it can have web services,
> > schedules etc.
> >
> >
> >
> > I suppose you should create an ear with the EJB jar and the log4j jar
> in
> > it, especially when using Java EE5. And I don't think this is
> different
> > in Java EE6.
> >
> >
> > I could, but that's messy with Maven
> > Then when I add a dep to the EJB , I need to add it to the EAR and not
> get the
> > version different
>
> Yes I know :-) I think it's common knowledge that packaging EJBs is
> messy, even in Java EE5.
>
> What happens when you do not use Maven for packaging the EJB jar and
> log4j? Do the log4j classes get included in the EJB jar?
>
That's the thing, it works 100%, because Netbeans packages the JAR
differently to Maven
The log4j-1.2.15.jar is included in the root of the EJB JAR
In the original mail I compared the two ways. One maven, the other NB 6.8
native
regards
Richard.