RE: JAX-WS client and service with Rampart module for signing messages

policy errors:make sure your policy.xml contains userCertAlias element e.g.client2 missing ServiceClass in services.xml for example: fu.Baris fu.Bar java class on your classpath http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2F

RE: doc/literal/wrapped soap response with jaxb binding

Thanks! Ruey -Original Message- From: java-user-return-86732-RUEY-JUIN.CHANG=saic@axis.apache.org [mailto:java-user-return-86732-RUEY-JUIN.CHANG=saic@axis.apache.org] On Behalf Of Andreas Veithen Sent: Tuesday, June 26, 2012 10:25 AM To: java-user@axis.apache.org Subject: Re: do

RE: Axis2 generating the wrong XML namespace

Good Evening Oli Looks like we'll need to file a JIRA requesting support for /xsd in services.xmlhttps://issues.apache.org/jira/secure/Dashboard.jspa depending on who is available either Sagara, Andreas or myself will address the item Thanks for using Axis! Martin Gainty

Re: JAX-WS client and service with Rampart module for signing messages

Hi Megadeth, Please find some answers inline. On Tue, Jun 26, 2012 at 1:15 PM, Megadeth wrote: > > Hi, > > I created java project. It is client of my jax-ws web service and I use it > for signing messages. > I renamed rampart.mar to rampart.jar and put it into classpath of java > project (also a

Re: doc/literal/wrapped soap response with jaxb binding

This is a bug: AXIS2-5147. I fixed that one just yesterday :-) Andreas On Tue, Jun 26, 2012 at 7:20 PM, Chang, Ruey-Juin wrote: > Hi, > > > > I am using Axis2 1.6.2 with jaxb data binding.  I noticed that the soap > response message always returning the request element instead of response > elem

doc/literal/wrapped soap response with jaxb binding

Hi, I am using Axis2 1.6.2 with jaxb data binding. I noticed that the soap response message always returning the request element instead of response element as expected. I even tried the wsdl file from the 'version' service but switched to use jaxb binding, still got and not . However, prog

Re: Axis2 generating the wrong XML namespace

Hi Martin, Thanks for that, I was hoping to be able to specify the namespace explicitly rather than have Axis2 generate one. Do you happen to know how to do this? Thanks for your help. Regards, Oli On 26/06/12 14:55, Martin Gainty wrote: yes it is hardwired: package org.apache.axis2.des

RE: Axis2 generating the wrong XML namespace

yes it is hardwired: package org.apache.axis2.description.java2wsdl; public class Java2WsdlUtils { public static final String SCHEMA_NAMESPACE_EXTN = "/xsd"; String DEFAULT_TARGET_NAMESPACE_PREFIX = "axis2";public static StringBuffer schemaNamespaceFromClassName(String packageName, C

Axis2 generating the wrong XML namespace

Hi there, Axis2 seems to strip off the "www." and tag on "xsd" to the XML namespaces of elements. E.g., "http://www.example.com/"; becomes "http://example.com/xsd";. The /xsd variant doesn't appear at all in any of my source code nor any associated assets and is completely generated by Axis2

JAX-WS client and service with Rampart module for signing messages

Hi, I created java project. It is client of my jax-ws web service and I use it for signing messages. I renamed rampart.mar to rampart.jar and put it into classpath of java project (also addressing and rahas mars). I am not sure if this is correct, but it works for me. In client I put this: