[CONF] Apache CXF 2.0 Documentation: Celtix Migration Guide (page edited)

[confluence]

Page Edited : CXF20DOC : Celtix Migration Guide Celtix Migration Guide has been edited by Adrian Trenaman (Jan 22, 2007). Change summary: Added some tips based on my experience porting the old Celtix exercise system to CXF. (View changes) Content: Migrating applications from Celtix to CXF is reasonably straightforward; both follow the JAX-WS mapping so the bulk of application code will no require any modification. Here are some things to look out for: There are some obvious changes of package names from org.objectweb.celtix.* to org.apache.cxf.*. If you have used any celtix-specific non-JAX-WS APIs in your application (for example, using the Bus), then you will have change imported package names. There is no Bus.init() or Bus.getCurrent() method. In CXF, you can create a bus using concrete implementations of the BusFactory.createBus() method, and then make your new bus the default bus as shown below. SpringBusFactory bf = new SpringBusFactory(); Bus bus = bf.createBus("ws_rm.xml"); bf.setDefaultBus(bus); Later, to get the bus, you can call Bus bus = bf.getDefaultBus(); On your classpath, change celtix.jar to cxf-incubator.jar; this jar contains manifest entries to pick up all other required jars in the CXF runtime. If you call getPort() on the client side then you must specify the target namespace of the WSDL contract as the namespace of the port name, like this: HelloWorld helloWorld = helloWorldService.getPort( new QName("http://www.my/wsdl/target/namespace", "SOAPOverHTTPEndpoint"), HelloWorld.class ); In Celtix you could leave the namespace of the port name as an empty string "". However, if you do that in CXF then the call to getPort() will fail. This latter behaviour is more in keeping with the JAX-WS specification (see Section 4.2.3 of the JAX-WS Specification).

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences