Hi,
For now , have made the tracer work in the WAR by making the following
changes in Jboss,
a. Changed standalone.xml. The following lines were added,
/datasource jndi-name=java:jboss/datasources/derbyDS pool-name=derbyDS
enabled=true use-java-context=true
Thanks Great to know !
Happy new year .
Regards
Guru
From: BAnanth [via Camel] [ml-node+s465427n5724733...@n5.nabble.com]
Sent: 31 December 2012 14:08:43
To: Gnanaguru Sattanathan (WT01 - BAS)
Subject: Re: Camel Tracer Component - problem with persistence
Hi
camel-example-cxf-tomcat_-_tracer.zip
http://camel.465427.n5.nabble.com/file/n5724443/camel-example-cxf-tomcat_-_tracer.zip
Hi Christian,
I am not able to upload the WAR file(size of the file is huge).
I am however sending the entire source content as a Zip. This has to be put
and extracted
My experience is that I have still had problems getting later versions
(2.9.x) working on JBoss 5.1.0.GA and JBoss 6.
So I still use the JBoss resolver to get things working.
But then again I've not put that much effort into finding the reason I
simply added the resolver and it started working.
Hi Guru
I have added persistence to the exiting cameml-cxf-tomcat example(this is a
WAR file). I have added the necessary dependencies in pom.xml also. The
derby jars are avaiable in web-inf/lib. Still the error is persisting.
Any pointers would be most helpful.
Thanks and Regards,
Bhavani
For me, it looks like something is wrong with your WAR. I assume the derby
database driver is not found:
10:23:31,605 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
(MSC service thread 1-3) HHH000342: Could not obtain connection to query
metadata : No suitable driver found for
: Christian Mueller [via Camel]
[mailto:ml-node+s465427n572430...@n5.nabble.com]
Sent: Wednesday, December 19, 2012 12:36 AM
To: Bhavani Ananth (WT01 - BAS)
Subject: Re: Camel Tracer Component - problem with persistence
For me, it looks like something is wrong with your WAR. I assume the derby
Hello Bhavani,
I also face the same issue with this.
I used Camel-example-tracer. I replaced the in-memory hsql database
configuration with derby standalone in persistence.xml.
I suspect, the issue could be because of how you converted the osgi project
into the WAR/Web-App as you specified.
