isNil and setNil methods are not always generated on nillable element

[glassfishrobot]

When the schema listed in the URL is compiled there is no isNil and setNil
method defined in the interface for the element multicast-interfaces. There is
another element in the schema that is nillable (the member-group element) and
the interface generated for that element gets a isNil and setNil method. The
strange thing is that when I also copy the member-group element to sequence of
the service-instance element that xjc refused to generate the isNil and setNil
method for that element too.

The schema has been validated with XMLSpy and the IBM Schema Quality Checker and
appears to be OK.

In case the binding files are required (this schema also includes a second
schema) please contact me to provide them.

The actual version of JAXB is 1.0.4 because JSWDP1.5 is not listed in the bug
system.

Environment

Operating System: All
Platform: All
URL: http://www.cheiron.org/schema/seven-config.xsd

Affected Versions

[JWSDP1.5 (JAXB1.0.4)]

[glassfishrobot]

Reported by marbro

[glassfishrobot]

Was assigned to jaxb-issues

[glassfishrobot]

ryan_shoemaker said:
Please attach your binding files.

[glassfishrobot]

marbro said:
Created an attachment (id=23)
zip file containing the bind files in the build directory, also contains some other files that are referred in the xjc task

[glassfishrobot]

File: jaxb.zip
Attached By: marbro

[glassfishrobot]

kohsuke said:
marked the correct version.

[glassfishrobot]

kohsuke said:
fixed in the 2.0 thread.

[glassfishrobot]

marbro said:
I may hope that this is also going to be fixed in the 1.0 branch as the
requirements (and licensing conditions) for JAXB 2.0 prevent us from using it
for a long time. As the original submitter of this bug (commercial user) this
problem is not resolved for me.

[glassfishrobot]

anandvallam said:
Fixing in 1.0 will help lot of users as thats the version used in production
releases. It may take a while before anyone really uses 2.0 - i.e works on
jdk1.5, which is a major road block for App server users as most of the app
servers won't support jdk1.5 yet.
Conclusion is that these bugs should be fixed in 1.0 to be more helpful for the
users.

[glassfishrobot]

Marked as fixed on Friday, April 15th 2005, 12:39:52 am

[glassfishrobot]

This issue was imported from java.net JIRA JAXB-41