Yes, the problem is weblogic's: http://forums.oracle.com/forums/thread.jspa?threadID=701300&tstart=0
On Mon, Nov 3, 2008 at 6:31 PM, Felipe Kamakura <[EMAIL PROTECTED]>wrote: > Yes, I know =( > > I think it's a Weblogic issue, because I could deploy in Glassfish. > > I'll try a little more, any news I'll report here! > > Regards > > > On Mon, Nov 3, 2008 at 6:23 PM, Fred Bricon <[EMAIL PROTECTED]> wrote: > >> Felipe, >> >> using the real path is a really really bad idea, you lose the >> portability of your project configuration. If you're in a team, I >> doubt everybody uses /home/kakamura/.m2/repository as their repository >> :-) >> >> M2_REPO is set by the m2eclipse plugin and resolved according to your >> settings.xml. >> >> I don't have a clue, right now, why it wouldn't be resolved to >> /home/kakamura/.m2/repository in your case. You can open a jira issue >> with a simple test project showcasing the bug and your eclipse >> configuration attached. I'll take a look at it. >> >> regards, >> >> Fred Bricon. >> >> >> >> On Mon, Nov 3, 2008 at 8:58 PM, Felipe Kamakura >> <[EMAIL PROTECTED]> wrote: >> > I found the problem! >> > >> > After creating a non-maven WTP project, and comparing, I found out that >> the >> > problem was the M2_REPO variable: >> > >> > I replaced all ocurrences of: >> > >> > module:/classpath/var/M2_REPO >> > >> > with >> > >> > module:/classpath/lib//home/kamakura/.m2/repository >> > >> > And then everything worked. >> > >> > Is there a way not to use M2_REPO variable, or to replace it with the >> real >> > path? >> > >> > Thanks again! >> > >> > >> > >> > On Fri, Oct 31, 2008 at 11:38 AM, Fred Bricon <[EMAIL PROTECTED]> >> wrote: >> >> >> >> Felipe, >> >> >> >> Have you tried modifying your projects manifest in WTP by hand >> >> (properties > J2EE module dependencies : check the jars your module >> >> depend on)? >> >> >> >> regards >> >> >> >> Fred Bricon >> >> >> >> On Fri, Oct 31, 2008 at 2:20 PM, Felipe Kamakura >> >> <[EMAIL PROTECTED]> wrote: >> >> > Hi, >> >> > >> >> > Well, I looks like an Issue with Weblogic Server Adapter or >> something, >> >> > because I was able to deploy in Glassfish. Maybe it is the way >> Weblogic >> >> > handles the libraries, and the APP-INF thing it uses... >> >> > >> >> > ='( >> >> > >> >> > Well I'll do some more testing here! Thanks a lot for the help! >> >> > >> >> > On Thu, Oct 30, 2008 at 2:28 PM, Fred Bricon <[EMAIL PROTECTED]> >> wrote: >> >> >> >> >> >> Felipe, >> >> >> >> >> >> are Hibernate jars provided by the server or packaged in your ear? >> >> >> If you embed hibernate using an ear 5 version, your jars should be >> >> >> deployed in the /lib directory of your ear (configure >> >> >> defaultLibBundleDir in your maven-ear-plugin), >> >> >> so there's no need to configure your deployed projects manifest. >> >> >> >> >> >> regards, >> >> >> >> >> >> Fred Bricon >> >> >> >> >> >> On Tue, Oct 28, 2008 at 7:29 PM, Felipe Kamakura >> >> >> <[EMAIL PROTECTED]> wrote: >> >> >> > Hi Fred, >> >> >> > >> >> >> > When I wrote my last post I was in a hurry, so I didn't notice >> that >> >> >> > my >> >> >> > EJB >> >> >> > Session had an annotation that causing an error :) >> >> >> > >> >> >> > But now I'm really stuck with something else. I have a >> persistece.xml >> >> >> > in >> >> >> > my >> >> >> > testewtp-core that declares org.hibernate.ejb.HibernatePersistence >> as >> >> >> > the >> >> >> > provider. When I try to deploy the application, the server doesn't >> >> >> > find >> >> >> > my >> >> >> > Hibernate dependency. >> >> >> > I'm getting a java.lang.ClassNotFoundException: >> >> >> > org.hibernate.ejb.HibernatePersistence. >> >> >> > >> >> >> > Without the persistence.xml and without @PersistenceContext in my >> >> >> > Session >> >> >> > the deploy goes fine. >> >> >> > >> >> >> > I also have another question(s): >> >> >> > >> >> >> > - Usually I use a shared persistence.xml, which is put in a >> separate >> >> >> > jar >> >> >> > (testewtp-config-persistence). I noticed that when using WTP the >> >> >> > server >> >> >> > doesn't find the persistence.xml. It tries to load my session and >> >> >> > when >> >> >> > it >> >> >> > sees the @PersistenceContext I throws an error saying that there >> are >> >> >> > no >> >> >> > persistence units available. Does anybody knows how to proceed in >> >> >> > this >> >> >> > case? >> >> >> > >> >> >> > Thanks a lot! >> >> >> > >> >> >> > On Tue, Oct 28, 2008 at 5:03 AM, Fred Bricon <[EMAIL PROTECTED]> >> >> >> > wrote: >> >> >> >> >> >> >> >> Felipe, >> >> >> >> >> >> >> >> I didn't try Weblogic so I can only guess. The stacktrace is >> pretty >> >> >> >> self explanatory though. >> >> >> >> - The obvious first : does your ejb project contain EJB3 >> annotated >> >> >> >> classes? >> >> >> >> - Try to open the deployed ear, see if the ejb jar contains >> compiled >> >> >> >> classes. If not, try to clean / rebuild / redeploy your project. >> >> >> >> - can you try to deploy the same app on glassfish? >> >> >> >> >> >> >> >> regards, >> >> >> >> >> >> >> >> Fred Bricon >> >> >> >> >> >> >> >> >> >> >> >> Have you tried to open the deployed jar? Are your classes >> >> >> >> >> >> >> >> On Tue, Oct 28, 2008 at 3:35 AM, Felipe Kamakura >> >> >> >> <[EMAIL PROTECTED]> wrote: >> >> >> >> > Hello everyone, >> >> >> >> > >> >> >> >> > I'm testing the Integration with WTP (MNGECLIPSE-688) in >> Weblogic >> >> >> >> > and >> >> >> >> > I'm >> >> >> >> > having some problems here: >> >> >> >> > >> >> >> >> > I have a simple EAR project with one EJB module. Has anyone >> have >> >> >> >> > this >> >> >> >> > problem while trying to deploy the EAR? >> >> >> >> > >> >> >> >> > java.io.IOException: No EJBs found in the ejb-jar file >> >> >> >> > 'testewtp-core.jar'. >> >> >> >> > Please ensure the ejb-jar contains EJB declarations via an >> >> >> >> > ejb-jar.xml >> >> >> >> > deployment descriptor or at least one class annotated with the >> >> >> >> > @Stateless, >> >> >> >> > @Stateful or @MessageDriven EJB annotation. >> >> >> >> > at >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:191) >> >> >> >> > at >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93) >> >> >> >> > at >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:965) >> >> >> >> > at >> >> >> >> > >> >> >> >> > >> weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:335) >> >> >> >> > at >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) >> >> >> >> > Truncated. see log file for complete stacktrace >> >> >> >> > >> >> >> >> > >> >> >> >> > My project structure is like this: >> >> >> >> > testewtp >> >> >> >> > - testewtp-app (EAR) >> >> >> >> > - testewtp-core (EJB) >> >> >> >> > - testewtp-core-client (JAR) >> >> >> >> > - testewtp-config (JAR) >> >> >> >> > - testewtp-config-persistence (JAR) >> >> >> >> > >> >> >> >> > I have the maven-ear-plugin declaring the testewtp-core as an >> >> >> >> > ejbModule. >> >> >> >> > >> >> >> >> > I think this is more a Weblogic Plugin's Issue than >> M2Eclipse's. >> >> >> >> > >> >> >> >> > Thanks in advance! >> >> >> >> > >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> GMail rox! >> >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> >> To unsubscribe from this list, please visit: >> >> >> >> >> >> >> >> http://xircles.codehaus.org/manage_email >> >> >> >> >> >> >> >> >> >> >> > >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> GMail rox! >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe from this list, please visit: >> >> >> >> >> >> http://xircles.codehaus.org/manage_email >> >> >> >> >> >> >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> GMail rox! >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe from this list, please visit: >> >> >> >> http://xircles.codehaus.org/manage_email >> >> >> >> >> > >> > >> >> >> >> -- >> GMail rox! >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> >
