The policy you have used enforces to use HTTPS. So you should try the HTTPS
endpoint instead of HTTP.
Thanks,
Thilina
On Thu, Sep 22, 2011 at 8:11 PM, Scott Selvia wrote:
> Thanks for the help but I get the following stack trace when I use Axis2
> 1.6.0 with Rampart 1.6.1. I tried backing down
Hi
It is a bit Confusing in the Documents for WSDL2JAVA /JAVA2WSDL are in 2
versions
Which to be used (under circumstances ) ...Both used to run via ANT ?
1)Ant task with ARGS
...
2)Ant tasks with built in
eg:-
--
View this message in context:
http://old.nabble.com/AXIS2-A
Amila / Axis Group,
I did not get any response on this. Can you please check when you get a
chance.
Here I am trying to explain the problem again. Problem is that axis2 server
on our side ( 1.4 or 1.6) sends response with same name space for all
elements even though they belong to different name
Sorry for the typo on the Rampart version the stack trace was displayed
when I had Axis2 1.6.0 and Rampart 1.6.1
From: Scott Selvia [mailto:ssel...@datamentors.com]
Sent: Thursday, September 22, 2011 10:41 AM
To: java-user@axis.apache.org
Subject: RE: Error Deploying Webservice on Axis2
Hi
I have some POJO Web Services that throws different types of exceptions
(Error, Warning, Security) that are converted into different types of
faults. If I use RPCServiceClient I only get AxisFault and in the detail
attribute I get the XML. Is there a way to easily map this exception to my
exist
I have my project working fine in Eclipse. However, it's not working when I
package it into a jar and run that. I am including all the required
libraries of axis2 and rampart in the jar, because the app will be deployed
via java web start and I can't expect users to install all the libraries on
t
Thanks for the help but I get the following stack trace when I use Axis2
1.6.0 with Rampart 1.6.1. I tried backing down to Rampart 1.5.1 with
Axis2 1.6.0 and I get the same stack trace.
I there an Axis2 config parameter to solve the stack trace below? If
not then I hope the new Rampart is rel
Hi Scot,
There is a known incompatibility between Axis2 1.6.1 and Rampart 1.6.0.
Please try reverting back to Axis2 1.6.0 until Rampart 1.6.1 will be
released. We are planning to release Rampart 1.6.1 soon.
Thanks,
Thilina
On Thu, Sep 22, 2011 at 5:59 PM, Scott Selvia wrote:
> The following ws
The following wsp:Policy block in my services.xml works with Axis2 1.5.5
with Rampart 1.5.1 however with Axis2 1.6.1 and Rampart 1.6.0 I get the
stack trace below the policy block. What has changed and is the policy
block no longer needed?
http://docs.oasis-open.org/wss/2004/01/oasis-200401-ws
Thanks. I'll roll back to 1.6.0 and keep an eye out for the rampart release.
Not to be smart, but is this incompatibility documented anywhere? I know from
when rampart was using x.y version numbers, they seemed to work across multiple
versions of axis (1.5.1, 1.5.2, etc), so I assumed that was s
You will have to wait for Rampart 1.6.1 which will be released soon.
Andreas
On Thu, Sep 22, 2011 at 12:21, Leon Koch wrote:
> Hi,
>
> I am attempting to re-build some server side code + stubs using axis 1.6.1
> and rampart 1.6.0. I am getting the following error:
>
> # wsdl2java.bat -uri Test.
Hi,
I am attempting to re-build some server side code + stubs using axis 1.6.1 and
rampart 1.6.0. I am getting the following error:
# wsdl2java.bat -uri Test.wsdl -o generated -or -p test -ss -sd -ssi -uw
--noBuildXML
Using AXIS2_HOME: C:\bin\axis2-1.6.1
Using JAVA_HOME: C:\Program Files\Ja
12 matches
Mail list logo
