OK, things appear to be working ok.  The problem was a classloading one in my
application server - The JAXB annotations on the POJOS were of the same
class but in a different classloader, so XFire couldn't find them when it
did resolveAnnotation() calls.

It still would be nice to have a working test example in the XFire
distribution.


greenstar wrote:
> 
> I am using XFire (1.2.5) and JAXB 2 to do code first development.  This
> supposedly allows me to use JAXB 2.0, JSR181 Annotations and XFire's wsdl
> generation together (as described in the docs here:
> http://xfire.codehaus.org/JAXB+2.0 under heading: "Code First
> Development").
> 
> However the generated wsdl does not include any of my custom JAXB
> information (ie: @XmlType, etc.).  It's like it's being completely
> ignored, and a "default" (aegis?) schema is being created.  I have
> followed all the directions in the docs, including of course specifying
> the jaxb2 serviceFactory in META-INF/xfire/services.xml.
> 
> In the xfire distribution, under examples/jaxb2, there is only a schema
> first example.  Can anyone come up with a working example that works as
> described in the docs here: http://xfire.codehaus.org/JAXB+2.0 under
> heading: "Code First Development", where JAXB annotations will control the
> name and namespace of the type in the wsdl?  For example, the docs uses
> the following type:
> 
> @XmlType(name="Book", namespace="urn:xfire:book")
> public class Book
> {
>     private String title;
>     private String isbn;
>     private String author;
> ...
> }
> 
> But there is no real working test in the distribution that illustrates
> this.  Does this indeed work?
> 

-- 
View this message in context: 
http://www.nabble.com/XFire-and-JAXB%3A-Code-First-Development-tf3538548.html#a9887501
Sent from the XFire - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to