Using the 6 Apr 2006 snapshot, I generated the client stub with
WSDL2Java -s -uri enterprise.wsdl
I use the stub to call login
SoapStub s = new
SoapStub("http://www.salesforce.com/services/Soap/c/7.0";);
Login l = new SoapStub.Login();
l.setUsername("[EMAIL PROTECTED]");
l.setPassword("pwd");
SoapStub.LoginResult lr = s.login(l).getResult();
System.out.println("sid=" + lr.getSessionId());
But the generated request is missing the username element (also there
seems to be extra ns declarations)
POST /services/Soap/c/7.0 HTTP/1.1
User-Agent: Axis/2.0
SOAPAction: ""
Host: www.salesforce.com
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8
141
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header
/><soapenv:Body><ns2:login
xmlns:ns2="urn:enterprise.soap.sforce.com"><ns2:password
xmlns="urn:enterprise.soap.sforce.com">pwd</ns2:password></ns2:login></soapenv:Body></soapenv:Envelope>
0
As i'm bulding a client, not a server, the -ss -sd -g options are no
good to me.
Cheers
Simon
On Wed, 29 Mar 2006 16:23:52 -0500, in soap you wrote:
>http://cvs.apache.org/dist/axis2/nightly/
>
>On 3/29/06, Simon Fell <[EMAIL PROTECTED]> wrote:
>> I'll try it out, are there nightly builds available ?
>>
>> Thanks
>> Simon
>>
>> -----Original Message-----
>> From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, March 29, 2006 11:32 AM
>> To: [email protected]
>> Subject: Re: [jira] Resolved: (AXIS2-515) WSDL2Java generates
>> uncompilablecode.
>>
>> On Wed, 2006-03-29 at 11:37 +0100, Ajith Harshana Ranabahu (JIRA) wrote:
>> > [ http://issues.apache.org/jira/browse/AXIS2-515?page=all ]
>> >
>> > Ajith Harshana Ranabahu resolved AXIS2-515:
>> > -------------------------------------------
>> >
>> > Resolution: Fixed
>> >
>> > I've generated the code and tested it against the salesforce service.
>> > I got the successful answers and I'm confident that if we write an
>> > application to utilize salesforce, the generated stub can be used
>> > effectively for that.
>>
>> Excellent! Simon, can you verify this please? It would be idea if you
>> could check it out now rather than waiting for the next release.
>>
>> > Here are the answers for the other questions
>>
>> > a) This is the default behavior. I agree that having a 5 Mb source
>> > file is hard to handle but I've made sure that it works and the can
>> > be easily compiled through the generated build file. You can use the
>> > -ss -sd -g option set to completely expand the generated classes.
>>
>> +1.
>>
>> > c). Yes. This seems to be the case and I'll have a look at this.
>> > Anyway I think this is better marked as a seperate Jira to keep track
>>
>> > of it
>>
>> OK.
>>
>> > d) Unfortunatley yes.
>>
>> Is that removable??
>>
>> > e) The reason is that you have elements and types in the same name.
>> > Since ADB generates classes for both toplevel elements and types, it
>> > gives unique names to avoid conflicts.
>>
>> Can we improve this? In particular, it seems to me we only need to
>> generate a class for a type if its used in a non-top level element. If
>> its a top level elem then we generate the class for the elem ..
>>
>> Maybe its too smart of an optimization but would appreciate your
>> thoughts.
>>
>> Sanjiva.
>>
