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">
<connection-url>jdbc:derby://localhost:1527/CAMEL_MESSAGETRACED</connection-url>
<driver-class>org.apache.derby.jdbc.ClientDriver</driver-class>
<driver>derbyclient.jar</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>APP</user-name>
<password>APP</password>
</security>
</datasource>/
/<driver name="derbyclient.jar" module="org.apache.derby">
<driver-class>org.apache.derby.jdbc.ClientDriver</driver-class>
<xa-datasource-class>org.apache.derby.jdbc.ClientXADataSource</xa-datasource-class>
</driver>/
b. Derby was installed as a module in jboss so that it got loaded during
startup.
i. Created a derby folder in jboss7.1.Final/modules/org/apache
ii. Created a main folder under derby
iii. Added derbyclient.jar in jboss7.1.Final/modules/org/apache/derby/main
iv. Added the module.xml with the following entry in
jboss7.1.Final/modules/org/apache/derby/main folder
/<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.apache.derby">
<resources>
<resource-root path="derbyclient.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.servlet.api" optional="true"/>
</dependencies>
</module>/
c. In camel-context, used the jta data source instead of the hibernate
connection properties
/<jta-data-source>java:jboss/datasources/derbyDS</jta-data-source>/
Please do let me know if there is a better approach.
Thanks and Regards,
Bhavani
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724733.html
Sent from the Camel - Users mailing list archive at Nabble.com.
