5 Replies Latest reply on Dec 24, 2010 9:58 AM by notify

Moveing from JBoss 4.2.3.GA + Seam 2.2.0.GA EJB3 App to JBoss 6.0.0.20101110-CR1 using Seam 2.2.1.CR2

notify Dec 20, 2010 4:01 AM

I'm attempting to move a JBoss 4.2.3.GA Seam 2.2.0.GA EJB3 App to JBoss 6.0.0.20101110-CR1 using Seam 2.2.1.CR2.

I used Seam-Gen to get started (as I did originally on my live App) and added 5 entities and just two of my EJBs.

It all appears to start fine;

18:09:50,631 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

        WeEatWell/UserBean/remote - EJB3.x Default Remote Business Interface
        WeEatWell/UserBean/remote-com.weeatwell.interfaces.UserRemote - EJB3.x Remote Business Interface

18:09:50,653 INFO  [SessionSpecContainer] Starting jboss.j2ee:ear=WeEatWell.ear,jar=WeEatWell.jar,name=AuthenticatorBean,service=EJB
3
18:09:50,662 INFO  [EJBContainer] STARTED EJB: com.weeatwell.ejb.AuthenticatorBean ejbName: AuthenticatorBean
18:09:50,665 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

WeEatWell/AuthenticatorBean/remote - EJB3.x Default Remote Business Interface
WeEatWell/AuthenticatorBean/remote-com.weeatwell.interfaces.AuthenticatorRemote - EJB3.x Remote Business Interface

18:09:50,668 INFO  [SessionSpecContainer] Starting jboss.j2ee:ear=WeEatWell.ear,jar=WeEatWell.jar,name=UserRemote,service=EJB3
18:09:50,669 INFO  [EJBContainer] STARTED EJB: com.weeatwell.ejb.UserBean ejbName: UserRemote
18:09:50,675 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

WeEatWell/UserRemote/remote - EJB3.x Default Remote Business Interface
WeEatWell/UserRemote/remote-com.weeatwell.interfaces.UserRemote - EJB3.x Remote Business Interface

18:09:50,699 INFO  [SessionSpecContainer] Starting jboss.j2ee:ear=WeEatWell.ear,jar=WeEatWell.jar,name=AuthenticatorRemote,service=E
JB3
18:09:50,700 INFO  [EJBContainer] STARTED EJB: com.weeatwell.ejb.AuthenticatorBean ejbName: AuthenticatorRemote
18:09:50,703 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

WeEatWell/AuthenticatorRemote/remote - EJB3.x Default Remote Business Interface
WeEatWell/AuthenticatorRemote/remote-com.weeatwell.interfaces.AuthenticatorRemote - EJB3.x Remote Business Interface

18:09:50,725 INFO  [SessionSpecContainer] Starting jboss.j2ee:ear=WeEatWell.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,servi
ce=EJB3
18:09:50,727 INFO  [EJBContainer] STARTED EJB: org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
18:09:50,734 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

WeEatWell/TimerServiceDispatcher/local - EJB3.x Default Local Business Interface
WeEatWell/TimerServiceDispatcher/local-org.jboss.seam.async.LocalTimerServiceDispatcher - EJB3.x Local Business Interface

18:09:50,737 WARN  [TimerServiceContainer] EJBHREE-2193: using deprecated TimerServiceFactory for restoring timers
18:09:51,070 INFO  [SessionSpecContainer] Starting jboss.j2ee:ear=WeEatWell.ear,jar=jboss-seam.jar,name=EjbSynchronizations,service=
EJB3
18:09:51,071 INFO  [EJBContainer] STARTED EJB: org.jboss.seam.transaction.EjbSynchronizations ejbName: EjbSynchronizations
18:09:51,077 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

WeEatWell/EjbSynchronizations/local - EJB3.x Default Local Business Interface
WeEatWell/EjbSynchronizations/local-org.jboss.seam.transaction.LocalEjbSynchronizations - EJB3.x Local Business Interface

18:09:51,167 INFO  [service] Removing bootstrap log handlers

Until;

