try to generate the code with ADB binding (i.e the defult) and using -b (for
backwork compatibility) option
On 5/7/07, Axel Bock <[EMAIL PROTECTED]> wrote:
Hi Paul,
thanks for that. I just learned that our decision for Axis1 had other
reasons, I just assumed it was compatibility with 1.4. One of those things
you "think" you know ... :-) .
still, switching to Axis2 is not a good option, cause the complete project
works with 1.4 right now, and that would mean a major rewrite in the final
development phase. Not good, no time for that. Unless Axis2 guarantees that
the stubs are identical to the ones from Axis1, which I don't actually
believe.
Can I - somehow - define a custom mapping of these data types, or the
wrapping element? I could parse that manually via DOM for example ... but I
don't know how ...
Thanks & greetings,
Axel.
On 5/7/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> Axel
>
> Axis2 is 1.4 compatible.
>
> Paul
>
>
> On 5/7/07, Axel Bock < [EMAIL PROTECTED]> wrote:
> >
> > Hi Anne,
> >
> > I am sorry. I forgot to mention that Axis2 is not an option for this
> > project, becasue we need Java 1.4 compatibility.
> >
> > Do you have any other ideas, maybe? :-)
> >
> >
> > Greetings & thanks,
> > Axel.
> >
> >
> >
> >
> > On 5/6/07, Anne Thomas Manes <[EMAIL PROTECTED] > wrote:
> > > Try using Axis2 with the XMLBeans databinding.
> > >
> > > On 5/4/07, Axel Bock < [EMAIL PROTECTED]> wrote:
> > > > Hi list,
> > > >
> > > > Using Axis 1.4 I ran into a very annoying problem, based on this
> thing
> > in my
> > > > web service schema:
> > > >
> > > > <element name="SignDocumentResponse">
> > > > <complexType>
> > > > <sequence>
> > > > <element ref="C:Status"/>
> > > > <element name="DocumentList" minOccurs="0">
> > > > <complexType>
> > > > <choice maxOccurs="unbounded">
> > > > <element name="Document" type="base64Binary"/>
> > > > <element name="Deselected"/>
> > > > </choice>
> > > > </complexType>
> > > > </element>
> > > > </sequence>
> > > > </complexType>
> > > > </element>
> > > >
> > > > Now every time axis tries to parse the answer with more than one
> element
> > in
> > > > the DocumentList type I get the following error:
> > > >
> > > > No deserializer for
> > > >
> >
{http://www.w3.org/2001/XMLSchema}anyType<http://www.w3.org/2001/XMLSchema%7DanyType>
> >org.xml.sax.SAXException
> > :
> > > > No deserializer for {
> > > >
http://www.w3.org/2001/XMLSchema}anyType<http://www.w3.org/2001/XMLSchema%7DanyType>
> > > > I found a post concerning that topic back from 2002, which
> basically
> > said
> > > > "bad luck, axis does not do this". (see here:
> > > >
> > http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200204.mbox/[EMAIL
PROTECTED]
>
> > > > ).
> > > >
> > > > I tried to change the choise(0..n) thing to a
> sequence(0..n)-->choice
> > thing,
> > > > or a sequence(1)-->choice(0..n) thing, but both did not help. I
> had a
> > look
> > > > into the stubs and they always look the same - they only seem to
> expect
> > ONE
> > > > sub-element under DocumentList.
> > > >
> > > >
> > > > This is ... well, kind of mission-critical for us here, so I would
> be
> > > > thankful for every suggestion.
> > > >
> > > >
> > > > cheers & thanks in advance,
> > > > Axel.
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Amila Suriarachchi,
WSO2 Inc.
