I do have a problem with JBoss AS5. 
datasource is accessed via JNDI before it is even bound

My environment
Win XP SP2
Java 1.5.0 10
Seam 2.0.3.CR1 (This should include compatibility patches for AS5.0)
richfaces-ui-3.2.1.GA
JBT 2.1.1

The story:
Created a Seam project with JBT 2.1.1  (mysql database)
and deployed it successfully to JB AS 4.2.2GA

Created a server for 5.0.0.CR1
Deployed the above mentioned project to it. 

The problem is a kind of ordering:

  | 07:15:58,703 INFO  [Contexts] starting up: prunusEntityManagerFactory
  | 07:15:58,859 INFO  [Version] Hibernate Annotations 3.4.0.CR1
  | 07:15:58,890 INFO  [Environment] Hibernate 3.3.0.CR1
  | 07:15:58,906 INFO  [Environment] hibernate.properties not found
  | 07:15:58,921 INFO  [Environment] Bytecode provider name : javassist
  | 07:15:58,937 INFO  [Environment] using JDK 1.4 java.sql.Timestamp handling
  | 07:15:59,125 INFO  [Version] Hibernate Commons Annotations 3.1.0.CR1
  | 07:15:59,125 INFO  [Version] Hibernate EntityManager 3.4.0.CR1
  | 07:15:59,515 INFO  [NamingHelper] JNDI InitialContext 
properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory,
 java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interf
  | aces}
  | 07:15:59,515 ERROR [DatasourceConnectionProvider] Could not find 
datasource: java:/prunusDatasource
  | javax.naming.NameNotFoundException: prunusDatasource not bound
  | 
  | 07:16:00,421 INFO  [ConnectionFactoryBindingService] Bound 
ConnectionManager 'jboss.jca:service=DataSourceBinding,name=prunusDatasource' 
to JNDI name 'java:prunusDatasource'
  | 
As you see, the datasource is accessed via JNDI before it is even bound:-(

Can someone reproduce this behaviour?

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162430#4162430

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162430
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to