Reshat Sabiq <crts <at> argushealth.com> writes:
> JAXB Alone does support arrays/lists. There's a book example,
> w/ the following
> generated, and successfully marshalled/unmarshalled:
> java.util.List getBook();
>
> Above, however, this goes from JAXB back to aegis, for some reason.
> Why would it
> do that?
> 1) Should i somehow config aegis to map java.util.List, or
> 2) is this because JAXB 1 isn't fully utilized and
> thus the fix should be in
> making sure the execution doesn't go from JAXB back to aegis?
>
> Some architecture feedback here would be appreciated.
In JaxbTypeRegistry the following calls on to DefaultTypeMappingRegistry to get
org.codehaus.xfire.aegis.type.XMLTypeCreator:
protected TypeCreator createTypeCreator()
{
return new JaxbTypeCreator(super.createTypeCreator(), jaxbContext);
}
To me that appears to be not what should be happening, because i'd expect
org.codehaus.xfire.jaxb.JaxbTypeCreator to be used w/ JAXB, rather than
org.codehaus.xfire.aegis.type.XMLTypeCreator.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
