|
As of October 27th, please open all new issues in the Red Hat Customer Portal . |
|
Aileen Cunningham made changes - 29/Apr/08 12:53 PM
sure, spring-dm, what ever works best. (at the time of jira creation camel-cxf was supposed to be the method of choice but in fairness i think there was alot of flux. gnodets example did not exist yet.)
top priority is to validate smx4 as container of choice, if it is indeed the container of choice. This is exactly the kind of testing that needs to be done to validate SMX4 as the deployment environment of choice for CXF endpoints. I would agree with Dan that we should focus on deployment of endpoints using Spring DM. An ideal SMX/Fuse CPI would be to run all the CXF demos as Spring DMs in SMX. We made need some kind of Ant target to create the application bundles for these demo. In addition we may need to alter the CXF config a bit to add a jaxws:endpoint to existing config.
Aileen Cunningham made changes - 25/Sep/08 01:53 PM
Aileen Cunningham made changes - 13/Oct/08 08:55 AM
Aileen Cunningham made changes - 17/Oct/08 07:50 AM
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
FUSE SMX4 as deployment platform for CXF
Umm... why would they be a camel-cxf endpoint? That seems strange.
Why wouldn't it be a spring-dm module plugged into SMX4 as per gnodet's sample?