Hi,
We tried to reproduce this problem with Windows XP, but in our
environment it worked. "jaxb-xjc.jar" has a manifest entry that look for
../../jwsdp-shared/lib/jax-qname.jar. Although it was broken up by line
break, Java VM doesn't seem to be affected by it.
When I renamed it to jax-qname.ja_, if starts to exhibit the problem you
mentioned (ClassNotFoundError for javax.xml.namespace.QName)
By default, JWSDP will install jax-qname.jar into the abovementioned directory,
so it should be able to find the jar file. Is there any chance you moved
those files, or can you think of any other potential step we need to
take to reproduce the problem?
I'm also curious if Mark Brouwer experienced the same problem when he
invoked jaxb-xjc.jar directly. Mark?
regards,
--
Kohsuke KAWAGUCHI 408-276-7063 (x17063)
Sun Microsystems kohsuke.kawaguchi_at_sun.com