On Tue November 3 2009 3:30:42 pm Randd12 wrote:
> hi
> 
> Issue 1:
> I am generating all code from wsdl with multiple schemas and discovered
>  when deploying a cxf-se if there are any anonymous types, an
> illegalargumentexception is thrown from
> com.sun.xml.txw2.Document.writeValue:125. That is, if any of the generated
> annotations contains @XmlType(name=""), you get the exception.
> 
> After determining why the Java files were generated this way, I modified
>  the schemas to not use anonymous types and things look peachy.
> 
> Question:
> Is it safe to assume this is user error and the schemas were invalid? or
> should the cxf JAXBUtils be able to handle these case?

Well, this is JAXB itself, not the CXF JAXBUtils.  

That said, we certainly have a lot of tests that use both formats so I have no 
idea why it wouldn't be working for you.    What version of CXF and what 
version of the JDK and what version of JAXB?   That information may help 
diagnose it.

Dan

> 
> Issue 2:
> If I add a redefine for one of the schemas for the type House for example,
> cxf generates a House.java, and OriginalHouse.java. My problem is with
> OriginalHouse.java, it is generated w/ an @XmlType(name="") annotation
>  which brings me back to the error described above.
> 
> Question:
> How can I a) add type name information myself (jaxb custom binding??) or b)
> make cxf work w/ anonymous types?
> 
> Some reference links:
> [1]
> http://old.nabble.com/client-side-JAXB-marshalling-error%28instance-of-xxx-
> is-substituting-yyy-but-xxx-is-bound-to-an-anonymous-type%29-on-polymorphic
> -element-td20193622.html [2]
>  http://www-01.ibm.com/support/docview.wss?uid=swg1PK84673
> [3]
> http://www.docjar.com/docs/api/com/sun/xml/internal/txw2/Document.html#writ
> eValue%28Object,%20NamespaceResolver,%20StringBuilder%29 [4]
>  http://www.mail-archive.com/[email protected]/msg04000.html
> 
> thanks,
> -r
> 
> crosspost: [http://fusesource.com/forums/thread.jspa?threadID=1381]
> 

-- 
Daniel Kulp
[email protected]
http://www.dankulp.com/blog

Reply via email to