Thankyou all - between all these comments I managed to get it worked out :)
On Fri, 15 Oct 2004 09:02:01 -0700, Dan Ciarniello
<[EMAIL PROTECTED]> wrote:
> Pat Allan wrote:
>
> >Do I need the Axis servlet? I assumed it wasn't necessary.
> >
> >
> Yes, you do need the Axis servlet.
>
> >I didn't
Pat Allan wrote:
Do I need the Axis servlet? I assumed it wasn't necessary.
Yes, you do need the Axis servlet.
I didn't have a web.xml file, so I copied the one in the axis webapp,
and have the following as my only servlet and servlet mapping nodes
(and kept the mime mappings, etc):
TaskWS
I didn't have those handler lines - but having them doesn't seem to
make a difference.
On Fri, 15 Oct 2004 15:37:44 +0200 (MEST), [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
>
> Are you using the URLMapper handler? You should check that it is present
> in your server-config.wsdd. This handler
Do I need the Axis servlet? I assumed it wasn't necessary.
I didn't have a web.xml file, so I copied the one in the axis webapp,
and have the following as my only servlet and servlet mapping nodes
(and kept the mime mappings, etc):
TaskWS
Task Web Services
com.freelancingGod
Are you using the URLMapper handler? You should check that it is present
in your server-config.wsdd. This handler finds the service associated with
the URL sent by your request. Axis needs the service to generate the
WSDL.
That file should contain something like this:
...
...
Pat,
By default, Axis has a mapping, in WEB-INF/web.xml,
that specifies a URI of "/services/*", to get to the Axis servlet
(and, thus, to the services). This is the path below the context root.
It looks like your context root is "taskServices", but I'm not
sure what mapping you have for the Axis
Hi all
I've been scouring this list and the net for an answer to my question
- seems some people have had similar issues, but no fixes.
http://localhost:8181/taskServices/TaskWS is the service. And when I
visit that through a browser, I get:
And now... Some Services
* TaskWS (wsdl)
-Original Message-
From: Satrusalya, Prassana [mailto:[EMAIL PROTECTED]
Sent: Friday, May 07, 2004 9:38 AM
To: '[EMAIL PROTECTED]'
Subject: WSDL autogeneration - xmlns="" in service response
In my response axis sends back the response the following way. Notice the '
x
-Original Message-
From: Satrusalya, Prassana [mailto:[EMAIL PROTECTED]
Sent: Friday, May 07, 2004 9:38 AM
To: '[EMAIL PROTECTED]'
Subject: WSDL autogeneration - xmlns="" in service response
In my response axis sends back the response the following way. Notice the '
x
I had exactly the same problem. To fix it add elementFormDefault="qualified"
to the schema element in your wsdl, and then rerun wsdl2java.
On Friday 07 May 2004 6:38 am, Satrusalya, Prassana wrote:
> In my response axis sends back the response the following way. Notice the '
> xmlns="" ' . .NET
In my response axis sends back the response the following way. Notice the '
xmlns="" ' . .NET does not like it. My WSDL is generated on the fly and I am
using
Simple types. Any idea how to avoid this.
- http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xml
On Mon, 2002-12-02 at 04:32, Raju Gottumukkala wrote:
> Mr Cliffe.
> I have observed that in the wsdl file generated for my java class the
> xsd:type doesn't change once created!
>
> for example if i have created a method which returns String then recompile
> the class to a int method, then the x
looks mysterious.
is my problem also similar to yours..?
From: "Owen Cliffe" <[EMAIL PROTECTED] default ic.uk>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 01, 2002 7:56 PM
Subject: WSDL autogeneration of non-visible classes
> Hi, apologies if this is a duplicate, there are mail
Hi, apologies if this is a duplicate, there are mail issues.
Is there a way of explicitly telling axis to include certain classes in
the WSDL type definition without them being exposed through parameters or
return types of available service methods?
we have been successfully using axis to aut
14 matches
Mail list logo
