camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4714) Improvements to camel-example-cxf-tomcat sample
Date Mon, 28 Nov 2011 03:36:41 GMT


Glen Mazza commented on CAMEL-4714:

Hold off on this patch, unfortunately.  Because we release the WAR to the central repository
we might be required to include the version within the WAR file name.  I'll look into it.
> Improvements to camel-example-cxf-tomcat sample
> -----------------------------------------------
>                 Key: CAMEL-4714
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: examples
>            Reporter: Glen Mazza
>            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:!default.jspa
For more information on JIRA, see:


View raw message