camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-4714) Improvements to camel-example-cxf-tomcat sample
Date Mon, 28 Nov 2011 15:25:39 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158508#comment-13158508
] 

Glen Mazza commented on CAMEL-4714:
-----------------------------------

Willem, I apologize, the patch is good without any changes needed.  I just confirmed, if I
use <build>...<finalName>foo</finalName></build> in the pom.xml, I'll
get foo.war in the target directory (good for local deployment, client can always access it:
 http://localhost:8080/foo/...) but Maven will nicely still add the version number and timestamp
(foo-1.2.3-SNAPSHOT.war) when it places it in the repo.

There's enough of a use case to *not* placing the version number in the deployed war (namely,
so client endpoints won't need updating each time the webapp changes to a new version number)
that I think the example is good using <finalName/>.  Someone might wish to revert back
to resource filtering to deploy WARs w/version numbers but that can be done at a later date.

                
> 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
>            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

        

Mime
View raw message