I'll try that and let you know what the results are.
Rich
--- In [EMAIL PROTECTED]ups.com,
"Franck de Bruijn"
<franck.de.bruijn@...> wrote:
>
> Have you tried to access the wsdl and call the webservice operation from
> another webservice client than Flex?
>
>
>
> The tool I always use is: http://www.soapui.org/jnlp/1.5/soapui.jnlp
(this
> is a webstart link; if you click it, and you have Java installed on your
> machine it should start automatically).
>
>
>
> Cheers,
>
> Franck
>
>
>
> _____
>
> From: [EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
> Behalf Of richmcgillicuddy
> Sent: Friday, July 28, 2006 9:43 PM
> To: [EMAIL PROTECTED]ups.com
> Subject: [flexcoders] Re: WebService Call
>
>
>
> Yes,
>
> I see the definition but with most XML parse errors (not just flex),
> the error messages are difficult to track down. It is telling me that
> it cannot add the node "". I'll get the exact error message and
post
> it later tonight. I'd prefer to use a WebService rather than an Service.
>
> Rich
>
> --- In [EMAIL PROTECTED] <mailto:flexcoders%40yahoogroups.com>
ups.com,
> slangeberg <slangeberg@> wrote:
> >
> > So when you point your browser to: http://localhost:
> <http://localhost:9126/SOAP>
9126/SOAP
> > you are seeing the WSDL definition?
> >
> > Scott
> >
> >
> > On 7/28/06, richmcgillicuddy <rich@> wrote:
> > >
> > > Thanks for the pointers, they are really helpful. I have my own
app
> > > server and can tell that the flex application calls it, tries to
> > > retrieve the wsdl file and then in flex it tells me that there
is an
> > > XML parsing error in the wsdl file. It this point, I am leaning
> > > towards using simple XML since I can generate that if needed.
Other
> > > than download and testing SOAP wsdl validators and making sure
it is
> > > standard, i think the only other option is the straight XML.
> > >
> > > Rich
> > >
> > >
> > > --- In [EMAIL PROTECTED] <mailto:flexcoders%40yahoogroups.com>
ups.com
> <flexcoders%40yahoogroups.com>,
> > > slangeberg <slangeberg@> wrote:
> > > >
> > > > Yeah,
> > > >
> > > > Try something more like (I'm not sure what your 'FlexData'
> object was
> > > > supposed to refer to... ):
> > > >
> > > > <mx:..sometag >wsTest.getData()"">
> > > >
> > > > <mx:WebService
> > > > id="wsTest"
> > > > wsdl="http://localhost:
<http://localhost:9126/SOAP>
9126/SOAP"
> > > > fault="{trace(-1);}"
> > > > result="{trace(1);}"/>
> > > >
> > > > </mx:...sometag>
> > > >
> > > >
> > > > On 7/26/06, richmcgillicuddy <rich@> wrote:
> > > > >
> > > > > I have a simple web service calling a SOAP web service
on my
local
> > > > > machine. The call looks like:
> > > > >
> > > > > <mx:WebService id="wsTest"
> > > > > wsdl="http://localhost:
<http://localhost:9126/SOAP>
9126/SOAP"
> > > > > load="wsTest.FlexData.getData()"
> > > > > fault="trace(-1);" />
> > > > >
> > > > > It seems to hang waiting for localhost and if I let it
wait long
> > > > > enough, it will give me the following error:
> > > > >
> > > > > ReferenceError: Error #1069: Property getData not
found on
> > > > > mx.rpc.soap.mxml.Operation and there is no
default value.
> > > > > at Step2/__wsTest_load()
> > > > > ...
> > > > >
> > > > > On the Web Server side, I am looking for client
connects from
> flash
> > > > > and do not seem to get even the client connect. Any
ideas?
> > > > >
> > > > > Is there anything that looks odd with the WebService
statement?
> > > > >
> > > > > Rich
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > : : ) Scott
> > > >
> > >
> > >
> > >
> >
> >
> >
> > --
> >
> > : : ) Scott
> >
>