Benson Margulies-4 wrote: > > >> 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. > > What do you mean by annotations in this context? (@'s)? It sure is true > that the CXF runtime is ignorant of the old XFire annotations and vica > versa, since we've changed all the packages. An @nnotation is just an > object in a class. No way can XFire see the new @nnotations, since they > all got new names. >
Yes, the @'s in the JARred class files. They were showing up as "org.codehaus.xfire.aegis.type.java5.XmlType" in the old JAR and "org.apache.cxf.aegis.type.java5.XmlType" in the new compiled classes. This is the part I wasn't seeing up until a little while ago. (Light in the refrigerator type thing. :) ) So I realized that XFire wasn't going to see/find the CXF/Aegis annotation marker and thus use the package name for the namespace when generating the SOAP. Anyway, you did essentially answer my questions with the following: > A jar of annotated classes has to go with the reader of the annotations. > ... and ... > In my limited experience, it seems more common for server-providers to > tell their clients to pick the kit of their choice and use wsdl2java to > build their own proxies. > Thanks! -- View this message in context: http://www.nabble.com/XFire-%3ECXF-discovery-question-tp14590348p14590628.html Sent from the cxf-user mailing list archive at Nabble.com.
