Re: Stockquote DynamicInvocation: Cannot get Object part 'Result'.

Hi all,

I still have the problem....

java clients.DynamicInvoker samples/simplesoap/StockquoteSOAP.wsdl getQuote IBM
Reading WSDL document from 'samples/simplesoap/StockquoteSOAP.wsdl'
Preparing WSIF dynamic invocation
Executing operation getQuote
Result:
org.apache.wsif.soap.fault.object=java.net.ConnectException: Connection timed
out

Done!

I use the lastest CVS with new endpoints.
Where can I find these endpoints ? I searched on xmethods web site but I found :

http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx
This endpoint doesn't run better.

There is a very big delay between "Executing operation getQuote" and the display
of the result, is it caused by the search of the web service ?
I used getQuote method on xmethod web site, it runs successfully and and it is
very fast.

Regards,
Charles




Aleksander Slominski wrote:

> Daniel,
>
> this error is definitely not intuitive!
>
> i have fixed DI now in CVS so you get this for invalid service address:
>
>     Reading WSDL document from
> 'C:\Forge\ws-apache-cvs\ws-wsif\java\samples\simplesoap\StockquoteSOAP.wsdl'
>     Preparing WSIF dynamic invocation
>     Executing operation getQuote
>     Result:
>     org.apache.wsif.soap.fault.object=java.net.ConnectException:
> Connection refused: connect
>
> if you still have those problems please reopen issue:
> http://nagoya.apache.org/jira/browse/WSIF-62
>
> thanks,
>
> alek
>
> Daniel da S. Lacerda wrote:
>
> >Hi gurus, I have something that must serve you.
> >
> >I was getting the following message when trying to use my first WSIF
> >example :)
> >
> >$ java clients.DynamicInvoker
> >build/samples/simplesoap/StockquoteSOAP.wsdl getQuote IBM
> >
> >
> >>Reading WSDL document from
> >>
> >>
> >'build/samples/simplesoap/StockquoteSOAP.wsdl'
> >...
> >
> >
> >>Exception in thread "main" org.apache.wsif.WSIFException: Cannot get
> >>
> >>
> >Object part 'Result'. No parts are set on the message
> >
> >After controlling the classpath a hundred times and looking resources on
> >the web (where I found people with the same unsolved problem) I thought
> >that maybe xmethods had inadvertently changed the soap endpoint. So, I
> >made some research and changed the the line in the wsdl file:
> >
> ><soap:address location='http://66.28.98.121:9090/soap'/>
> >for
> ><soap:address location='http://64.124.140.30:9090/soap'/>
> >
> >And voilà ! It works.
> >
> >The first IP still doesn't ping. Sorry if I published the comment in the
> >wrong place, I was afraid putting this on bugzilla was not very
> >appropriate, and maybe other people are getting crazy now for this as I
> >was, they should be informed :).
> >
> >Regards,
> >Daniel Lacerda
> >
> >
> >
>
> --
> The best way to predict the future is to invent it - Alan Kay