Re: Failed to build Axis2 1.5 using Maven

The trunk builds properly with the default poms without needing to specify any repos. Is there any reason as to why you are using a specific repo? If not, use the default pom and it will build without a problem without any repo problems. On Wed, May 5, 2010 at 1:15 AM, thinke365 wrote: > > the r

axis2-wsdl2code maven plugin

I'm trying to use this maven plugin and it's generating the XmlBeans files properly, as far as I can tell, but when I try and run a minimal unit test it's blowing up with a missing class, TypeSystemHolder, error. Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to lo

Failed to build Axis2 1.5 using Maven

the repository i used is http://repo1.maven.org/maven2/. mvn compile at the root directory with pom.xml, it fails after 1 minute compilation. the error suggest that some packages are not found in the repository. so is there any repository i can found all the packages i need？(so with one simple

RE: New line is appended on result

whatever utilities..editors or StaxParsers you decide to work with must ALL support the encoding you are currently implementing i dont work with CJK charset here (thankfully) so i'll leave it up to those engineers from the pacific rim to determine the correct encoding that will work in your are

RE: New line is appended on result

Mr. Ducheol Sorry to hear solution suggested not worked. In my case this problem occurred in my binary attachment where CR was added for certain sized binary attachment. I think your problem is some thing more structural & may be easy. CR is appended to every XML element pair. Please

IllegalArgumentException when changing fault-y soap-envelope from within a handler

Hi, (I'm using axis2-1.4.1 due to jdk-1.4 requirement) In an axis2-client, i need to replace the SOAPEnvelope from within a In-Fault Handler. But i'm getting the next exception: java.lang.IllegalArgumentException: The MessageContext does not have an associated SOAPFault. at org.apache.a

RE: New line is appended on result

Hi Yogesh. Thanks to answer my question. I test it again after change axiom library, but same issue happen. Below is environment we use. WAS : jBoss-4.0.2 Axis2 : Axis2-1.3 ( Some error message is displayed during deploy axis2 if we use current axis2 version. So I choose minor version. ) WS Me

Re: namespace mismatch problem

I've solved it by adding this line: element.declareDefaultNamespace( "http://manager.units.standalone.ev.tracking.agp.obteq.com";); before sending the request! --- On Tue, 5/4/10, Ahmed Al-Obaidy wrote: > From: Ahmed Al-Obaidy > Subject: namespace mismatch problem > To: java-user@axis.a

namespace mismatch problem

I have Axis2 1.5.1 to expose and consume Web Service. I've got the following error in the server org.apache.axis2.AxisFault: namespace mismatch require http://manager.units.standalone.ev.tracking.agp.obteq.com found none at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUti

Re: A Fault-Handler to retransmit message still return the 1st in-msg

Please, any help on re-transmitting a soap-message?? On Mon, May 3, 2010 at 7:44 PM, Kostis Anagnostopoulos wrote: > Hi, > > I have modified the behavior of axis2-clients. > In particular, when invoking some WS i setup a pair of handlers that, > in case of some Fault, they will re-submit the orig