3 Replies Latest reply on Mar 24, 2010 3:43 AM by jaikiran pai

    where is this source code?

    null null Novice

      This source is not found in the src tarball on the downloads page...

       

      org.jboss.ejb3.Ejb3Deployment.resolvePersistenceUnitSupplier(Ejb3Deployment.java:770)

       

      I can't seem to find it.  I found an org.jboss.ejb3.deployers.Ejb3Deployer.java file but not the above file .  I tried poking around the EJB3 project but could not find there either.  Where is this source code?

       

      thanks,

      Dean

        • 2. Re: where is this source code?
          null null Novice

          thanks, that helped alot.  After looking there and digging, I tried xcore3.jar#xcore and ./xcore3.jar#xcore, etc. etc.  I am close to giving up.  I have a log file for each use case.  Unfortunately, there are not many logs in this part of the system...I turned up to trace and started to look some more but couldn't really find what was going on.......

           

          I keep thinking, if the OSGi stuff in jboss was more stable, that would work perfectly as "I think" i could just put xcore3.jar in my client jars classpath through the OSGi bundle manifest...this has worked great in the past....hmmmm, in fact, isn't everything in the same classloader?  why is it not picking up xcore3.jar anyways?   I wonder if I added jboss-app.xml if that would help any and specified the same classloader for all client jars and the ejb3 jar if that would work.....As you can tell, I don't believe in ears .  I hate them and have worked with OSGi quite a bit in another platform and love that much more...seems cleaner.  I tried the JBoss OSGi stuff a month ago but kept running into bugs.

           

          later,

          Dean

          • 3. Re: where is this source code?
            jaikiran pai Master

            null null wrote:

             

             

            I keep thinking, if the OSGi stuff in jboss was more stable, that would work perfectly as "I think" i could just put xcore3.jar in my client jars classpath through the OSGi bundle manifest...this has worked great in the past....hmmmm, in fact, isn't everything in the same classloader?  why is it not picking up xcore3.jar anyways? 

            It (the problem that we are discussing in your other thread http://community.jboss.org/thread/149710?tstart=0) is not really related to classloading. By the way, if you are interested in OSGi related stuff on JBoss AS, then you might want to follow the JBossOSGi project http://community.jboss.org/wiki/jbossosgi