axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "keith chapman" <>
Subject Re: Rampart - is it usable on client-side when you don't control server side
Date Thu, 02 Oct 2008 01:18:50 GMT
You should use rampart 1.3 with axis2-1.3 and rampart 1.4 with axis2-1.4 or
axis2-1.4.1. I answered your JMS question on the other thread. And no
rampart does NOT depend on JMS.


On Thu, Oct 2, 2008 at 5:25 AM, Steve Cohen <> wrote:

> After all day futilely trying to use Rampart I have some simple questions
> that maybe the developers can answer:
> What versions of Axis2 is Rampart compatible or incompatible with?  In
> particular is it compatible with Axis2-1.4?  If not what must be done to
> make it so?
> What undocumented dependencies does Rampart have?  Why does client code
> blow up because of
> java.lang.NoClassDefFoundError: javax/jms/BytesMessage
> Does Rampart use JMS?
> (Note: this happens with the out of the box sample client code in
> sample03).
> What I am looking for is a simple solution that allows me to take a
> vendor-provided WSDL for a Web Service that uses basic HTTP authentication,
> and quickly generate a usable client for it.  All documentation I have seen
> for Axis/Rampart seems to contain an unhealthy intermingling of client-side
> and server-side code with the client-side code always something of an
> afterthought.  This negates the whole idea of Web Services.
> Is there a sample out there or an article that shows how to work with Axis2
> in the scenario where the developer is in control only of the client, not
> the server?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.


View raw message