Sorry, but ejb-client is not supported yet in m2e-wtp (See https://issues.sonatype.org/browse/MECLIPSEWTP-26) In order to implement proper ejb-client support, Eclipse WTP needs to open up it's API (https://bugs.eclipse.org/bugs/show_bug.cgi?id=330894)
One possible workaround for you is to create a new dedicated module containing your interfaces (and any relevant classes) and acting as your ejb client. All other modules would depend on it. I know it's not perfect but it should work. Other users might know & share better workarounds. Regards, Fred Bricon 2011/8/26 Lars Fischer <[email protected]> > Hello, > > I use Eclipse Indigo, Maven 3.0.3 and m2e with wtp to develop TWO > dependent EAR applications. > > I split the projects into ear and ejb projects and use the ejb/ear > packaging. > The ejb projects are configured to create 2 jars (EJB and EJB-CLIENT) > > EAR-a contains EJB-a and EJB-a-CLIENT. > EJB-a deploys a SessionBean with a special global jndi name (this is > required). > > EAR-b uses the EJB-a-CLIENT dependency to enable remote calls on EAR-a. > > > Building with maven and running the created archives, everything is > fine. But running the open projects direct from the eclipse workspace, > I get this problem: > > Inside the eclipse, the complete EJB-a (not only the client part) is > used to create EAR-b. Now also EAR-a and EAR-b contain EJB-a and then > I have TWO SessonBeans trying to use the same global jndi name. --> > NameAlreadyBoundException :( > > > > How can I prevent that wtp uses the complete EAR-a? It only has to use > the EJB-a-CLIENT part like configured inside the pom dependencies of > EAR-b. > > > Regards, > Lars > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > -- "Have you tried turning it off and on again" - The IT Crowd
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