18:09:51,256 ERROR [org.jboss.profileservice.bootstrap] Failed to load profile:: org.jboss.deployers.client.spi.IncompleteDeployment
Exception: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

DEPLOYMENTS MISSING DEPENDENCIES:
  Deployment "jboss.web.deployment:war=/WeEatWell" is missing the following dependencies:
    Dependency "persistence.unit:unitName=WeEatWell.ear/WeEatWell.jar#WeEatWell" (should be in state "Create", but is actually in st
ate "** NOT FOUND Depends on 'persistence.unit:unitName=WeEatWell.ear/WeEatWell.jar#WeEatWell' **")

DEPLOYMENTS IN ERROR:
  Deployment "persistence.unit:unitName=WeEatWell.ear/WeEatWell.jar#WeEatWell" is in error due to the following reason(s): ** NOT FO
UND Depends on 'persistence.unit:unitName=WeEatWell.ear/WeEatWell.jar#WeEatWell' **

Appears to imply that it can't find the DB connection successfully deployed MyDatabaseName-ds.xml.

I've posted on the JBoss forum to no avail and Googled until the proverbial cows come home!

Any suggestions. Thanks.

1. Re: Moveing from JBoss 4.2.3.GA + Seam 2.2.0.GA EJB3 App to JBoss 6.0.0.20101110-CR1 using Seam 2.2.1.CR2

notify Dec 21, 2010 10:54 AM (in response to notify)

Totally stuck.

Does the latest Seam work with JBoss 6.x?
Actions
2. Re: Moveing from JBoss 4.2.3.GA + Seam 2.2.0.GA EJB3 App to JBoss 6.0.0.20101110-CR1 using Seam 2.2.1.CR2

lvdberg Dec 21, 2010 11:48 AM (in response to notify)

Hi,

unless you have a very commercial/technical reason to migrate to Jboss AS6, I would go for AS5 because your existing application is not able to use the new features of AS6 without doing some substantial rewriting/reconfiguring.

I wilol certainly experiment/migrate next year, but with Seam3.

Leo
Actions

3. Re: Moveing from JBoss 4.2.3.GA + Seam 2.2.0.GA EJB3 App to JBoss 6.0.0.20101110-CR1 using Seam 2.2.1.CR2

notify Dec 22, 2010 2:44 AM (in response to notify)

Thanks Leo for your contribution. Will probably act on your advice, though now fixed with;

The problem with that web.xml is this section:

<persistence-unit-ref>
<persistence-unit-ref-name>WeEatWell/pu</persistence-unit-ref-name>
<persistence-unit-name>../WeEatWell.jar#WeEatWell</persistence-unit-name>
 
1) Do you really need that persistence-unit-ref? If not then just remove it.
2) If yes, then you'll have to set the correct unit name (which we can decide after looking at your application packaging details).

I'm now encountering further (context) problems when trying to start my Home page!

Regards.

4. Re: Moveing from JBoss 4.2.3.GA + Seam 2.2.0.GA EJB3 App to JBoss 6.0.0.20101110-CR1 using Seam 2.2.1.CR2

lvdberg Dec 22, 2010 3:47 AM (in response to notify)
Hi,

JPA is defined in such a way that it can be used in stand-alone J2se application but also with J2EE. In the latter you don't need to define the location of the JAR-file. But you need to define the following to be able to use the entitymanager (be aware that since AS5, JBOSS has native support for JPA, while AS4.2 has is as an extra!!!).

<property name="jboss.entity.manager.factory.jndi.name" value="java:/WHATEVEREntityManagerFactory" />

In components.xml you can reference it:

<persistence:managed-persistence-context name="entityManager" auto-create="true" persistence-unit-jndi-name="java:/WHATEVEREntityManagerFactory" />

Leo
Actions
5. Re: Moveing from JBoss 4.2.3.GA + Seam 2.2.0.GA EJB3 App to JBoss 6.0.0.20101110-CR1 using Seam 2.2.1.CR2

notify Dec 24, 2010 9:58 AM (in response to notify)

Regenerated my project with Seam-gen using;

jboss-seam-2.2.1.CR3

and now sucessfully deployed and running on;

JBoss 6.0.0.20101110-CR1
Actions

Go to original post