Code changes for Axis 14 support for optional sequence and choice

[vernekap]

Recently for one of my projects, I needed Axis 14 to support 
- optional sequences 
--verify that mandatory elements below optional sequence are either all
present or none
- mandatory choice
   -- verify only one of choice element is present
- optional choice 
   -- verify 0/1 of choice element is present

I made some changes to WSDL2Java. I do not think that I can add that
standard way of handling serialization and do not think that it can be added
to axis repository.

If someone is looking for this code, I can share it.

with regards
Pralhad

-- 
View this message in context: 
http://www.nabble.com/Code-changes-for-Axis-14-support-for-optional-sequence-and-choice-tp21326196p21326196.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: ADB maxlength

[Amila Suriarachchi]

On Thu, May 22, 2008 at 1:22 AM, sultanat  wrote:

>
> For the following schema, the axis2 1.4 ADB doesnt check for max length, it
> is only checking for the regular expression. Can anyone please help me with
> this.
> 
>  
>
>  
>  
>
>  
> 
>

This is an issue with ADB. please log a jira.

thanks,
Amila.

>
> --
> View this message in context:
> http://www.nabble.com/ADB-maxlength-tp17369134p17369134.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: axis-user-unsubscr...@ws.apache.org
> For additional commands, e-mail: axis-user-h...@ws.apache.org
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: ADB maxlength

[asheikh]

Hi

I have similar problem, can anyone, please,  put some light why axis2
1.3/1.4 doesn't check  xsd:maxLength,

In my case, the client application can set the field value either in Arabic
or English which has different character length.

Thanks in advance

On Wed, May 21, 2008 at 10:52 PM, sultanat  wrote:

>
> For the following schema, the axis2 1.4 ADB doesnt check for max length, it
> is only checking for the regular expression. Can anyone please help me with
> this.
> 
>  
>
>  
>  
>
>  
> 
>
> --
> View this message in context:
> http://www.nabble.com/ADB-maxlength-tp17369134p17369134.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: axis-user-unsubscr...@ws.apache.org
> For additional commands, e-mail: axis-user-h...@ws.apache.org
>
>

Two XBeans-packaged.jar having same class name

[Aseem Sharma]

Hello, 

I have created client stubs for two different web services using axis2(ver
1.4, xmlbeans binding, asynchronous). Two -test-client.jar files are
created. I have put both the jars in lib directory of axis2 as I have to
call both the webservices from the same project. 

I am able to call both the web services with these client jars. But I am
unable to process response of the web services as response of both the web
services is having same format. I am getting class cast exception as I am
having two XBeans-packaged.jar in my class path containing same name of the
class in both jars (i.e Response Document object from both the
webservices)(although directory structure of both the Response Document is
different). 

Please help me to resolve this problem. 

Thanks & Regards, 
Aseem Sharma
-- 
View this message in context: 
http://www.nabble.com/Two-XBeans-packaged.jar-having-same-class-name-tp21325385p21325385.html
Sent from the Axis - User mailing list archive at Nabble.com.

Two XBeans-packaged.jar having same class name

[Aseem Sharma]

Hello,

I have created client stubs for two different web services using axis2(ver
1.4, xmlbeans binding, asynchronous, different directory structure). Two
-test-client.jar files are created. I have put both the jars in lib
directory of axis2 as I have to call both the webservices from the same
project.

I am able to call both the web services with these client jars. But I am
unable to process response of the web services as response of both the web
services is having same format. I am getting class cast exception as I am
having two XBeans-packaged.jar in my class path containing same name of the
class in both jars (i.e Response Document object from both the webservices).

Please help me to resolve this problem.

Thanks & Regards,
Aseem Sharma 

-- 
View this message in context: 
http://www.nabble.com/Two-XBeans-packaged.jar-having-same-class-name-tp21325323p21325323.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: XMLStreamException: end reached! - More details provided

[Deenadayalan J]

Hi All,

I got some more inputs and need your help in this regard. I am getting this
error consistently now for one sample data. I will provide details of what I
have found till now.

