JBossDeveloper

I am seeing the following error in server.log, will have to debug to see why "java" is getting doubled...

   New missing/unsatisfied dependencies:

      service jboss.naming.context.java.java:jdbc/eFpDataSource (missing)

looks like the double "java" isn't the issue.

Instead, lets try changing the datasource name to something like "java:jboss/datasources/eFpDataSource"

There's a bug in the PersistenceUnitDeploymentProcessor. It isn't handling the jta-data-source value properly while translating it into a ServiceName. As a workaround, I changed the jta-data-source value in persistence.xml to remove the java: prefix:

<jta-data-source>jdbc/eFpDataSource</jta-data-source>

It still doesn't deploy due to (different) missing dependencies. I am not sure what it's missing yet.

P.S: Something appears to have changed just before CR1 with respect to error reporting. The errors weren't this complex earlier.

Changing the datasource to "java:jboss/datasources/eFpDataSource" worked for me.

I added a jira (https://issues.jboss.org/browse/AS7-1171) for this problem.

Change from the above to:

updated DS definition:

<xa-datasource jndi-name="java:jboss/datasources/eFpDataSource" pool-name="eFpXADS" enabled="true" use-java-context="true" use-ccm="true">

updated persistence.xml:

<jta-data-source>java:jboss/datasources/eFpDataSource</jta-data-source>

Hi,

I am trying to migrate from AS 6 to AS 7.0.0 Final and get a similar problem, although I changed the datasource like above suggested by Scott.

09:51:15,845 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "myapp.war" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"myapp.war\".component.SearchHome.START missing [

jboss.naming.context.java.module.myapp.myapp.\"env/com.myapp.persistence.generated.SearchHome/entityManager\" ]"

The class looks like

@Stateless

public class SearchHome {

     @PersistenceContext

    protected EntityManager entityManager;

In AS 6 it deployed without problems.

Any help would be greatly appreciated

Have you configured the datasource in standalone.xml? What does it look like? Also what are the contents of your persistence.xml file?

yes, datasource is in standalone.xml:

<datasource jndi-name="java:jboss/datasources/MyAppDS" pool-name="MyAppDS_Pool" enabled="true" jta="true" use-java-context="true" use-ccm="true">

persistence.xml (relevant parts):

<persistence-unit name="myapp">

<provider>org.hibernate.ejb.HibernatePersistence</provider>

<jta-data-source>java:jboss/datasources/MyAppDS</jta-data-source>

Thanks for the quick reply!

Does using:

@PersistenceContext(unitName="myapp")

make a difference? If not, can you please attach the application which reproduces this issue?

No, it doesn't make a difference. I thought it could be the location of the persistence.xml file (WEB-INF/classes/META-INF and not META-INF), but doesn't help neither.

Attached a slim version of the war archive to reproduce the problem. I will delete it after a while.

Thanks