Hmm, when using sculptor-generator.properties:
deployment.applicationServer=JBoss
The generated persistence.xml:
java:jdbc/MyAppDS
You should change the jndi name in the datasource to
jdbc/MyAppDS
jboss-web.xml is not needed, and not generated by sculptor.
/Patrik
By the way, jndi name in you
Hi Danny,
this is a bug in sculptor 1.6.
The correct JNDI name to lookup the datasource in JBoss
should be 'java:jdbc/UniverseDS' not java:comp/java/jdbc/UniverseDS.
We have to fix this.
As quick workaround you can try adding this to SpecialCases.xpt.
«AROUND templates::Hibernate::persistenc
Good, thanks for reporting the problem. We are glad that we could assist you.
Good luck with the evaluation and let us know if you have any questions.
/Patrik
--
View this message in context:
http://www.nabble.com/Problem-deploying-Sculptor-generated-.war-file-in-JBoss-tp24167140s17564p2418310
In your first post the log is:
Failed to look up JNDI DataSource with name 'java:comp/env/jdbc/UniverseDS'
NameNotFoundException: jdbc not bound
In the latest:
Failed to look up JNDI DataSource with name
'java:comp/env/jdbc/applicationDS'
NameNotFoundException: applicationDS not bound
So you hav
I have created jira issue for this:
http://fornax.itemis.de/jira/browse/CSC-362
An alternative that might work is that you add the following to web.xml:
jdbc/UniverseDS
javax.sql.DataSource
Container
And create a jboss-web.xml:
Hi Danny,
this is a bug in sculptor 1.6.0.
The correct JNDI name to lookup the datasource in JBoss
should be 'java:jdbc/UniverseDS' not java:comp/java/jdbc/UniverseDS.
We have to fix this.
As quick workaround you can try adding this to SpecialCases.xpt.
«AROUND templates::Hibernate::persiste
Hi,
>From the stack it looks like you havn't registred the datasource in the jndi
tree in jboss. Have you added the file:
server/default/deploy/universe-mysql-ds.xml
with the content as stated in the tutorial?
See:
http://fornax.itemis.de/confluence/display/fornax/4.+Archetype+Tutorial+(CSC)#4.Arch
