I just wanted to follow up on my problem since I have found a solution. The
issue turned out not to be a bug, so much as a bad interaction between
different default choices on the two platforms, combined with misleading
error messages. The solution was to set the elementFormDefault, and
attributeFormDefault attribute on my schema. When they are left unspecified,
.NET and JAX-RPC make different default choices, leading to the
incompatibilities I noted. The error message generated by JAX-RPC is very
misleading, and led me to believe there was a parsing error.
Thanks,
Dave
On 6/23/05, Doug Kohlert <Doug.Kohlert_at_sun.com> wrote:
>
> Dave,
> If you are willing to sign the SCA you can provide us with any fix that
> you might find and we maybe able
> to incorporate it into the next release of JAX-RPC 1.1. You can read
> more about the SCA and how to
> contribute at: https://jwsdp.dev.java.net/contributions.html.
>