Below is the request XML generated at my client end.
I am working on a Web application and the app is a client to a webservice.
I am using Axis2-v1.3 with XML Beans for the client. Web sevice is host by
3rd party.
I have deployed my web application in Weblogic81 SP4

[Jan 06 16:58:16] - http://x.xx..xxx";>
  
3

  bb

mth08
  
  http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ns="http://x.xx..xxx";>
test

W

2
hugh
jackman



true


  12234
  36355
  @#@
  2009-01-07


  


1. When I call stub.update(), the exception is thrown. The exception is
thrown at client side itself before reaching the service.

2. Exception always occurs for the above sample data.

3. The web service call occurs successfully, if I do one of the changes
given below
 a. If I increase the number of characters to node aaa from *test *to *
testabcd*, the service call happens successfully.
 b. keeping the sample as such, If I change the fff & ggg nodes to some
other name it works. But not always, it does fail for some names.
 c. Keeping the sample as such, If I add value to one of the blank fields,
it works.

4. Exception never occurs when I deploy the web-app in my local computer.
Exception always occurs for the above sample data, when I deploy the web app
in a remote server. I have tried re-deplyment or re-start of server thinking
it might be due to some objects not getting garbage collected. But the
exception still occurs when i deploy in a remote server
*
*Have been struggling with this problem for quite a while. I would really
appreciate any help in this regard.
*

*Thanks
Deena


On Mon, Nov 24, 2008 at 12:44 PM, Deenadayalan J  wrote:

> Hi,
>
> I getting this error frequently for the same request. But not always. When
> does this happen?
>
>
> Message:javax.xml.stream.XMLStreamException: end reached!:
>
> StAXOMBuilder.javaorg.apache.axiom.om.impl.builder.StAXOMBuildernext
> OMStAXWrapper.javaorg.apache.axiom.om.impl.llom.OMStAXWrapperupdateNextNode
> OMStAXWrapper.javaorg.apache.axiom.om.impl.llom.OMStAXWrapper
>
> OMElementImpl.javaorg.apache.axiom.om.impl.llom.OMElementImplgetXMLStreamReader
>
> OMElementImpl.javaorg.apache.axiom.om.impl.llom.OMElementImplgetXMLStreamReaderWithoutCaching
>
> OMSerializerUtil.javaorg.apache.axiom.om.impl.util.OMSerializerUtilserializeByPullStream
>
> OMElementImpl.javaorg.apache.axiom.om.impl.llom.OMElementImplinternalSerialize
>
> OMElementImpl.javaorg.apache.axiom.om.impl.llom.OMElementImplinternalSerializeAndConsume
>
> SOAPEnvelopeImpl.javaorg.apache.axiom.soap.impl.llom.SOAPEnvelopeImplserializeInternally
>
> SOAPEnvelopeImpl.javaorg.apache.axiom.soap.impl.llom.SOAPEnvelopeImplinternalSerialize
>
> OMElementImpl.javaorg.apache.axiom.om.impl.llom.OMElementImplinternalSerializeAndConsume
> OMNodeImpl.javaorg.apache.axiom.om.impl.llom.OMNodeImplserializeAndConsume
>
> SOAPMessageFormatter.javaorg.apache.axis2.transport.http.SOAPMessageFormatterwriteTo
>
> AxisRequestEntity.javaorg.apache.axis2.transport.http.AxisRequestEntitywriteRequest
>
> EntityEnclosingMethod.javaorg.apache.commons.httpclient.methods.EntityEnclosingMethodwriteRequestBody
> HttpMethodBase.javaorg.apache.commons.httpclient.HttpMethodBasewriteRequest
> HttpMethodBase.javaorg.apache.commons.httpclient.HttpMethodBaseexecute
>
> HttpMethodDirector.javaorg.apache.commons.httpclient.HttpMethodDirectorexecuteWithRetry
>
> HttpMethodDirector.javaorg.apache.commons.httpclient.HttpMethodDirectorexecuteMethod
> HttpClient.javaorg.apache.commons.httpclient.HttpClientexecuteMethod
> HttpClient.javaorg.apache.commons.httpclient.HttpClientexecuteMethod
>
> AbstractHTTPSender.javaorg.apache.axis2.transport.http.AbstractHTTPSenderexecuteMethod
> HTTPSender.javaorg.apache.axis2.transport.http.HTTPSendersendViaPost
> HTTPSender.javaorg.apache.axis2.transport.http.HTTPSendersend
>
> CommonsHTTPTransportSender.javaorg.apache.axis2.transport.http.CommonsHTTPTransportSenderwriteMessageWithCommons
>
> CommonsHTTPTransportSender.javaorg.apache.axis2.transport.http.CommonsHTTPTransportSenderinvoke
> AxisEngine.javaorg.apache.axis2.engine.AxisEnginesend
>
> OutInAxisOperation.javaorg.apache.axis2.description.OutInAxisOperationClientsend
>
> OutInAxisOperation.javaorg.apache.axis2.description.OutInAxisOperationClientexecuteImpl
> OperationClient.javaorg.apache.axis2.client.OperationClientexecute
>
> CSMVOUIServicesStub.javaau.com.qantas.csmvo.pmaui.services.CSMVOUIServicesStubupdateCustomerContact
>
> SectorFunctionServiceClient.javaau.com.qantas.csmvo.pmaui.serviceclients.SectorFunctionServiceClientupdateCustomerContact
>
> CustomerContactUpdateAction.javaau.co

Re: WSDL Generation has incorrect port

[Nandana Mihindukulasooriya]

Hi Kevin,
   Did you try this with the trunk ? There were few changes with respect
to this in the trunk.

thanks,
nandana

On Wed, Jan 7, 2009 at 3:45 AM, Kevin Witten wrote:

>  Hello,
>
>
>
> I am using Axis2 1.4.1 with Tomcat 6.0 and Apache2.2 httpd.
>
>
>
> I setup Apache httpd to only support SSL and to connect to Tomcat via a
> proxy (AJP), via port 8009.
>
>
>
> Apache httpd.conf has
>
>
>
> SSLProxyEngine On
>
> ProxyRequests Off
>
> ProxyPass /  ajp://localhost:8009/
>
> ProxyPassReverse  /  ajp://localhost:8009/
>
> ProxyPreserveHost On
>
>
>
> Tomcat server.xml has the following connector
>
>
>
> 
>
>
>
>
>
> Now I deploy an Axis2 service (ACSService.aar) in the
> webapps\axis2\WEB-INF\services directory.
>
> Restart Tomcat and Apache.
>
>
>
> This service includes a WSDL file with the following port:
>
>
>
> 
>
> 
>
> 
>name="ACSServiceSOAP">
>
> 
> location="https://localhost/axis2/services/ACSService
> "/>
>
> 
>
> 
>
>
>
> I have changed the services.xml file to include
>
> true
>
>
>
> Now when I run get the WSDL from the service (i.e.
> https://67.130.148.13/axis2/services/ACSService?wsdl) The URL in the port
> is not correct.
>
> Notice the port 80. This is not correct as the only way to access this
> service is through SSL (port 443) as Apache is configured.
>
>
>
> 
>
> 
>
> https://67.130.148.13:80/axis2/services/ACSService/"/>
>
> 
>
> 
>
>
>
> Next I tried adding the following to services.xml
>
> false
>
>
>
> But this did not do what I expected. I would have expected the hostname up
> get updated to 67.130.148.13. Instead the URL was not changed at all.
>
> So the output was as follows, which is the unmodified URL form the original
> WSDL.
>
>
>
> 
>
> 
>
> https://localhost/axis2/services/ACSService/"/>
>
> 
>
> 
>
>
>
> This seems like a bug, as the modifyUserWSDLPortAddress controls updating
> of the hostname and port.
>
>
>
> How do I get the WSDL to update to the hostname with no port, or as a
> second choice port 443?
>
>
>
> 
>
> 
>
> https://67.130.148.13/axis2/services/ACSService/
> "/>
>
> 
>
> 
>
>
>
>
>
> Thanks in advanced for the help.
>
>
>
> *Kevin Witten*
> Software Engineer
> Nomadix, Inc.  *  1100 Business Center Circle, Suite 100, Newbury Park, CA
> 91320  *  USA
> direct +1 (818) 575-2421  *  main +1-818-597-1500  *  fax
>
> *interTouch Group of Companies  *  a NTT DoCoMo Group company
> *Enhancing Guest Experience
>
> www.inter-touch.com *  www.maginet.net *  www.percipia.com *  www.nomadix.com
>  *  www.azure.com.au
>
> --
> Notice● The information and attachment(s) contained in this communication
> are intended for the addressee only, and may be confidential and/or legally
> privileged. If you have received this communication in error, please contact
> the sender immediately, and delete this communication from any computer or
> network system. Any interception, review, printing, copying,
> re-transmission, dissemination, or other use of, or taking of any action
> upon this information by persons or entities other than the intended
> recipient is strictly prohibited by law and may subject them to criminal or
> civil liability. None of the interTouch Group of Companies shall be liable
> for the improper and/or incomplete transmission of the information contained
> in this communication or for any delay in its receipt.
>

Re: Returning from a different package

[Deepal Jayasinghe]

Hi,

It is not the QName different in those two cases, it is just the prefix.
It does not matter what the prefix is. What you need to do is too
compare the response with the WSDL. Since you are new the Web service,
one thing you can do is send us the WSDL, then we can tell what the
problem is.

Deepal

Jason Wells wrote:
> Hi, I'm new to the Axis2/SOAP world and I'm using Tomcat 6/Axis2
> 1.4.1. I'm running into a problem. I've written a simple Java POJO
> service and generated ADB client code from its generated WSDL. One of
> its operations returns another simple POJO, in this case having two
> String members. When I call it from a SOAP tool I'm using, I get this
> response back:
>
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> 
> http://service.enterprise.semantica
> ">
> 
> Blah<./ax21:name>
> Blah2.
> 
> 
> 
> 
>
> And when I call that operation from my ADB client, I get the following
> exception:
>
> "org.apache.axis2.AxisFault:
> org.apache.axis2.databinding.ADBException: Unexpected subelement guid"
>
> But I have another operation that is essentially identical, in that it
> has the same signature and returns a different POJO having two
> Strings, just like the first one. I get this back:
>
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> 
> http://service.enterprise.semantica
> ">
> 
> One.
> The Other.
> 
> 
> 
> 
>
> This one works in the ADB client. The only significant difference I
> see is that the QNames for the return classes is different (ax21 vs.
> ax23). The two classes are basically identical, except that the broken
> code uses a class from a different package than the service class, and
> the working class is in the same package. But why would this be a problem?
>
> Thanks,
> Jason

-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

Returning from a different package

[Jason Wells]

Hi, I'm new to the Axis2/SOAP world and I'm using Tomcat 6/Axis2  
1.4.1. I'm running into a problem. I've written a simple Java POJO  
service and generated ADB client code from its generated WSDL. One of  
its operations returns another simple POJO, in this case having two  
String members. When I call it from a SOAP tool I'm using, I get this  
response back:


http://schemas.xmlsoap.org/soap/envelope/ 
"


http://service.enterprise.semantica";>

Blah<./ax21:name>
Blah2.





And when I call that operation from my ADB client, I get the following  
exception:


"org.apache.axis2.AxisFault:  
org.apache.axis2.databinding.ADBException: Unexpected subelement guid"


But I have another operation that is essentially identical, in that it  
has the same signature and returns a different POJO having two  
Strings, just like the first one. I get this back:


http://schemas.xmlsoap.org/soap/envelope/ 
">


http://service.enterprise.semantica";>

One.
The Other.





This one works in the ADB client. The only significant difference I  
see is that the QNames for the return classes is different (ax21 vs.  
ax23). The two classes are basically identical, except that the broken  
code uses a class from a different package than the service class, and  
the working class is in the same package. But why would this be a  
problem?


Thanks,
Jason

Bug with POJOs w/ HashSet bug (aka AXIS2-4121)

[Comerford, Sean]

I¹m trying to use the Pojo functionality of Axis2 using the latest release
build (1.4.1).

Simple examples work great but my ³real² POJO has fields like this:

Set teams = new HashSet();

Those seem to be causing problems. I can successfully invoke the service but
when it tries to marshall the object it throws:

Exception in thread "main" java.lang.IllegalArgumentException: argument type
mismatchat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)at java.lang.reflect.Method.invoke(Method.java:597)at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:457)
at 
org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:722)
at 
org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:670
)at 
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:602)
at 
org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceClient
.java:104)


Issue AXIS2-4121 seems to be the culprit but I¹m not sure how to get the
fix... I downloaded the nightly snapshot of axis2-adb (where the 2 classes
referenced in the bug live) but I¹m still seeing the same issue.

Any ideas how to get this fix or otherwise resolve this?

---
Sean Comerford, Software Engineer
ESPN.com Site Architecture Group
Office: 860.766.6454Cell: 860.951.6973

WSDL Generation has incorrect port

[Kevin Witten]

Hello,

I am using Axis2 1.4.1 with Tomcat 6.0 and Apache2.2 httpd.

I setup Apache httpd to only support SSL and to connect to Tomcat via a proxy 
(AJP), via port 8009.

Apache httpd.conf has

SSLProxyEngine On
ProxyRequests Off
ProxyPass /  ajp://localhost:8009/
ProxyPassReverse  /  ajp://localhost:8009/
ProxyPreserveHost On

Tomcat server.xml has the following connector




Now I deploy an Axis2 service (ACSService.aar) in the 
webapps\axis2\WEB-INF\services directory.
Restart Tomcat and Apache.

This service includes a WSDL file with the following port:




https://localhost/axis2/services/ACSService"/>



I have changed the services.xml file to include
true

Now when I run get the WSDL from the service (i.e. 
https://67.130.148.13/axis2/services/ACSService?wsdl) The URL in the port is 
not correct.
Notice the port 80. This is not correct as the only way to access this service 
is through SSL (port 443) as Apache is configured.



https://67.130.148.13:80/axis2/services/ACSService/"/>



Next I tried adding the following to services.xml
false

But this did not do what I expected. I would have expected the hostname up get 
updated to 67.130.148.13. Instead the URL was not changed at all.
So the output was as follows, which is the unmodified URL form the original 
WSDL.



https://localhost/axis2/services/ACSService/"/>



This seems like a bug, as the modifyUserWSDLPortAddress controls updating of 
the hostname and port.

How do I get the WSDL to update to the hostname with no port, or as a second 
choice port 443?



https://67.130.148.13/axis2/services/ACSService/"/>




Thanks in advanced for the help.

Kevin Witten
Software Engineer
Nomadix, Inc.  *  1100 Business Center Circle, Suite 100, Newbury Park, CA 
91320  *  USA
direct +1 (818) 575-2421  *  main +1-818-597-1500  *  fax
interTouch Group of Companies  *  a NTT DoCoMo Group company
Enhancing Guest Experience
www.inter-touch.com *  
www.maginet.net *  
www.percipia.com *  www.nomadix.com 
  *  www.azure.com.au


Notice? The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or legally 
privileged. If you have received this communication in error, please contact 
the sender immediately, and delete this communication from any computer or 
network system. Any interception, review, printing, copying, re-transmission, 
dissemination, or other use of, or taking of any action upon this information 
by persons or entities other than the intended recipient is strictly prohibited 
by law and may subject them to criminal or civil liability. None of the 
interTouch Group of Companies shall be liable for the improper and/or 
incomplete transmission of the information contained in this communication or 
for any delay in its receipt.

[Axis2] How to manually configure JAX-WS Services

[Víctor Downs]

Hello everybody.

Its just recently that I found out that Axis2 supports JAX-WS, so I was
eager to try it. I followed a top down approach, using wsimport and an
existing WSDL file (SampleWS.wsdl) to generate java artifacts, then
copied the generated files to an existing project.

Although I'm kind of new to the use of Axis2 (and Web Services for that
matter), i've managed to configure JMS for a "standard" (i.e. ADB,
eclipse-wizard-generated) service by modifying axis2.xml and its
corresponding services.xml.

Maybe I'm a little confused about the way JAX-WS works, but I would
appreciate it if somebody could give me some pointers on a couple of
issues:

  - 1 -
First, I would llike to modify the "name" with which my bean is
deployed. Take the following code for example:

@WebService(endpointInterface = "com.test.SayHiPortType",
targetNamespace= "http://localhost:8080/Test/SayHiWS/";, serviceName
=
"SayHiWS", portName = "SayHi", wsdlLocation =
"WEB-INF/wsdl/SampleWS.wsdl")
public class SayHiWS {
...
}

When I deploy the project, axis2 reports the service deployment like
this:

[INFO] Deploying JAXWS annotated class com.test.SayHiWS as a service
- SayHiWS.SayHi

Then, if i want to test the service, i have to use the following URL on
my web browser...

http://localhost:8080/Test/services/SayHiWS.SayHi?wsdl

...which is quite different from the soap:address specified in the WSDL
file:


http://localhost:8080/Test/SayHiWS/"/>


Is there a way i could configure the Service in order to be invoked with
that address? (SayHiWS)


- 2 -
The second issue is related to the first: how to configure the JMS
transport. By default, Axis2 tries to look for a queue named after the
service (SayHiWS.SayHi in this case), which of course doesn't exist as I
expected the service to be named simply SayHiWS. I tried creating a
custom services.xml file, but this deploys the service twice! on for the
annotated class and another for the services.xml entry

Is there something Im doing wrong?

Thanks in advance!

Re: List of free webservices

[keith chapman]

You can try mooshup.com You can register there for free and create your own
services using JavaScript as well.

Thanks,
Keith.

On Tue, Jan 6, 2009 at 11:04 PM, florin.botis  wrote:

>
> Hello,
>
> I'm a student in computer science and I need some web services for some
> project. I don't know what kind of web services but I will chose one when I
> will have some options. Please tell me where I can find some nice/cool web
> services in the web. If you know some please send me the link of the
> homepage.
>
>
> Best regards,
> Florin Botis
> --
> View this message in context:
> http://www.nabble.com/List-of-free-webservices-tp21315053p21315053.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

List of free webservices

[florin.botis]

Hello,

I'm a student in computer science and I need some web services for some
project. I don't know what kind of web services but I will chose one when I
will have some options. Please tell me where I can find some nice/cool web
services in the web. If you know some please send me the link of the
homepage.


Best regards,
Florin Botis
-- 
View this message in context: 
http://www.nabble.com/List-of-free-webservices-tp21315053p21315053.html
Sent from the Axis - User mailing list archive at Nabble.com.

getting typeTable from wsdl url?

[אלחנן מעיין]

Hi..

 

I have a service in biztalk, is there a way that I can get it's TypeTable class 
from wsdl? I was thinking I could use that type table for BeanUtil.getOMelement 
so it would convert my beans correctly according the schema

Re: Axis2/jax-ws unmarshal response

[Pauli Savolainen]

Hello,

issue solved. I was using the wrong message receiver. Instead of
org.apache.axis2.rpc.receivers.RPCMessageReceiver I am supposed to use the
org.apache.axis2.jaxws.server.JAXWSMessageReceiver. How silly of me.

Pauli
-- 
View this message in context: 
http://www.nabble.com/Axis2-jax-ws-unmarshal-response-tp21294027p21307265.html
Sent from the Axis - User mailing list archive at Nabble.com.