In doc/lit there is no spoon - er - I mean there is no notion of inout, in, out or whatever. Those are entirely rpc concepts and have no bearing in doc/lit (wrapped or otherwise).
Plenty of folks differ on this - which is why even at this point interop and tools still blow - but there is a camp that feel that wrapped should be the way you do everything. That might be overstating it a bit but it should be the default/common practice.
<mini-rant>
This is all just like the various function calling conventions of C, C++, Java, FORTRAN, MSIL etc. Debate over whether the calling function should clear the stack or the called function should clear the stack both have merit but its better to have one method so I don't have to keep in mind what convention is in place every time I want to call a function! In that way what if we all just agreed to use Wrapped doc/lit all the time and were done with it? Imagine how much simpler the design choices and how much better the tools and interop would be! Then we could move on from getting point to point services limping to fully distributed composite apps.
</mini-rant>
Jim Murphy Mindreef, Inc.
Shantanu Sen wrote:
You should use the wrapped mode if you have more than one parameter in the service end-point. Typically, plain doc-lit should only be used if there is one parameter in end-point.
Can anyone comment on how the WSDL should be generated if there are 2 parameters in a method, where one parameter is an 'inout' parameter? I believe we should still use 'wrapped' mode, right?
Shantanu
--- David Thielen <[EMAIL PROTECTED]> wrote:
I just tried to do doc/literal (not wrapped) with an add method (two int's in, one returned) and it failed. That has to be a known bug.
- dave
-----Original Message-----
From: Shantanu Sen [mailto:[EMAIL PROTECTED] Sent: Monday, April 26, 2004 5:20 PM
To: [EMAIL PROTECTED]
Subject: RE: Have doubts about Doc/Lit with axis
I think it will be a great help to all of us if you could file a bug with your specific test-case.
I disagree with your statement that 'it appears to be totally broken'. I have successfully used doc-lit - both wrapped and non-wrapped - with the current axis src code. But clearly my test cases do not contain the stuff that is causing this bug to surface.
The more bugs we find and file with specific use cases, the more robust the 1.2 version will be. As it has been pointed out, these guys are really doing a commendable job in fixing the bugs.
Shantanu
--- David Thielen <[EMAIL PROTECTED]> wrote:
I didn't post a bug because it appears to be
totally
broken and therefore I am assuming that numerous bugs have already been posted.
- dave
-----Original Message-----
From: Nelson Minar [mailto:[EMAIL PROTECTED] Sent: Monday, April 26, 2004 12:29 PM
To: [EMAIL PROTECTED]
Subject: RE: Have doubts about Doc/Lit with axis
David Thielen said:
I tried and tried and tried to get doc/literal
to
work - and finally gave
up. I think it just has too many problems still.
Joe Rattz said:
Dave, I had a lot of problems too, specially with
1.2 beta, so I reverted
back to 1.1. I know I have seen a lot that makes
its support of doc/lit
look inadequate, but once I finally got the right
WSDL, it did work.
Could you please, please file bug reports about
the
problems you're seeing? The Axis team is doing a great job of
fixing
bugs as they get 1.2beta ready for a full 1.2 release. They're
doing
free work for you! All you have to do is file a meaningful problem report.
Information about filing bugs is here: http://ws.apache.org/axis/bugs.html
I've been very impressed with how fast bugs I file are fixed.
PS - for what it's worth, Axis 1.2 beta is working well for me with document/literal wrapped services.
