Hi Gareth,
As you use EJB 3, you must be using JBoss 4 or above.
It happens that on JBoss 4 (of another anterior version), the classloading of
JBoss have changed. Now, it seems that it load the resources in alphabetic
order.
Try to change the name of u Datasource deployment to something like 1
... but first, verify on your log to see any Exception and if the naming
service is up.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872873#3872873
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872873
Have u a firewall ? Verify if it leave u access u jndi on 1099.
Another important thing, the naming starting with java:comp/env is not
accessible out of Container. Use another name like jdbc/MyDataSource, ejb/MyEjb
in spite of java:comp/env/ejb/MyEjb, ...
View the original post :
http://www.
Hey samfra,
Where is your post ?
How I do that ? Install/Deploy Hibernate 3 and remove Hibernate 2 ? How I do
this ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872868#3872868
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode
Hi Danrall,
In the below item on the FAQ on wiki we have:
| Which JBoss version with what JDK?
|
| JBoss version series 3.2.x 4.0.x 5.0.x
(HEAD)
| compiles with JDK version 1.3/1.4 1.4/5.0 1.4/5.0
| runs under JDK version 1.3/1.4/
Observing the code:
|public JDBCCreateCommand createCreateEntityCommand()
| throws DeploymentException
|{
|
| JDBCCreateCommand cec;
| try
| {
| cec = (JDBCCreateCommand)manager.getMetaData().
| getEntityCommand().getCommandCl
