]
Geoffrey De Smet resolved JBRULES-3520.
---------------------------------------
Resolution: Out of Date
This issue is out of date and discarded.
If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira
projects.
CamelServerApp.class missing, camel-client.xml wrong for Drools and
jBPM integration camel server war on Tomcat
---------------------------------------------------------------------------------------------------------------
Key: JBRULES-3520
URL:
https://issues.jboss.org/browse/JBRULES-3520
Project: JBRULES
Issue Type: Release
Components: drools-camel
Affects Versions: 5.4.0.CR1, 5.4.0.Final
Environment: Tomcat 6.x
Reporter: Ryley Gahagan
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: 5.4.0.CR1, 5.4.0.Final
Attachments: CamelServerApp.class, CamelServerApp.java, camel-client.xml
Original Estimate: 2 hours
Remaining Estimate: 2 hours
The CamelServerApp.class file is missing from the war. Also, the camel-client.xml has, as
default:
<to uri="cxfrs://http://localhost:8080/drools-server/kservice/rest"/>
<to uri="cxfrs://http://localhost:8080/drools-server/kservice/soap"/>
Which Tomcat deploys out of the box as
<to
uri="cxfrs://http://localhost:8080/drools-camel-server-5.4.0.Final/kservice/rest"/>
<to
uri="cxfrs://http://localhost:8080/drools-camel-server-5.4.0.Final/kservice/soap"/>
(...5.4.0.CR1 for that dist)
Has existed for awhile, apparently. Documentation indicates test.jsp working out of the
box.