As to your questions 2nd and 3rd, Yes it is possible to have
webservices over different protocols, meaning we can publish a
webservice which can work on top of different protocols like SOAP,
RMI-IIOP protocol all simultaneously.
This has been possible 'cause wsdl allows for a definition of a
webser
The access control and username/passwd details are maintained in
perms.lst and users.lst located in axis\WEB-INF folder.
Typical entries in perms.lst are as follows:
user1 WebserviceName1
user2 WebserviceName2
The users.lst would contain entries something like this
user1 password1
user2 p
Hi Patrick,
You can even create the server-config.wsdd with running the following
command(in your console) on your deploy.wsdd which you got to create.
java org.apache.axis.client.AdminClient deploy.wsdd-l
http://localhost:8080/axis/services/AdminService
After the command you will see the output
Well,
I got a solution to it. If we just store the document in the WEB-INF
folder, and then try accessing the document we get the same one which
is stored over there.
The '?' in the URL if we use, it would get AXIS to generate the wsdl
document runtime for us.
Regards
Vinay
Is there any way, by which we can stop axis from generating a wsdl runtime.
So that once I generate a wsdl, I can store it somewhere and everytime
the wsdl is requested from the browser, its the stored wsdl which is
showed.
Regards
Vinay
Hi,
Somewhere I read that for maximum platform neutrality, WSDL uses XML
Schema syntax to define data types. But I couldn't map any of the
datatypes to the XMLSchema syntax.
Like I couldn't find a mention of
"xsd:string" or "xsd:float" on
http://www.w3.org/1999/XMLSchema.xsd
I don't know how to r
You can even try Custom serializers and deserializers to convert the
HashMap into XML, and then the client side of the service can use it
in whatever way it finds it useful.
On Fri, 29 Oct 2004 17:07:25 +1000, Mark Chaimungkalanont
<[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I'm writing a SOAP s
