Not sure if this fits your requirements, but if you want to use HTTP Basic
Authentication **without** having the servlet container manage it for you, try
using:
org.apache.axis.handlers.http.HttpAuthHandler
This class strips out the user name and password from the HTTP Headers
and sets the userna
Hi Kumar,
Other than the HTTP Transport, Axis also provides a JMS Transport and a Mail
Transport.
See the following packages for details:
org.apache.axis.transport.mail
org.apache.axis.transport.jms
So instead of communicating SOAP over HTTP, you would communicate SOAP over JMS
or SMTP/POP3.
A
Hi Dave,
Just FYI, the wsabi4axis open source project allows you to manage your
server-config.wsdd using an intuitive GUI. The GUI is actually a web
application that can run standalone or be integrated within your axis
deployment.
For a demo, check out, http://demo.wsabi.org
Click on "Configur
Hi Jason,
Sorry to contact directly, but didn't want to get too off-topic on the mailing
lists.
What are your requirements for a SOAP Intermediary? Are you looking for Web
Services Management capabilities??
Thanks,
Al
Quoting Jason Judt <[EMAIL PROTECTED]>:
> Hi all,
>
> I was curious about
Hi Marko,
One option is to configure your web service to have a request handler that
captures the incoming request. This handler would grab the SOAP request and
then log it. But I am not sure if that meets your requirement of "before axis
begins to parse them".
To save you some work, the wsabi
Hi Jay,
Are all of the relevant jar files that Axis is dependant on accessible to the
applet to download?? That might be the reason it is working in netbeans and
not in IE.
Al
Quoting Jay Doggett <[EMAIL PROTECTED]>:
> Al,
>
> The interesting thing is, the applet code works when I run
Hi Jay,
OK, it sounds like you do not have a need for a handler, and just want to
connect to the service. Please correct me if I am misunderstanding.
Try the following out
a) extract client-config.wsdd from axis.jar
jar xvf axis.jar org/apache/axis/client/client-config.wsdd
b) place th
Hi Jay,
Here is a client-config.wsdd that you can use as an example for defining a
handler. The handler in this case is configured at the global level, so all
client invocations will invoke this handler.
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/p
As an alternative, server-config.wsdd exists in axis.jar in the RC2
distribution.
jar xvf axis.jar org/apache/axis/server/server-config.wsdd
Al
Quoting Stojan Sljivic - GDS <[EMAIL PROTECTED]>:
> Thanks Christopher.
>
> Regards,
> Stojan
>
> -Original Message-
> From: Hewitt, Christophe
Hi Paul,
This should get you where you want to go
SOAPEnvelopeenv = messageContext.getRequestMessage().getSOAPEnvelope();
SOAPBodyElement e= env.getFirstBody();
Iterator it = e.getChildElements();
while (it.hasNext()) {
}
By iterating thru the child elements you should be a
Hi Jorge,
One option you have is to set up a handler that is invoked before and/or after
your web service method has completed. This handler could inspect the SOAP
envelope to make sure that the response message has been sent "successfully",
but the definition of "successfully" can mean many thin
Hi Andy,
The current release of wsabi4axis project
(http://sourceforge.net/projects/wsabi4axis) has the building blocks for the
auditing capabilities you are looking for. A subsequent release will support
full-blown auditing capabilities. We prioritize new features based on feedback
from the co
Hi Suzy,
The wsabi4axis project at http://sourceforge.net/projects/wsabi4axis has the
functionality that you are looking for. After configuring your web services
with a WSABI Handler, information about each invocation on your web services is
collected and persisted. Using an intuitive GUI, users
13 matches
Mail list logo
