*
The moose likes Web Services and the fly likes JAXWS with Frontend CXF API vs WSDL top down approach Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "JAXWS with Frontend CXF API vs WSDL top down approach" Watch "JAXWS with Frontend CXF API vs WSDL top down approach" New topic
Author

JAXWS with Frontend CXF API vs WSDL top down approach

Rithanya Laxmi
Ranch Hand

Joined: Jan 24, 2011
Posts: 135
Hi,

I am creating and consuming JAXWS in java,

1) Where it is better to create a WS using frontend API like JaxwsServerFactorybean (produce)& JaxwsProxyFactoryBean (consume)or use the WSDL contract based approach?
2) By using the frontend API you dont have relay on the WSDL as much as it can be generated through the SEI with ?wsdl typed in the browser, hence WSDL is not used for generating the java classes to be used for consuming the WS as it is with WSDL contract based approach? In which we will use wsimport or wsdl2java to generate the java classes to comsume the WS?

Now tell me know which approch we need to use , i feel using front end api is easier and using this we can add more features of CXF like LoggingInInterceptor,LoggingOutInterceptor,SOAPHandlers,Handlerchain, etc by setting those in JaxwsServerfactoryBean which is not possible if we genereate the java classes from WSDL (using contract first approach)?

Please clarify and let me know your opinion any links on these as which one to choose is highly appreciated.

Thanks.


 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JAXWS with Frontend CXF API vs WSDL top down approach
 
Similar Threads
Web Services Security in tomcat6
Using ResultSet as return Type in Web Services
Client Code Change - Adding new field
Difference between Apache CXF Maven distribution and CXF distribution
Which web service tool/tech to use for consuming ?