Try passing an explicit ConfigurationProvider into the Service constructor -
for instance, use the XMLStringProvider and custom WSDD. Alternately you
could whip up a custom provider which directly deploys whatever you need.
Or we could build a URLConfigurationProvider which sucks the desired WSDD
over from the applet's home host.
--G
> -----Original Message-----
> From: Doug Davis [mailto:dug@us.ibm.com]
> Sent: Wednesday, December 12, 2001 10:20 AM
> To: axis-dev@xml.apache.org
> Subject: Axis in an applet
>
>
> If Axis (client) is running in an applet it dies because we
> try to access
> the file system looking for the config file - which of course
> you can't do
> in an applet. I figure we don't just want to catch the
> exception and hide
> it from people, so what are our options? Will the JNDI stuff recently
> added help at all here?
> -Dug
>
|