[ http://issues.apache.org/jira/browse/AXIS2-109?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-109:
-------------------------------------------
Resolution: Invalid
Following my previous comment I would say we are not moving towards the
databind agonstic approach at all! Hence I'm marking this non-issue and
resolving it
> Databinding completeness in the stubs that are generated
> --------------------------------------------------------
>
> Key: AXIS2-109
> URL: http://issues.apache.org/jira/browse/AXIS2-109
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: databinding
> Reporter: Jayachandra Sekhara Rao Sunkara
> Assignee: Ajith Harshana Ranabahu
> Priority: Minor
> Attachments: SimpleTest.wsdl
>
> 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
> Jayachandra
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
