If I specify the -p option at the command line, I can change the package
name with your new version. I was trying to do it exclusively with
custom bindings before, and it didn't work. Perhaps I missed something?
It seems desirable to change the package for generated adapters at the
granularity of the bindings file.
Also, the problem with the unset method turned out to be that I didn't
check for null being passed into the adapter class that I created.
Setting a null value does work as you said. Just as a design suggestion,
it seems that if an xml element or attribute is optional, an unset
method should exist, even if all that method does is pass a null value.
I guess neither of these constitute a bug. Thank you for your support!
Ryan
-----Original Message-----
From: Kohsuke Kawaguchi [mailto:Kohsuke.Kawaguchi_at_Sun.COM]
Sent: Monday, November 06, 2006 11:58 AM
To: users_at_jaxb.dev.java.net
Subject: Re: JAXB Package Solution
Lichtenwalter, Ryan wrote:
> I apologize, but the response you provided to me was unclear. Before
> further questions, I decided to try what I thought you meant. I
> downloaded a new (I think, but I was already using JAXB 2.0 that came
> with the NetBeans SJSAS9 bundle) version of JAXB 2.0 from the
> following
> location:
>
> https://jaxb.dev.java.net/files/documents/51/43091/JAXB2_20061030.jar
>
> I remove my previous installation. I install this version. I
recompile.
>
> The package is still:
> org.w3._2001.xmlschema
> The class is still:
> Adapter1.java
>
> I appreciate the time you gave in your previous response. Please
> advise how I can change the output of the compile so that these names
> are specifiable.
Hmm. I thought I fixed the bug, but I guess you are saying that it
doesn't look like it's fixed.
I'd appreciate a test case to look into. If you can file this as a bug
in
http://jaxb.dev.java.net/issues/ that would be great.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com