9 Replies Latest reply on Feb 27, 2009 5:06 PM by Lucas Silva

    Release according to JBossAS 5.0.0.GA

    Juergen Zimmermann Master

      Is a release according to JBossAS 5.0.0.GA being planned?

        • 1. Re: Release according to JBossAS 5.0.0.GA
          Parragh Szabolcs Newbie

          It's so very sad, that this project became dead! The main site even states, that the JBoss 5 kernel is the main focus of the embedded project, and now not even a response for this question in a month! Not a very reassuring attitude from JBoss/RH!

          • 2. Re: Release according to JBossAS 5.0.0.GA
            Ales Justin Master

            Parszab, you're welcome to contribute. ;-)

            btw: what main site states this?

            There was never to my knowledge any promises that
            this is gonna be aligned with JBossAS 5.0.0.GA.

            There is some ongoing work to separate the bootstrap,
            hence making any future Embeddable easier to assemble.

            • 3. Re: Release according to JBossAS 5.0.0.GA
              Carlo de Wolf Master

              To put it bluntly: there will be no release of the old JBoss Embedded that is compatible with AS 5.0.0.GA.

              But we are working on a facility that allows unit testing outside of the Application Server with the same codebase. Therein the same JBoss MicroContainer as used in AS as the heart. We want to try and have this before the release of Enterprise Application Server 5.

              As an example you can take a look at the EJB 3.1 Embeddable prototype: http://www.jboss.org/wiki/EJB31Embeddable
              It doesn't use JBoss Bootstrap yet, but that'll come.

              JBoss Bootstrap itself is already used for some of the unit tests within the EJB 3 project (booting up the JTA 'profile'):

              10:47:03,660 INFO [LookupTransactionManagerTestCase] dir = file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/
              10:47:03,720 INFO [VFSCacheFactory] Using VFSCache [NoopVFSCache]
              10:47:03,736 INFO [ServerImpl] Starting JBoss (Microcontainer)...
              10:47:03,737 INFO [ServerImpl] Release ID: JBossAS Bootstrap 0.1.0-SNAPSHOT
              10:47:03,737 INFO [ServerImpl] Bootstrap URL: null
              10:47:03,737 INFO [ServerImpl] Home Dir: FileHandler@10378355[path= context=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/ real=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/]
              10:47:03,737 INFO [ServerImpl] Home URL: vfsfile:/home/carlo/work/ejb3/jta-profile/target/bootstrap/
              10:47:03,738 INFO [ServerImpl] Library URL: vfsfile:/home/carlo/work/ejb3/jta-profile/target/bootstrap/lib/
              10:47:03,739 INFO [ServerImpl] Patch URL: null
              10:47:03,739 INFO [ServerImpl] Common Base URL: vfsfile:/home/carlo/work/ejb3/jta-profile/target/bootstrap/common/
              10:47:03,739 INFO [ServerImpl] Common Library URL: vfsfile:/home/carlo/work/ejb3/jta-profile/target/bootstrap/common/lib/
              10:47:03,739 INFO [ServerImpl] Server Name: default
              10:47:03,740 INFO [ServerImpl] Server Base Dir: FileHandler@3154093[path=server context=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/ real=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/]
              10:47:03,740 INFO [ServerImpl] Server Base URL: vfsfile:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/
              10:47:03,740 INFO [ServerImpl] Server Config URL: file:/home/carlo/work/ejb3/jta-profile/src/test/resources/conf/
              10:47:03,740 INFO [ServerImpl] Server Home Dir: FileHandler@28399250[path=default context=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/ real=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/]
              10:47:03,741 INFO [ServerImpl] Server Home URL: vfsfile:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/
              10:47:03,743 INFO [ServerImpl] Server Data Dir: FileHandler@2691004[path=data context=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/ real=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/data/]
              10:47:03,744 INFO [ServerImpl] Server Library URL: vfsfile:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/lib/
              10:47:03,744 INFO [ServerImpl] Server Log Dir: FileHandler@27959193[path=log context=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/ real=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/log/]
              10:47:03,748 INFO [ServerImpl] Server Native Dir: FileHandler@26171428[path=native context=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/tmp/ real=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/tmp/native/]
              10:47:03,749 INFO [ServerImpl] Server Temp Dir: FileHandler@29887233[path=tmp context=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/ real=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/tmp/]
              10:47:03,750 INFO [ServerImpl] Server Temp Deploy Dir: FileHandler@31706449[path=deploy context=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/tmp/ real=file:/home/carlo/work/ejb3/jta-profile/target/bootstrap/server/default/tmp/deploy/]
              10:47:03,750 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
              10:47:04,197 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/home/carlo/work/ejb3/jta-profile/src/test/resources/conf/bootstrap.xml
              10:47:05,522 INFO [ServerImpl] JBoss (Microcontainer) [0.1.0-SNAPSHOT] Started in 1s:769ms
              10:47:06,187 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
              10:47:06,187 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
              10:47:06,324 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TxControl_1] - Name of XA node not defined. Using 7f000001:a0af:4995419a:0
              10:47:06,499 INFO [arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_1] - Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 5712
              10:47:06,502 INFO [arjLogger] TransactionStatusManagerItem - host: 127.0.0.1 port: 5712
              10:47:06,584 INFO [arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_3] - TransactionStatusManager started on port 5712 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
              10:47:06,594 INFO [tsmxLogger] Registering mbean for module 'arjuna'
              10:47:06,599 INFO [tsmxLogger] Initialising JMX agent com.arjuna.ats.internal.jbossatx.agent.LocalJBossAgentImpl
              10:47:06,617 INFO [TransactionManagerService] Initializing recovery manager
              10:47:06,654 INFO [arjLogger]
               --- Start RecoveryActivators
              10:47:06,660 INFO [arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery_13] - Recovery manager listening on endpoint 127.0.0.1:5,713
              10:47:06,663 INFO [arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.ready] RecoveryManagerImple is ready on port 5,713
              10:47:06,664 INFO [TransactionManagerService] Recovery manager configured
              10:47:06,664 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
              10:47:06,724 INFO [TransactionManagerService] Starting transaction recovery manager
              10:47:06,816 INFO [ServerImpl] Shutting down the server, blockingShutdown: false
              10:47:06,840 INFO [ServerImpl] Server exit(0) called

              So depending on your needs there is already some stuff that can help you out, but it's not yet in a state where we want to release it.

              (I especially like the Started in 1s:769ms. :-) (I know it's a bit of cheating... ;-) )

              • 4. Re: Release according to JBossAS 5.0.0.GA
                Parragh Szabolcs Newbie

                Thanks for the replies!

                I might have misunderstood what can be read on this site: http://www.jboss.org/community/docs/DOC-9690 namely that: "The focus of Embedded JBoss is to be able to run the JBoss 5 Kernel and JEMS services with a non-JBoss-controlled classloader. "

                I thought it sort of meant that the goal was to provide an embedded system that would be compatible with the JBoss 5 AS. Which would be great to some of us, who need exactly this ;-) -- e.g. if they develop applications that they want to run both as standalone desktop and client-server apps -- with the same codebase. Is it not a major appeal of the Embedded JBoss idea?

                And trust me, I would love to contribute if I was good enough a developer for such complex tasks ;-) Hope I will have a chance later!

                • 5. Re: Release according to JBossAS 5.0.0.GA
                  Lucas Silva Newbie

                  I have misunderstood about this site: http://www.jboss.org/community/docs/DOC-9690 too.

                  Well what I need is a facility that allows unit testing outside of the Application Server.
                  So, I use JBoss AS 5 and I want to use junit through eclipse, maven, and hudson.

                  I have followed this instructions: http://www.jboss.org/community/docs/DOC-9618 it worked with Session Beans, but I need JPA (hibernate) working too. So now I am having problems in jpa-deployers-beans.xml. Anyone could help me ?
                  I got this message:

                  *** DEPLOYMENTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
                  PersistenceUnitDependencyResolver -> class org.jboss.jpa.resolvers.strategy.SpecCompliantSearchStrategy{Installed:** NOT FOUND **}
                  


                  Carlo could you tell me how do you boot up JTA profile ?

                  • 6. Re: Release according to JBossAS 5.0.0.GA
                    Lucas Silva Newbie

                     

                    "landir" wrote:

                    I got this message:
                    *** DEPLOYMENTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
                    PersistenceUnitDependencyResolver -> class org.jboss.jpa.resolvers.strategy.SpecCompliantSearchStrategy{Installed:** NOT FOUND **}
                    


                    Well now I got other problem, this one above is ok. The problem is that the class EmbeddedDataSourceDependencyResolver is NYI.
                    Do you guys have any idea to workround it or how to implement it ?

                    • 7. Re: Release according to JBossAS 5.0.0.GA
                      Carlo de Wolf Master

                      That's because we don't have a standalone JTA data source deployer yet.

                      So what I do in my project is in deploy/jpa-deployers-beans.xml:

                      <deployment xmlns="urn:jboss:bean-deployer:2.0">
                       <bean name="DataSourceDependencyResolver"
                       class="org.jboss.ejb3.timerservice.mk2.test.common.SimpleDataSourceDependencyResolver"/>
                      </deployment>

                      But it actually doesn't belong there. It should be provided by said JTA data source deployer.

                      And then conf/bootstrap/derby.xml:
                      <?xml version="1.0" encoding="UTF-8"?>
                      <deployment xmlns="urn:jboss:bean-deployer:2.0">
                       <!-- As a 'mock' DataSource we use HSQLDB -->
                       <bean name="HSQLDBService" class="org.jboss.ejb3.timerservice.mk2.test.common.HSQLDBService">
                       <depends>NamingServer</depends>
                       </bean>
                      </deployment>

                      Hmm, it would probably be better to put that data source dependency resolver here.

                      http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/timerservice-mk2/src/test/java/org/jboss/ejb3/timerservice/mk2/test/common/HSQLDBService.java
                      http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/timerservice-mk2/src/test/java/org/jboss/ejb3/timerservice/mk2/test/common/SimpleDataSourceDependencyResolver.java

                      As you can see the two are basically hard-coded cousins.
                      Anyway this will give you a data source, but not a JTA compliant one. I'm not yet sure how this will affect operations.

                      • 8. Re: Release according to JBossAS 5.0.0.GA
                        Carlo de Wolf Master

                         

                        "parszab" wrote:
                        Thanks for the replies!

                        I might have misunderstood what can be read on this site: http://www.jboss.org/community/docs/DOC-9690 namely that: "The focus of Embedded JBoss is to be able to run the JBoss 5 Kernel and JEMS services with a non-JBoss-controlled classloader. "

                        I thought it sort of meant that the goal was to provide an embedded system that would be compatible with the JBoss 5 AS. Which would be great to some of us, who need exactly this ;-) -- e.g. if they develop applications that they want to run both as standalone desktop and client-server apps -- with the same codebase. Is it not a major appeal of the Embedded JBoss idea?

                        And trust me, I would love to contribute if I was good enough a developer for such complex tasks ;-) Hope I will have a chance later!

                        The goal is to get an Embedded that is 100% compatible with AS 5, but it won't happen for 5.0.0.GA. :-)

                        Almost all the code you see running is the code that's going into AS 5.1 & 6, so it should be compatible. Note that some bits have been replaced because they make no sense in a light environment.

                        • 9. Re: Release according to JBossAS 5.0.0.GA
                          Lucas Silva Newbie

                          After a plenty of tries I succeded well in executing jpa + ejb3 with junit. So I got one problem that I want to know how can I fix it.
                          In my Stateless bean I have a EntityManager property that is annotated with @PersistenceContext but it didn't inject the value there. So I want to use the interceptor or samething else. It would help me a lot.