axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Sosnoski <>
Subject Re: Rationale for Id and IDRef types?
Date Wed, 03 Mar 2004 18:56:37 GMT
I'm really only interested in running some tests using Axis, so I'll 
just code around the issue for my purposes. FWIW I'd imagine what would 
be involved in fixing this would be to change WSDL2Java to generate an 
object reference for the IDREF, change the deserialization handling to 
track IDs and fill in the object references, and change the 
serialization handling to ignore the IDREF object references. The only 
tricky parts are first that the IDs can be forward references, and 
second that the code may want to check for duplicate/undefined IDs (at 
least for undefined IDs when deserializing).

  - Dennis

Tom Jordahl wrote:

>Sure sounds like these didn't get hooked up when ID and IDREF got checked in
>as XML Schema types.
>A patch to implement this would be welcome.
>Tom Jordahl
>-----Original Message-----
>From: Dennis Sosnoski [] 
>Sent: Tuesday, March 02, 2004 4:59 PM
>To: axis dev
>Subject: Rationale for Id and IDRef types?
>When I generate code from a doc/lit WSDL that includes ID/IDREF links I 
>get instances of the org.apache.axis.types.Id and 
>org.apache.axis.types.IDRef classes in my generated data objects. These 
>don't appear to do anything useful, at least not in the sense of linking 
>the IDREF to the ID (the whole point of using these types in XML).
>The JAX-RPC RI treats ID and IDREF as simple strings unless an optional 
>flag is used in the code generation (resolveidref), in which case 
>they're converted into object id and reference (so the ID values are 
>used as identifiers for objects, and the IDREFs become java.lang.Object 
>references). This is the way I'd expect these to be used in Java. Are 
>there plans to implement this functionality in Axis? I don't see any 
>relevant options listed in the 1.1 alpha WSDL2Java list.
>  - Dennis

View raw message