axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayachandra Sekhara Rao Sunkara (JIRA)" <>
Subject [jira] Created: (AXIS2-109) Databinding completeness in the stubs that are generated
Date Thu, 28 Jul 2005 12:22:22 GMT
Databinding completeness in the stubs that are generated

         Key: AXIS2-109
     Project: Apache Axis 2.0 (Axis2)
        Type: Improvement
  Components: databinding  
    Reporter: Jayachandra Sekhara Rao Sunkara

We should project stub methods tha are completely agnostic of the databinding mechanism utilized
to generate them.

FYI, I'm copy pasting the issue that was mailed to axis-dev on 28th July 2005

*** Transcript of the mail follows ***

Hi there,
I planned to test a stub based style of invocation with this wsdl [attached below- SimpleTest.wsdl].
Its the wsdl for a webservice which hosts a method of the signature public String echoString(String
inputString); I started with wsdl2java to generate stubs for me. I then set out to write a
test client (this was lacking from wsdl2java artifacts that got generated) that would just
assume as if it was invoking a local method named echoString on the stub. Strangely the method
signature of
echoString(..) in the generated stub is seen to expect an XMLBeans specific EchoStringDocument
kind of object as its input parameter.
This makes us think that data binding is not facilitated to the user fully. User shouldn't
have to bore the onus of creating an EchoStringDocument object and pass it as parameter to
the stub method, at least when he is using the stub based invocation, isn't it? Is this feature
on our wish list or am I missing something!?!

Thank you

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message