RE: [AXIS2] RESTful using Sun JAX-RS and AXIS2 SOAP
https://issues.apache.org/jira/browse/AXIS2-3619 Created JIRA for this. Thank You. -Venky From: Brian De Pradine [mailto:[EMAIL PROTECTED] Sent: Monday, March 17, 2008 11:34 AM To: axis-user@ws.apache.org Subject: Re: [AXIS2] RESTful using Sun JAX-RS and AXIS2 SOAP Hi Venky, This is definitely not in the next release of axis2 (i.e. version 1.4), but feel free to raise a JIRA so that it may be considered for a future release. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? "Venkatesh Jayaraman (jvenky)" <[EMAIL PROTECTED]> wrote on 17/03/2008 16:25:12: > Added AXIS2 header to get attention. > > Are we planning to support WADL ?? > > Thanks > > -Venky > > -Original Message- > From: Venkatesh Jayaraman (jvenky) > Sent: Sunday, March 16, 2008 12:32 PM > To: axis-user@ws.apache.org > Subject: RESTful using Sun JAX-RS and AXIS2 SOAP > > I see sun is publishing following link for RESTful interface /JAX-RS > > http://blogs.sun.com/sandoz/resource/TS-6411.pdf > > Are we planning to use JAX-RS binding in AXIS2?? > > Thanks for your response in advance. > > -Venky > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
[AXIS2] RESTful using Sun JAX-RS and AXIS2 SOAP
Added AXIS2 header to get attention. Are we planning to support WADL ?? Thanks -Venky -Original Message- From: Venkatesh Jayaraman (jvenky) Sent: Sunday, March 16, 2008 12:32 PM To: axis-user@ws.apache.org Subject: RESTful using Sun JAX-RS and AXIS2 SOAP I see sun is publishing following link for RESTful interface /JAX-RS http://blogs.sun.com/sandoz/resource/TS-6411.pdf Are we planning to use JAX-RS binding in AXIS2?? Thanks for your response in advance. -Venky - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RESTful using Sun JAX-RS and AXIS2 SOAP
oOne more: Are we planning to support WADL in AXIS2? https://wadl.dev.java.net/ -Venky -Original Message- From: Venkatesh Jayaraman (jvenky) Sent: Sunday, March 16, 2008 12:32 PM To: 'axis-user@ws.apache.org' Subject: RESTful using Sun JAX-RS and AXIS2 SOAP I see sun is publishing following link for RESTful interface /JAX-RS http://blogs.sun.com/sandoz/resource/TS-6411.pdf Are we planning to use JAX-RS binding in AXIS2?? Thanks for your response in advance. -Venky
RESTful using Sun JAX-RS and AXIS2 SOAP
I see sun is publishing following link for RESTful interface /JAX-RS http://blogs.sun.com/sandoz/resource/TS-6411.pdf Are we planning to use JAX-RS binding in AXIS2?? Thanks for your response in advance. -Venky - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Environment variable in tag of server-config.wsdd file [AXIS 1.4]
I looked at the AXIS 1.4 source and I did not see any indication that wsdlFile tag handles the environment variables. So I am planning to go with generation of two server-cong.wsdd. one for windows and the other for linux. Thanks for your help any way ...;D Happy New Year 2008 -Venky From: Venkatesh Jayaraman (jvenky) Sent: Wednesday, January 02, 2008 11:01 AM To: axis-user@ws.apache.org Subject: Environment variable in tage of service-config.wsdd file Helo I am using WSDL file path with in wsdd file like as follows Server-config.wsdd file: /usr/local/tomcat/webapps/myservice/myservice.wsdl ... NOW I need to support this wsdd for both windows and linux. Can we use environment varible with in wsdlFile tag of service definition?? Thanks for the help in advance.. -Venky
Environment variable in tage of service-config.wsdd file
Helo I am using WSDL file path with in wsdd file like as follows Service-config.wsdd file: /usr/local/tomcat/webapps/myservice/myservice.wsdl ... NOW I need to support this wsdd for both windows and linux. Can we use environment varible with in wsdlFile tag of service definition?? Thanks for the help in advance.. -Venky
RE: Do we have XML Injection thread on AXIS 1.X Soap Servers?
I could find the answers in FAQ. Special XML attacks XML messages have a few intrinsic weakness, that Web Service creators should know about. None of these problems are unique to SOAP; anyone processing incoming XML needs to know and resist these. Large XML Documents Have a client post an XML doc of extreme length/depth ... This does bad things to DOM parsers and memory consumption on the server: a DoS attack. The issue here is that the costs of handling a large XML document are much greater than the cost of generating one. Entity Expansion Attacks. If an XML doc header declares some recursive entity declarations, and the file refers to them, then bad things happen. Axis became immune to this between versions 1.0 and 1.1. Entities referring to the filesystem. Here you declare an entity referring to a local file, then expand it. Result: you may be able to probe for files, perhaps even get a copy of it in the error response. As Axis does not support entities any more, it resists this. If your code has any way of resolving URLs from incoming messages, you may recreate this problem. The other thing to know about XML is that string matching is not enough to be sure that the content is safe, because of the many ways to reformat the same XML. Thanks -Venky From: Venkatesh Jayaraman (jvenky) Sent: Thursday, November 09, 2006 9:57 AM To: axis-user@ws.apache.org Subject: RE: Do we have XML Injection thread on AXIS 1.X Soap Servers? Does AXIS take care of this internally? Thanks for the answers in advance. -Venky From: Venkatesh Jayaraman (jvenky) Sent: Thursday, November 09, 2006 9:51 AM To: 'axis-user@ws.apache.org' Subject: Do we have XML Injection thread on AXIS 1.X Soap Servers? Security Issue Posed by Nested Entity Definitions While XML does not allow recursive entity definitions, it does permit nested entity definitions, which produces the potential for Denial of Service attacks on a server which accepts XML data from external sources. For example, a SOAP document like the following that has very deeply nested entity definitions can consume 100% of CPU time and large amounts of memory in entity expansions: ... ]> &x1; A system that doesn't take in external XML data need not be concerned with the issue, but one that does can utilize one of the following safeguards to prevent the problem: New system property to limit entity expansion The entityExpansionLimit system property lets existing applications constrain the total number of entity expansions without recompiling the code. The parser throws a fatal error once it has reached the entity expansion limit. (By default, the limit is set to 64000.) To set the entity expansion limit using the system property, use an option like the following on the java command line: -DentityExpansionLimit=10 New parser property to disallow DTDs The application can also set the http://apache.org/xml/features/disallow-doctype-decl parser property to true. A fatal error is then thrown if the incoming XML document contains a DOCTYPE declaration. (The default value for this property is false.) This property is typically useful for SOAP based applications where a SOAP message must not contain a Document Type Declaration. New feature for Secure Processing JAXP 1.3 includes a new secure processing feature in which an application can configure the SAXParserFactory or DocumentBuilderFactory to get an XML processor that behaves in a secured fashion. Setting this feature to true sets the entity expansion limit to 64000. Note that the default limit can be increased using the entityExpansionLimit system property. http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html Thanks -Venky (Venkatesh Jayaraman)
RE: Do we have XML Injection thread on AXIS 1.X Soap Servers?
Does AXIS take care of this internally? Thanks for the answers in advance. -Venky From: Venkatesh Jayaraman (jvenky) Sent: Thursday, November 09, 2006 9:51 AM To: 'axis-user@ws.apache.org' Subject: Do we have XML Injection thread on AXIS 1.X Soap Servers? Security Issue Posed by Nested Entity Definitions While XML does not allow recursive entity definitions, it does permit nested entity definitions, which produces the potential for Denial of Service attacks on a server which accepts XML data from external sources. For example, a SOAP document like the following that has very deeply nested entity definitions can consume 100% of CPU time and large amounts of memory in entity expansions: ... ]> &x1; A system that doesn't take in external XML data need not be concerned with the issue, but one that does can utilize one of the following safeguards to prevent the problem: New system property to limit entity expansion The entityExpansionLimit system property lets existing applications constrain the total number of entity expansions without recompiling the code. The parser throws a fatal error once it has reached the entity expansion limit. (By default, the limit is set to 64000.) To set the entity expansion limit using the system property, use an option like the following on the java command line: -DentityExpansionLimit=10 New parser property to disallow DTDs The application can also set the http://apache.org/xml/features/disallow-doctype-decl parser property to true. A fatal error is then thrown if the incoming XML document contains a DOCTYPE declaration. (The default value for this property is false.) This property is typically useful for SOAP based applications where a SOAP message must not contain a Document Type Declaration. New feature for Secure Processing JAXP 1.3 includes a new secure processing feature in which an application can configure the SAXParserFactory or DocumentBuilderFactory to get an XML processor that behaves in a secured fashion. Setting this feature to true sets the entity expansion limit to 64000. Note that the default limit can be increased using the entityExpansionLimit system property. http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html Thanks -Venky (Venkatesh Jayaraman)
Do we have XML Injection thread on AXIS 1.X Soap Servers?
Security Issue Posed by Nested Entity Definitions While XML does not allow recursive entity definitions, it does permit nested entity definitions, which produces the potential for Denial of Service attacks on a server which accepts XML data from external sources. For example, a SOAP document like the following that has very deeply nested entity definitions can consume 100% of CPU time and large amounts of memory in entity expansions: ... ]> &x1; A system that doesn't take in external XML data need not be concerned with the issue, but one that does can utilize one of the following safeguards to prevent the problem: New system property to limit entity expansion The entityExpansionLimit system property lets existing applications constrain the total number of entity expansions without recompiling the code. The parser throws a fatal error once it has reached the entity expansion limit. (By default, the limit is set to 64000.) To set the entity expansion limit using the system property, use an option like the following on the java command line: -DentityExpansionLimit=10 New parser property to disallow DTDs The application can also set the http://apache.org/xml/features/disallow-doctype-decl parser property to true. A fatal error is then thrown if the incoming XML document contains a DOCTYPE declaration. (The default value for this property is false.) This property is typically useful for SOAP based applications where a SOAP message must not contain a Document Type Declaration. New feature for Secure Processing JAXP 1.3 includes a new secure processing feature in which an application can configure the SAXParserFactory or DocumentBuilderFactory to get an XML processor that behaves in a secured fashion. Setting this feature to true sets the entity expansion limit to 64000. Note that the default limit can be increased using the entityExpansionLimit system property. http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html Thanks -Venky (Venkatesh Jayaraman)
RE: [Axis2] Does Axis2 Provide Asynchronous Notifications
Yes...I do see it. Looking forward seeing a sample on how to use it http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/savan/ src/org/apache/savan/eventing/ -Venky -Original Message- From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Sent: Saturday, October 28, 2006 11:41 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Does Axis2 Provide Asynchronous Notifications Yes... We have an implementation on board.. Please check the "savan" module in axis2. There is also a sample in the samples module.. We are not releasing it as part of Axis2 1.1... But I'm sure it'll be released soon as a seperate module.. Thanks, Thilina On 10/29/06, Venkatesh Jayaraman (jvenky) <[EMAIL PROTECTED]> wrote: > I am looking for long answer and explicit answer...;D > > http://www.w3.org/Submission/WS-Eventing/ > > Please see above specification. Does AXIS2 support it? > > Thanks > -Venky > > -Original Message- > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > Sent: Friday, October 27, 2006 9:16 AM > To: axis-user@ws.apache.org > Subject: Re: [Axis2] Does Axis2 Provide Asynchronous Notifications > > Short Answer: Yes :) > > -- dims > > On 10/27/06, Venkatesh Jayaraman (jvenky) <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Let us say "soap client's needs asynchronous notification of progress > of the > > soap transaction" > > > > > > > > Can it be achieved through AXIS2 toolkit? > > > > > > > > Thanks > > > > > > > > -Venky (Venkatesh Jayaraman) > > > > > > > > > > > -- > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service > Developers) > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Does Axis2 Provide Asynchronous Notifications
I am looking for long answer and explicit answer...;D http://www.w3.org/Submission/WS-Eventing/ Please see above specification. Does AXIS2 support it? Thanks -Venky -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, October 27, 2006 9:16 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Does Axis2 Provide Asynchronous Notifications Short Answer: Yes :) -- dims On 10/27/06, Venkatesh Jayaraman (jvenky) <[EMAIL PROTECTED]> wrote: > > > > > Let us say "soap client's needs asynchronous notification of progress of the > soap transaction" > > > > Can it be achieved through AXIS2 toolkit? > > > > Thanks > > > > -Venky (Venkatesh Jayaraman) > > > > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Does Axis2 Provide Asynchronous Notifications
Let us say “soap client’s needs asynchronous notification of progress of the soap transaction” Can it be achieved through AXIS2 toolkit? Thanks -Venky (Venkatesh Jayaraman)
RE: Array is different moving from Axis 1.2 to Axis 1.4
Looking at the email thread "Denis Schlesinger" is suggestiong the fix. BUT no
one has commited the fix yet..
Any final decision on this BUG?
-Venky
>>>>>>
Comment by Denis Schlesinger [13/Oct/05 10:03 AM]
An object of the class "EntityListResultBean" is being returned by the
web service. The entries of the list generated from the member array
"value" of type "EntityBean" have the same name as the list itself - "value".
Itshould be "item" for each list entry. The same problem occures for
all other arrays of custom types.
[ Permlink ] Comment by Denis Schlesinger [18/Oct/05 06:24 PM]
I solved it to my own needs by adding an "else" branch at
org.apache.axis.encoding.ser.ArraySerializer, line 404:
[...] else
elementName = new QName(elementName.getNamespaceURI(), "item");
[...]
Making the whole if-block:
if (!maxOccursUsage) {
serializeAttr = null; // since we are putting them here
context.startElement(name, attributes);
if (itemQName != null)
elementName = itemQName;
else if(componentQName != null)
elementName = componentQName;
else
elementName = new QName(elementName.getNamespaceURI(), "item");
}
Anyway, this needs to be checked by some other people as well...
[ Permlink ] Comment by Chad Wilson [20/Jan/06 05:02 AM]
I believe this is a dupe of AXIS-2095, as it was resolved by Anil's fix
mentioned there, at least in theDocument/Wrapped encoding.
[ Permlink ] Comment by René Zanner [31/May/06 05:47 PM]
It seems this bug exists also in version 1.3, so please change the
"Affects version" field to "1.3"!
We use Axis 1.3 with a hand written WSDD as well as a manually modified
WSDL. Our Axis client stubs are generated using this manually modified
WSDL file. The stubs expect an "item" element inside the Array wrapper element
but deserialize the wrong response without an error. How does that
work???
So the Axis client stubs (using the ArrayDeserializer) ignore the wrong
response from the server and simply deserialize despite the wrong xml
structure.
Maybe that's the reason why nobody stumbled over it any more? Since we
have a .NET client at the other side, we found this bug very quickly
and need a fix as soon as possible!
Thanks a lot!
>>>>>
-Original Message-
From: Venkatesh Jayaraman (jvenky)
Sent: Thursday, July 13, 2006 6:21 PM
To: axis-user@ws.apache.org
Cc: [EMAIL PROTECTED]
Subject: RE: Array is different moving from Axis 1.2 to Axis 1.4
http://issues.apache.org/jira/browse/AXIS-2250
I am seeing similar bug opened. But not resolved...
Any Idea ...
Thanks
-Venky
-Original Message-
From: Venkatesh Jayaraman (jvenky)
Sent: Thursday, July 13, 2006 10:29 AM
To: axis-user@ws.apache.org
Cc: [EMAIL PROTECTED]
Subject: RE: Array is different moving from Axis 1.2 to Axis 1.4
I have the code that was generated using 1.2 Axis.
I do not want to change the code.
Is there any option in .wsdd file to specify the to get item element in
Array?
Thanks
-Venky
-Original Message-
From: Jarmo Doc [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 12, 2006 6:18 PM
To: axis-user@ws.apache.org
Subject: RE: Array is different moving from Axis 1.2 to Axis 1.4
See if this article helps:
http://www.nabble.com/Re%3A-%3Citem%3E-in-Arrays-tf1254632.html#a334
1799
>From: "Venkatesh Jayaraman (jvenky)" <[EMAIL PROTECTED]>
>Reply-To: axis-user@ws.apache.org
>To:
>Subject: Array is different moving from Axis 1.2 to Axis 1.4 Date:
>Wed, 12 Jul 2006 16:03:19 -0700
>
>In Axis 1.2
>
>xsi:type="soapenc:Array"
>xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>
><http://schemas.xmlsoap.org/soap/encoding/";>>
>xsi:type="ns1:CounterNameType"> MyCounterName xsi:type="xsd:long">1xsi:type="xsd:unsignedInt">0
>
>
>
>In Axis 1.4
>xsi:type="soapenc:Array"
>xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>
><http://schemas.xmlsoap.org/soap/encoding/";>>
>xsi:type="ns1:CounterNameType">MyCounterNamexsi:type="xsd:long">1xsi:type="xsd:unsignedInt">0
>
>
>
>
>Basically "item" element in Array is replaced with array element name
>itself.
>
>Can you please explain why this change was done?
>
>Thanks
>
>-Venky
>
>
_
On the
RE: Array is different moving from Axis 1.2 to Axis 1.4
http://issues.apache.org/jira/browse/AXIS-2250 I am seeing similar bug opened. But not resolved... Any Idea ... Thanks -Venky -Original Message- From: Venkatesh Jayaraman (jvenky) Sent: Thursday, July 13, 2006 10:29 AM To: axis-user@ws.apache.org Cc: [EMAIL PROTECTED] Subject: RE: Array is different moving from Axis 1.2 to Axis 1.4 I have the code that was generated using 1.2 Axis. I do not want to change the code. Is there any option in .wsdd file to specify the to get item element in Array? Thanks -Venky -Original Message- From: Jarmo Doc [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 12, 2006 6:18 PM To: axis-user@ws.apache.org Subject: RE: Array is different moving from Axis 1.2 to Axis 1.4 See if this article helps: http://www.nabble.com/Re%3A-%3Citem%3E-in-Arrays-tf1254632.html#a334 1799 >From: "Venkatesh Jayaraman (jvenky)" <[EMAIL PROTECTED]> >Reply-To: axis-user@ws.apache.org >To: >Subject: Array is different moving from Axis 1.2 to Axis 1.4 Date: >Wed, 12 Jul 2006 16:03:19 -0700 > >In Axis 1.2 > >xsi:type="soapenc:Array" >xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";> ><http://schemas.xmlsoap.org/soap/encoding/";>> >xsi:type="ns1:CounterNameType"> MyCounterName xsi:type="xsd:long">1xsi:type="xsd:unsignedInt">0 > > > >In Axis 1.4 >xsi:type="soapenc:Array" >xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";> ><http://schemas.xmlsoap.org/soap/encoding/";>> >xsi:type="ns1:CounterNameType">MyCounterNamexsi:type="xsd:long">1xsi:type="xsd:unsignedInt">0 > > > > >Basically "item" element in Array is replaced with array element name >itself. > >Can you please explain why this change was done? > >Thanks > >-Venky > > _ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Array is different moving from Axis 1.2 to Axis 1.4
I have the code that was generated using 1.2 Axis. I do not want to change the code. Is there any option in .wsdd file to specify the to get item element in Array? Thanks -Venky -Original Message- From: Jarmo Doc [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 12, 2006 6:18 PM To: axis-user@ws.apache.org Subject: RE: Array is different moving from Axis 1.2 to Axis 1.4 See if this article helps: http://www.nabble.com/Re%3A-%3Citem%3E-in-Arrays-tf1254632.html#a334 1799 >From: "Venkatesh Jayaraman (jvenky)" <[EMAIL PROTECTED]> >Reply-To: axis-user@ws.apache.org >To: >Subject: Array is different moving from Axis 1.2 to Axis 1.4 Date: >Wed, 12 Jul 2006 16:03:19 -0700 > >In Axis 1.2 > >xsi:type="soapenc:Array" >xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";> ><http://schemas.xmlsoap.org/soap/encoding/";>> >xsi:type="ns1:CounterNameType"> MyCounterName xsi:type="xsd:long">1xsi:type="xsd:unsignedInt">0 > > > >In Axis 1.4 >xsi:type="soapenc:Array" >xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";> ><http://schemas.xmlsoap.org/soap/encoding/";>> >xsi:type="ns1:CounterNameType">MyCounterNamexsi:type="xsd:long">1xsi:type="xsd:unsignedInt">0 > > > > >Basically "item" element in Array is replaced with array element name >itself. > >Can you please explain why this change was done? > >Thanks > >-Venky > > _ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Array is different moving from Axis 1.2 to Axis 1.4
In Axis 1.2- MyCounterName 10> > In Axis 1.4
xsi:type="ns1:CounterInfoType">MyCounterName10 ArrayOfCounterInfo> Basically "item" element in Array is replaced with array element name itself. Can you please explain why this change was done? Thanks -Venky
