I've asked a question or three over the past couple of weeks during my attempt to convert from XFire to CXF, using Aegis. I think I have the server side sorted out and working correctly; my sticking point was not understanding why I had problems using the XFire client to talk to the CXF service.
Here's the catch and subsequent question: We gave our customers a JAR full of our precompiled proxy objects, a fairly significant package of 70+ container classes. These objects have XFire/aegis annotations in them. When I created an XFire test client using the precompiled class JAR file, I kept getting nulls in most of the object members, and I finally looked at the SOAP going across and realized the members had the wrong namespace. I finally realized XFire saw the CXF-version annotations and simply ignored them, and use the class package name for the namespace of the members. So I reverted to using the earlier XFire-annotated JAR classes and now it works again. So I now realize that we can't really safely publish a JAR full of proxy objects and assume all of our customers can use it - rather, only customers using the specific stack (XFire 1.2) can make correct use of this JAR file. So the question becomes - what is the standard way of providing customers with proxy objects? I'm guessing the answer is: "Let them use the WSDL to generate proxy objects with their chosen framework." Does that make sense? Again, I'm still feeling my way past the basic examples that we extended for our own use, so I'm "wet behind the ears yet." -- View this message in context: http://www.nabble.com/XFire-%3ECXF-discovery-question-tp14590348p14590348.html Sent from the cxf-user mailing list archive at Nabble.com.
