Hello,
I find it very useful to generate a WSDL and then automatically create the
code from it.
However, when I need to update my web service (add new function / parameter
to an existing function) - is it possible to only update the WSDL and then
synchronize the code against it?
Hello,
When I use the eclipse (GUI) wizard to generate code from my wsdl file
(right clicking on the wsdl file, choosing Web Services and then Generate
Java bean Skeleton) when I press the next button and get to the Axis2 Web
Service Skeleton Java Bean Configuration screen the service name, port
Hello,
I would like to be able to log all the parameters given to my WS function.
To do so in the most generic way, I was wondering if there is any way to
iterate all input parameters from the MessageContext or anything similar.
For example, suppose my WS exposes a function called test
Hi,
I have set up a web service that upon error throws an exception as fault.
The web service is accessible through tomcat by using my web browser.
Is there any way to have tomcat (I assume it is in charge of this part) not
display the stack trace, in case my service raises a fault?
.
Anyone familiar with this issue?
From: Yoav Naveh [mailto:y...@contextin.com]
Sent: Wednesday, February 04, 2009 11:26 AM
To: axis-user@ws.apache.org
Subject: not showing stack trace when accessing the web service via browser
Hi,
I have set up a web service that upon error throws
(getSOAPFactory(msgContext), your_func_nameResponse,
false);
From: Yoav Naveh [mailto:y...@contextin.com]
Sent: Monday, February 02, 2009 9:55 AM
To: axis-user@ws.apache.org
Subject: Getting all parameters of the request
Hello,
I would like to be able to log all the parameters given to my WS
Hi,
I throw a custom exception (fault) in my WS (axis2, tomcat)
This works fine, but in my log4j log file I see for each time I throw an
exception the following log message: (the server side log file)
ERROR http-80-16 org.apache.axis2.engine.AxisEngine error message here
Why is this counted as
My web service reports errors using exceptions (which are well defined in
the wsdl file)
This seems to work ok, but there is an annoying side-effect, where for each
thrown exception, an error message appears in my log file:
ERROR http-80-16 org.apache.axis2.engine.AxisEngine error message here
Hello,
I have a WS using axis2 and tomcat 6.
Sometimes, usually under high load of requests from clients, the web
service writes following log error messages:
org.apache.axis2.transport.http.CommonsHTTPTransportSender - name
cannot be null!!
org.apache.axis2.engine.AxisEngine - name cannot be
