Re: [m2] including ejb client jar in webapp

Yes, you're right. Could the EJB client ever use the dependencies though? I'm not sure how best to mark them for separation if that is the case. I think the first step is to make none of the dependencies transitive through the ejb client. Please file a JIRA issue. - Brett On 10/26/05, Ashley

Re: [m2] including ejb client jar in webapp

Is that not the correct behaviour? The ejb doesn't include the jars itself, does it? - Brett On 10/25/05, Ashley Williams [EMAIL PROTECTED] wrote: Thanks that works. However I still get all the dependency artifacts referenced in the ejb pom file - is there some way to 'switch off' transitive

Re: [m2] including ejb client jar in webapp

Hi Brett, I believe the client (happens to be a servlet) should only see the remote and home interfaces. The ejb container (on a different VM) will host my enterprise bean and the util classes it needs to get its work done - as well as about 2 dozen dependency classes that get pulled in.

Re: [m2] including ejb client jar in webapp

You need to specify the type as ejb-client in your client project's pom. dependency groupIdcom.abc/groupId artifactIdEjb/artifactId version1.00/version typeejb-client/type /dependency On 10/25/05, Ashley Williams [EMAIL PROTECTED] wrote: Hi, Just wondering how I go about including an

Re: [m2] including ejb client jar in webapp

Thanks that works. However I still get all the dependency artifacts referenced in the ejb pom file - is there some way to 'switch off' transitive dependencies? On 26 Oct 2005, at 03:20, Tomislav Stojcevich wrote: You need to specify the type as ejb-client in your client project's pom.