Hi Deepal, Our team would like to see the following issue resolved in the 1.4 release, if possible:
https://issues.apache.org/jira/browse/AXIS2-3400 (AxisService name not unique enough) Thanks, Greg Foundation Portal Services Applications Infrastructure and Middleware Deepal Jayasinghe <[EMAIL PROTECTED]> 19/12/2007 04:02 PM Please respond to axis-user@ws.apache.org To "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, "axis-user@ws.apache.org" <axis-user@ws.apache.org> cc Subject [Axis2] Release plan and road map for Axis2 1.4 release Reference Expires 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] ********************************************************************** IMPORTANT: This e-mail is intended for the use of the addressee and may contain information that is confidential, commercially valuable or subject to legal or parliamentary privilege. If you are not the intended recipient you are notified that any review, re-transmission, disclosure, use or dissemination of this communication is strictly prohibited by several Commonwealth Acts of Parliament. If you have received this communication in error please notify the sender immediately and delete all copies of this transmission together with any attachments. **********************************************************************
