Thanks Ron. I am specifically interested in CXF framework. Like I understand your point but the only reason I am going into details is that I can understand the Web service better as a product or a technology. There are several concepts like JAXWS, JAXB, WSDL, Schemas....etc and each plays a significant role in the Web service infrastructure per say. And there are plenty of Web service based use cases which most of the people (specially ones like me) don't even know.
I am just going a bit far as I can understand the semantics of this framework (CXF) better and therefore also understand the Web service as a technology better. My apologies if that has confused you. I am just kinda researching and it can just make me more better equipped to use Web services in projects. Thx Raj On Tue, Mar 15, 2011 at 9:50 PM, Ron Wheeler <[email protected] > wrote: > I am certainly not an expert in this area but it seems that you are getting > a bit far into the details. > CXF looks after a lot of the plumbing for you and you should be able to get > a simple web service and its clients going without to much worry about the > internal flow. > > What are you trying to build? > Is there anything about what you need to do that you expect to be outside > the normal web services pattern? > > We were able to build quite a few web services in a simple Tomcat/Jetspeed > portal environment just by following the normal CXF patterns as described on > the site and in the docs. > I did not do the work but my team got things done very quickly with no big > complaints or delays. > > It might help if you described your IDE and the frameworks that you want to > use. > For example, we used Eclipse/STS with a Spring, Hibernate, MySQL and > Tomcat. > This probably has an impact on the tools, process and packaging that people > will recommend to you. > > Good luck. > Ron > > > > On 15/03/2011 11:10 AM, Raj Floyd wrote: > >> Hi Dan, >> >> Thanks for the reply. But still need to understand this. I am a novice in >> Web service and researching on various Web service use cases. The obvious >> and basic ones are consuming the service with the code first and contract >> first approach. Coming to your reply: >> >> 1. I can use the generated client and server code (and they do not use >> ObjectFactory or XXResponse classes) and comfortably run my services. Now >> as >> you said the ObjectFactory is checked by JAXB for xsd:any type. What >> situation makes use of this scenario? >> >> 2. XX and XXResponse are used as wrappers @ runtime. It happens when? >> >> I am sorry for the above questions, it may sound trivial, but need to >> understand the flow. Any pointers will be greatly appreciated. >> >> Thx >> >> Raj >> >> On Tue, Mar 15, 2011 at 7:18 PM, Daniel Kulp<[email protected]> wrote: >> >> On Tuesday 15 March 2011 8:27:40 AM Raj Floyd wrote: >>> >>>> Hi, >>>> >>>> When I use wsdl2java with either client or server option, it generates >>>> ObjectFactory class, >>>> >>> JAXB itself uses that. In cases where there are xsd:any and similar or >>> places >>> where a JAXBElement is needed, it checks the ObjectFactory for the right >>> methods for dealing with the actual elements. >>> >>> XX and XXResponse classes. Why are these classes >>>> generated and where it could be useful? >>>> >>> When available, they are used at runtime. The parameters (and returns) >>> are >>> wrappered with these objects and fed into JAXB as one whole unit instead >>> of >>> for each param. >>> >>> -- >>> Daniel Kulp >>> [email protected] >>> http://dankulp.com/blog >>> Talend - http://www.talend.com >>> >>> >
