You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/05 05:15:40 UTC
[jira] [Resolved] (CAMEL-4714) Improvements to
camel-example-cxf-tomcat sample
[ https://issues.apache.org/jira/browse/CAMEL-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-4714.
---------------------------------
Resolution: Fixed
Assignee: Willem Jiang
Applied the full patch with thanks of Glen.
> Improvements to camel-example-cxf-tomcat sample
> -----------------------------------------------
>
> Key: CAMEL-4714
> URL: https://issues.apache.org/jira/browse/CAMEL-4714
> Project: Camel
> Issue Type: Improvement
> Components: examples
> Reporter: Glen Mazza
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: camelCXFTomcat.patch
>
>
> Hi, attached patch makes the following changes to the camel-example-cxf-tomcat sample:
> 1.) Reactivates the client call (mvn exec:java now enabled); README updated.
> 2.) In the README, provides sample SOAP requests for usage via soapUI.
> 3.) Allows for optional faster deployment of the WAR via mvn tomcat:deploy (for TC7) or mvn tomcat:deploy -PTomcat6 (TC6) instead
> of just manually copying the WAR to the webapps folder.
> 4.) Removed the resource filtering (as the client Java file was missing it and hence not working, and there's enough of a case
> that SOAP web service providers shouldn't have a version # in the deployed WAR) in favor of a hardcoded
> "camel-example-cxf-tomcat" WAR file name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira