Axis2 1.4.1 service sends same name space for all elements even though
different elements belong to different name space. The type attribute for
each element has Java package which is correct , but the name space is
incorrect and most of the clients other than axis ( like .Net or NetBeans)
not abl
Can you please check with Axis2 1.6.0?
thanks,
Amila.
On Sat, Sep 17, 2011 at 4:35 AM, ramkig wrote:
>
> Axis2 1.4.1 service sends same name space for all elements even though
> different elements belong to different name space. The type attribute for
> each element has Java package which is co
The way axis2 handles soapsession is specific to the Axis2. so it won't work
with any other client.
thanks,
Amila.
On Fri, Sep 16, 2011 at 8:27 PM, Barry Hathaway wrote:
> I just finished developing a POJO-based web service that operates with
> scope=soapsession.
> It works just fine when access
I tried with axis2 1.6.0. Getting same response with invalid name space. Only
difference is type attribute is not coming which does not matter. Please
advise.
Amila Suriarachchi wrote:
>
> Can you please check with Axis2 1.6.0?
>
> thanks,
> Amila.
>
> On Sat, Sep 17, 2011 at 4:35 AM, ramkig
I use spring+axis2 to publish my webservice.The client use cxf to call my
service,Then, I ran into the Exception:
Caused by: org.xml.sax.SAXParseException: undefined simple or complex
type 'xs:RuntimeException'
at
com.sun.xml.xsom.impl.parser.ParserContext$1.reportError(ParserContext.java:17
Hi All,
I have been using axis 1.5.4 and recently changed to axis 1.6.0 and when I try
to run some of my existing code I get the following error. could this be due to
some version issue?
ERROR:
org.apache.axis2.AxisFault: Unable to engage module : addressing
at org.apache.axis2.client.Servic
