This week's book giveaway is in the HTML Pages with CSS and JavaScript forum.
We're giving away four copies of Testing JavaScript Applications and have Lucas da Costa on-line!
See this thread for details.
Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

references and axis code generation

Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I'm trying to build a web service that has a complex XML document as input. In that XML document I have some elements referencing each other, something like this for example:

I defined these references in my WSDL file using key and keyref elements. I would have loved it if axis would now use this to generate a Thing reference in my OtherThing class, like this:

But unfortunately this isn't happening Axis is just generating the simple fields and I have to resolve the reference myself. I'm wondering now: is this really not possible in Axis at the moment, or is there a chance I'm doing it wrong? Anybody have a clue about this?

Many thanks,
[ May 03, 2005: Message edited by: Jan Vandernoot ]
Jan Vandernoot
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've been doing some research and this is what I've come up with:
  • when using an 'encoded' SOAP binding you can use ID and HREF, which seems to be supported by Axis (the HREF seems to be important when working with attachments in SOAP)
  • 'encoded' automatically means RPC/encoded as document/encoded is not supported by the JAX-RPC specification and generally not well understood
  • documented/literal seems to be the recommended SOAP binding, as it has the most support
  • this means I can't use ID/HREF and should resolve references myself

  • Comments anyone?

    Don't get me started about those stupid light bulbs.
      Bookmark Topic Watch Topic
    • New Topic