Hello Adrian,

here are two wsdl-files, one for doc/lit and one for rpc/enc. They are both 
generated by java2wsdl:

..\project\..>java org.apache.axis.wsdl.Java2WSDL -l 
http://flak:8080/axis/services/SpServerWS -o ..\wsdl\SpServerWS.wsdl -n 
"urn:SpServerWS" -p"com.iez.spserver.ws" "urn:SpServerWS" -y document -u 
literal com.iez.spserver.ws.SpServerWS 

Here are the java interface and the complex data types as well. I hope it's not 
to much. I don't have posted TestBean2 and SubBean2, because they are quite 
working well (contains only strings). The problems are in getInt, getInts, 
getTestBeans and getTestBean. And of course, I can't create client stubs using 
wsdl2ws.

Thanks for your help.
Falk.

-----Urspr�ngliche Nachricht-----
Von: Adrian Dick [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 2. Juni 2005 18:07
An: Apache AXIS C User List
Betreff: Re: Settings for Java Webservice (used by C++-Client)

Hi,

I, personally, don't work with the Axis Java web services - I use WebSphere as 
my web service provider.  However, there are other developers in this community 
who use axis java for their services.

You mention doc/literal messages, this is what I use, and is definitely more 
thoroughly tested compared to rpc/encoded.
Note:  I see below that you're trying to use rpc/literal - this is not 
currently supported by Axis C++, you will need to choose from doc/literal or 
rpc/encoded.
Based on my experience with websphere, you would need to regenerate the WSDL 
and redeploy the service to make this change (in addition to re-generating the 
client stubs).

If you are able to post your WSDL to this mailing list we can look at why your 
stubs are not being correctly generated, and hopefully someone in the community 
more familiar with axis java will be able to diagnose any server side issues.

Adrian
_______________________________________
Adrian Dick ([EMAIL PROTECTED])


"Falk Sippach" <[EMAIL PROTECTED]> wrote on 02/06/2005 16:16:24:

> Hello,
>
> I need some more help. Is there anybody who has successfully developed 
> an Axis C++ client calling a Java Webservice? At the moment it's not 
> working at all. Are there other products (C++), which work together 
> with Java Axis webservices?
>
> I've read somewhere I should use doc/lit as message style. I've tried.
> First I've generated a wsdl-file with java2wsdl. Then I've created the 
> server skeletons (wsdl2java) and the client stubs (wsdl2ws). But 
> wsdl2ws fails with a not reproducable error:
>
> --------------------
> java.util.NoSuchElementException
>         at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
>         at java.util.HashMap$ValueIterator.next(Unknown Source)
>         at
> org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.addDocumentStyleInputMessageToMe
> thodInfo(Unknown Source)
>         at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.setMethodInfo(Unknown
> Source)
>         at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceInfo(Unknown
> Source)
>         at 
> org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.generateWrappers(Unknown
> Source)
>
>         at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(Unknown Source)
>
> Code generation failed. Please see errors above.
> --------------------
>
> If I use rpc/lit, the stub code generation succeeds. But the soap 
> messages look like this:
>
> --------------------
> <getStringResponse>
>    <getStringReturn>test string</getStringReturn> </getStringResponse>
> --------------------
>
> There is no type definition and the client can't read any string.
>
>
> It works, if I use rpc/encoded. But then I have the problem with 
> URI_XSD and URI_ENC (ok, I can fix it with the patch). And I can't get 
> int values or complex types with ints inside. It still doesn't work in 
> the
> 1.6 alpha from June 1st, 3 a. m. Maybe in the next nightly build it 
> will work, because Adrian has changed it yesterday (after the last 
> nightly build?).
>
> What may I do wrong? Please help.
>
> Thanks,
> Falk.

Attachment: SpServerWS_rpc_enc.wsdl
Description: SpServerWS_rpc_enc.wsdl

Attachment: SpServerWS_doc_lit.wsdl
Description: SpServerWS_doc_lit.wsdl

Attachment: SpServerWS.java
Description: SpServerWS.java

Attachment: SubBean.java
Description: SubBean.java

Attachment: TestBean.java
Description: TestBean.java

Reply via email to