users@jax-ws.java.net

Re: Still wsimport errors using JAX-WS 2.1EA3 (was: Strange wsimport and WSDL/XSD validation issues: Name resolution)

From: Andreas Loew <Andreas.Loew_at_Sun.COM>
Date: Fri, 17 Nov 2006 11:01:35 +0100

Vivek,

Vivek Pandey schrieb:
> If you can provide me a complete testcase, I can try to reproduce it
> and tell what the problem is.

I have already done so yesterday: You should have received a private
mail from me (16/11/06 11:23 AM MET) with the subject: "CONFIDENTIAL:
gematik WSDL and XSD files" which contains the original customer WSDL as
well as the stripped-down GTEST.xsd XML schema created by me which fails
validation in NetBeans although XMLSpy and myself consider the XSD to be
perfectly valid.

My feeling is that the XSD validation failure is directly related to the
wsimport problem as validiation complains about not being able to
resolve references in a very similar way as wsimport does when trying to
create the Java binding.

Over the week-end, I'll also try to proceed getting the XMLBeans/XFire
scenario for the exact same WSDL to run for a small test message - the
XMLBeans Java binding has already successfully been generated, but I'm
still struggling with XFire/XMLBeans deployment into Glassfish.

Looking forward eagerly to your findings... ;-)

Thank you & best regards,

Andreas

-- 
Andreas Loew
Java Architect
Sun Microsystems (Germany)