Missing tag in SOAP Response object

Question

Currently running WebLogic 8.1 SP2 (legacy system, unable to upgrade to newer versions).
Looking at a SOAP Response from a Web Service call, it's notable that there are some missing tags in the response. When the same call is made through an RMI invocation, the data is there, so it appears that it's being set correctly. The obvious answer is that it's an XML serialization problem, but there are no errors in any log files and the Codec classes for a working class and non-working class look identical.
Let me explain better
We have essentially:
Class foo {
public int getID();
public void setID(int);
Class bar1 extends foo {
//other stuff
Class bar2 extends foo {
//other stuff
The Schema defines the ID field as minOccurs="1" (the default).
The response coming from the server will look something like this:
<foo>
<bar1>
<ID>TheID</ID>
...other stuff...
</bar1>
</foo>
However, if the returned object is of the other type...
<foo>
<bar2>
...other stuff, but no ID...
</bar2>
</foo>
The classes and service are being generated from a WSDL and XSD files, searching through the value and codec classes shows no fundamental difference between the implementation of the two subclasses, yet one shows the ID, and the other doesn't.
Anyone have any idea where to look to start narrowing down the problem? This has us completely baffled.

Answer 1

I guess I'll answer my own question since I've since been able to solve it in the hopes that it will someday help someone else.
Short answer: There is a bug in WebLogic 8.1 SP2 which generates the isPropertySet(int index) method in the Codecs incorrectly for certain subclasses.
Using the foo example from the original question
class foo;
class bar extends foo;
class dot extends foo;
If dot has additional properties, the Codec will be generated incorrectly. They should look like:
<pre>
protected boolean isPropertySet(Object my_obj, int idx) {
if (idx < SUPERPROP_COUNT) return super.isPropertySet(my_obj,idx);
idx -= SUPERPROP_COUNT;     
Dot typed_obj = (Dot) my_obj;
switch(idx) {
case 0:
return typed_obj._isSetAdditionalProperty();
</pre>
...etc
What it actually does look like is...
<pre>
protected boolean isPropertySet(Object my_obj, int idx) {
Dot typed_obj = (Dot) my_obj;
switch(idx) {
case 0:
return typed_obj._isSetAdditionalProperty();
</pre>
...etc
so attempting to get the eariler properties of the super class from an instance of the sub class returns erratic results depending on whether properties of the subclass were set.
Anyway, this was fixed in SP3 or 4, and there was a patch available to fix it in SP2 as well. Good luck if anyone else happens to run into this problem.