[jboss-jira] [JBoss JIRA] (JBRULES-3520) CamelServerApp.class missing, camel-client.xml wrong for Drools and jBPM integration camel server war on Tomcat

[Damon Horrell (JIRA)]

     [ https://issues.jboss.org/browse/JBRULES-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damon Horrell updated JBRULES-3520:
-----------------------------------

    Attachment: CamelServerApp.java
                CamelServerApp.class
                camel-client.xml


Files for 6.0.1 attached.
                
> 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
>      Security Level: Public(Everyone can see) 
>          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: camel-client.xml, CamelServerApp.class, CamelServerApp.java
>
>   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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira