There are no standard tests for a product, only for the WSDLs and SOAP messages generated by the product. Axis2 frequently generates non-compliant WSDLs -- e.g., a service with multiple operations with non-unique signatures, where the signature is defined as the qname of the child element of the SOAP Body. If we properly supported wrapped document/literal, then it's very likely that would resolve the WS-I non-compliance issues.
It would be useful to have a switch that requests WS-I compliance, which would then automatically generate wrapped style. Anne On Dec 24, 2007 1:21 AM, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > > > > On Dec 22, 2007 7:49 PM, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > I'd like to see a WS-I BP 1.1 compliance option added. > > Axis2 do have most of the Basic profile features. Do we have to run any > standard test suite to claim the > compliance? I mean for JAXWS we have to pass the SUNs' TCK. > > Amila. > > > > > > > > Anne > > > > > > > > > > On Dec 19, 2007 12:02 AM, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > > > Hi Devs and Users, > > > > > > I saw a number of users asking about the next release of Axis2 , so I > > > think its good time to think about that. We did our last release on > > > August , looking at the mailing list and JIRA I can assume that the > > > release is very stable release. However in the meantime we have few > > > items that we need to implement that we discussed over the mailing list > > > for the next release. And there are a few bug fixes and new features > > > that users have ask about , so taking all those into account how about > > > doing a release on end of February ? > > > > > > So in the release I would like to see following list of items > > > - Support for RPC-Encoded > > > - Full support for JAX-WS > > > - Enhance NIO transport support > > > - Discuss and implement dynamic phase rule support > > > - Fix the issues we found at MS PlugFest > > > - Anything else ..... ?? > > > > > > In addition to that we need to identify the issues that we are going to > > > fix in next release , for that I would like ask Axis2 users to go and > > > create a JIRA or change the priority of JIRA if they want some issues or > > > features (s)he like to see in next release. In the meantime if someone > > > think to fix some particular issue for next release then please go and > > > mark the issue as blocker. But please do not just mark issue as blocker > > > provide some useful information specifying what do you think its is > > > important. > > > > > > So let's target Axis2 1.4 on end of February , and here is my +1 for the > > > release. > > > > > > -Deepal > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > > > -- > Amila Suriarachchi, > WSO2 Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
