Re: [Axis2] Release plan and road map for Axis2 1.4 release
Alick, Did you file a bug report with woodstox yet? thanks, dims On Jan 23, 2008 11:45 PM, Alick Buckley [EMAIL PROTECTED] wrote: Thanks Dims, It seems that Woodstox 3.9 does not work with JDK 1.4.2, but the release notes mention 1.4 as the baseline JDK. Woodstox - 3.2.4 works with JDK 1.4.2_15 Woodstox - 3.9 does not work with JDK 1.4.2_15 javac error com.ctc.wstx.stax.WstxInputFactory Class has wrong version number 49.0 should be 48.0 http://woodstox.codehaus.org/3.9.0/release-notes/VERSION Clean-up: * Removed compatibility classes from under com.ctc.wstx.compat, since baseline JDK requirement is now 1.4, and workarounds are not needed (for now?) === -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, 24 January 2008 3:13 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Release plan and road map for Axis2 1.4 release -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alick, +1. We usually do update the dependencies once we gather steam :) - -- dims Alick Buckley wrote: | Hi Guys, | | Do you plan to update 3rd party jar files with the latest available ? | | http://woodstox.codehaus.org/Download | | http://java.sun.com/products/javamail/ | | http://logging.apache.org/log4j/1.2/download.html | | Axis2 1.3 is currently using: | | mail-1.4.jar | activation-1.1.jar | wstx-asl-3.2.1.jar | log4j-1.2.14.jar | | Latest releases | | JAF is now 1.1.1 | JavaMail is now 1.4.1 | Woodstox is now 3.9 | Log4j is now 1.2.15 | | Also Apache Xerces and Xalan have changed | | | | | [Axis2] Release plan and road map for Axis2 1.4 release | | Deepal Jayasinghe | Tue, 18 Dec 2007 21:03:19 -0800 | | 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 | | | | | regards | | Alick Buckley | | LANSA Research and Development | LANSA Pty Ltd | | Phone: +61289070243 | | http://www.lansa.com | mailto:[EMAIL PROTECTED] | | | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHmBBFgNg6eWEDv1kRAmtvAJ9FAIrl0LbHfaBGaUAaMJyhhw0TdACgrnL2 I1xWyIUBV0O2fSQDEaRKerE= =jRAz -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Release plan and road map for Axis2 1.4 release
Dims, I have not logged a bug report -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, 25 January 2008 12:46 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Release plan and road map for Axis2 1.4 release Alick, Did you file a bug report with woodstox yet? thanks, dims On Jan 23, 2008 11:45 PM, Alick Buckley [EMAIL PROTECTED] wrote: Thanks Dims, It seems that Woodstox 3.9 does not work with JDK 1.4.2, but the release notes mention 1.4 as the baseline JDK. Woodstox - 3.2.4 works with JDK 1.4.2_15 Woodstox - 3.9 does not work with JDK 1.4.2_15 javac error com.ctc.wstx.stax.WstxInputFactory Class has wrong version number 49.0 should be 48.0 http://woodstox.codehaus.org/3.9.0/release-notes/VERSION Clean-up: * Removed compatibility classes from under com.ctc.wstx.compat, since baseline JDK requirement is now 1.4, and workarounds are not needed (for now?) === -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, 24 January 2008 3:13 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Release plan and road map for Axis2 1.4 release -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alick, +1. We usually do update the dependencies once we gather steam :) - -- dims Alick Buckley wrote: | Hi Guys, | | Do you plan to update 3rd party jar files with the latest available ? | | http://woodstox.codehaus.org/Download | | http://java.sun.com/products/javamail/ | | http://logging.apache.org/log4j/1.2/download.html | | Axis2 1.3 is currently using: | | mail-1.4.jar | activation-1.1.jar | wstx-asl-3.2.1.jar | log4j-1.2.14.jar | | Latest releases | | JAF is now 1.1.1 | JavaMail is now 1.4.1 | Woodstox is now 3.9 | Log4j is now 1.2.15 | | Also Apache Xerces and Xalan have changed | | | | | [Axis2] Release plan and road map for Axis2 1.4 release | | Deepal Jayasinghe | Tue, 18 Dec 2007 21:03:19 -0800 | | 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 | | | | | regards | | Alick Buckley | | LANSA Research and Development | LANSA Pty Ltd | | Phone: +61289070243 | | http://www.lansa.com | mailto:[EMAIL PROTECTED] | | | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHmBBFgNg6eWEDv1kRAmtvAJ9FAIrl0LbHfaBGaUAaMJyhhw0TdACgrnL2 I1xWyIUBV0O2fSQDEaRKerE= =jRAz -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Release plan and road map for Axis2 1.4 release
Hi Guys, Do you plan to update 3rd party jar files with the latest available ? http://woodstox.codehaus.org/Download http://java.sun.com/products/javamail/ http://logging.apache.org/log4j/1.2/download.html Axis2 1.3 is currently using: mail-1.4.jar activation-1.1.jar wstx-asl-3.2.1.jar log4j-1.2.14.jar Latest releases JAF is now 1.1.1 JavaMail is now 1.4.1 Woodstox is now 3.9 Log4j is now 1.2.15 Also Apache Xerces and Xalan have changed [Axis2] Release plan and road map for Axis2 1.4 release Deepal Jayasinghe Tue, 18 Dec 2007 21:03:19 -0800 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 regards Alick Buckley LANSA Research and Development LANSA Pty Ltd Phone: +61289070243 http://www.lansa.com mailto:[EMAIL PROTECTED]
Re: [Axis2] Release plan and road map for Axis2 1.4 release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alick, +1. We usually do update the dependencies once we gather steam :) - -- dims Alick Buckley wrote: | Hi Guys, | | Do you plan to update 3rd party jar files with the latest available ? | | http://woodstox.codehaus.org/Download | | http://java.sun.com/products/javamail/ | | http://logging.apache.org/log4j/1.2/download.html | | Axis2 1.3 is currently using: | | mail-1.4.jar | activation-1.1.jar | wstx-asl-3.2.1.jar | log4j-1.2.14.jar | | Latest releases | | JAF is now 1.1.1 | JavaMail is now 1.4.1 | Woodstox is now 3.9 | Log4j is now 1.2.15 | | Also Apache Xerces and Xalan have changed | | | | | [Axis2] Release plan and road map for Axis2 1.4 release | | Deepal Jayasinghe | Tue, 18 Dec 2007 21:03:19 -0800 | | 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 | | | | | regards | | Alick Buckley | | LANSA Research and Development | LANSA Pty Ltd | | Phone: +61289070243 | | http://www.lansa.com | mailto:[EMAIL PROTECTED] | | | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHmBBFgNg6eWEDv1kRAmtvAJ9FAIrl0LbHfaBGaUAaMJyhhw0TdACgrnL2 I1xWyIUBV0O2fSQDEaRKerE= =jRAz -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Release plan and road map for Axis2 1.4 release
Thanks Dims, It seems that Woodstox 3.9 does not work with JDK 1.4.2, but the release notes mention 1.4 as the baseline JDK. Woodstox - 3.2.4 works with JDK 1.4.2_15 Woodstox - 3.9 does not work with JDK 1.4.2_15 javac error com.ctc.wstx.stax.WstxInputFactory Class has wrong version number 49.0 should be 48.0 http://woodstox.codehaus.org/3.9.0/release-notes/VERSION Clean-up: * Removed compatibility classes from under com.ctc.wstx.compat, since baseline JDK requirement is now 1.4, and workarounds are not needed (for now?) === -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, 24 January 2008 3:13 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Release plan and road map for Axis2 1.4 release -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alick, +1. We usually do update the dependencies once we gather steam :) - -- dims Alick Buckley wrote: | Hi Guys, | | Do you plan to update 3rd party jar files with the latest available ? | | http://woodstox.codehaus.org/Download | | http://java.sun.com/products/javamail/ | | http://logging.apache.org/log4j/1.2/download.html | | Axis2 1.3 is currently using: | | mail-1.4.jar | activation-1.1.jar | wstx-asl-3.2.1.jar | log4j-1.2.14.jar | | Latest releases | | JAF is now 1.1.1 | JavaMail is now 1.4.1 | Woodstox is now 3.9 | Log4j is now 1.2.15 | | Also Apache Xerces and Xalan have changed | | | | | [Axis2] Release plan and road map for Axis2 1.4 release | | Deepal Jayasinghe | Tue, 18 Dec 2007 21:03:19 -0800 | | 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 | | | | | regards | | Alick Buckley | | LANSA Research and Development | LANSA Pty Ltd | | Phone: +61289070243 | | http://www.lansa.com | mailto:[EMAIL PROTECTED] | | | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHmBBFgNg6eWEDv1kRAmtvAJ9FAIrl0LbHfaBGaUAaMJyhhw0TdACgrnL2 I1xWyIUBV0O2fSQDEaRKerE= =jRAz -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Release plan and road map for Axis2 1.4 release
A few things that we'd like to see is better support for starting with Java and generating Schema and WSDL including: -Support for the latest versions of JAX-WS and JAXB and all of the annotations -The ability to exclude certain classes or packages when generating schema (similar to the Types.getStopClasses() feature in Axis 1.4) -The ability to generate the WSDL and Schema into seperate files, similar to how Sun's WsGen utility does. Thanks, Ben On 12/19/07, 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]
Re: [Axis2] Release plan and road map for Axis2 1.4 release
Hi Deepal, For our project, we need an option allowing the set the classloader to look for the libs in the aar files first rather than in web-inf/lib. Currently, if a WS in the AAR needs a lib and this one is in WEB-INF/lib AND in the AAR, the one in WEB-INF/lib is picked up, so this lib can't find a ressource in the aar. I sent a post some times ago that you replied: [quote] Hi all Axis2 users, I have a question about classloading in Axis2: If I have a JAR in WEB-INF/lib folder of the WAR and in the lib folder of my .aar service archive, which one will be loaded by Axis2 when a WebService calls a class in this JAR? If Axis2 loads the one in the war archive, will the files in the aar still be loadable by the JAR in the WAR? Well, that is one of the bug in Axis2 class loader and there is a JIRA as well . We wanted to fix that for 1.3 , somehow we didnt do that. I will fix that soon and make the feature available in nightly build [/quote] I would really need this evolution! Thanks in advance, Pierre Deepal Jayasinghe 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] -- View this message in context: http://www.nabble.com/-Axis2--Release-plan-and-road-map-for-Axis2-1.4-release-tp14411346p14434060.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Release plan and road map for Axis2 1.4 release
On Dec 19, 2007 2:03 PM, Mauro Molinari [EMAIL PROTECTED] wrote: Hi Deepal, personally I look forward to seeing the following issues solved: - https://issues.apache.org/jira/browse/AXIS2-3353 (using of Java wrapper types for optional elements + unwrapping of empty return types) fixed the issue please have a look at. - https://issues.apache.org/jira/browse/AXIS2-3354 (allow for sharing XSD schemas between services - I also posted a techical analysis of the problem) These are really critical for us. Cheers! -- Mauro Molinari Software Developer [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: [Axis2] Release plan and road map for Axis2 1.4 release
On Dec 20, 2007 12:00 PM, Pantvaidya, Vishwajit [EMAIL PROTECTED] wrote: Hi Deepal, I was facing a problem which I have described in http://www.nabble.com/RE%3A--Axis2--MTOM-Exception-with-Axis2-1.3-%22org.apache.axis2.databinding.ADBException%3A-Unexpected-subelement-Buffer%22-p14287244.html It pertains to the MTOM functionality where I get the error when the attachment element is not the last element in the message. Do you think this is a bug? If yes - I was wondering if it can be included in 1.4? Also in that thread, I have also outlined another MTOM issue ( https://issues.apache.org/jira/browse/AXIS2-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541070) that has been fixed after 1.3. To get the fix, I am using the axiom jars from a nightly build with my other 1.3 jars. Could you please create a jira with all the informaction needed to reproduce the issue? thanks, Amila. Finally, I am using a few wsdl2java post 1.3 fixes done by Amila. Because of this I am facing the prospect of using a mishmash of jars in production. Axi 1.4 is fine but a bugfix release earlier would be even better? - Vish. -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 19, 2007 7:52 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Release plan and road map for Axis2 1.4 release Hi! Could you please have a look at the following issue if it can be resolved to the Axis2 1.4 release. I have asked the axis mailing list about this issue a couple of times the last year but the problem has not been solved yet. We will definitely address this , please create a JIRA (if you have not create one already) -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.
Re: [Axis2] Release plan and road map for Axis2 1.4 release [SEC=UNCLASSIFIED]
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. **
RE: [Axis2] Release plan and road map for Axis2 1.4 release
Hi!
Could you please have a look at the following issue if it can be resolved to
the Axis2 1.4 release.
I have asked the axis mailing list about this issue a couple of times the last
year but the problem has not been solved yet.
When creating a web service using existing business logic with code first
approach I dont think custom exceptions are handled the way it should. (Axis2
1.3)
Assume the following server side code:
package axis2test;
public class MyService {
public MyService() {
}
public int addOneToPositiveValue(int value) throws CustomException {
if(value 1) {
throw(new CustomException());
}
return(value + 1);
}
}
package axis2test;
public class CustomException extends Exception {
private static final long serialVersionUID = 9;
public CustomException() {
super();
}
public String toString() {
return(super.toString() + ' axis2test.CustomException');
}
}
This is a webservice for MyService
axis2test.MyService
I deploy the service, let Axis2 generate the .wsdl file and then create a
client with the wsdl2java tool (xmlbeans style).
The custom exception appears on the client side in the AxisFault details field
within -tags together with a HUGE stack trace. This makes it hard for a client
to parse.
Is it posible to fix this to make it possible to use the generated client like:
try {
stub.addOneToPositiveValue(-1);
}
catch(CustomException c) {
...
...
}
catch(Exception e) {
...
...
}
I have tried the parameters drillDownTo... and sendStackTrace...
It doesn't solve the problem for me.
Thanks.
/Pär
_
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Release plan and road map for Axis2 1.4 release
Hi! Could you please have a look at the following issue if it can be resolved to the Axis2 1.4 release. I have asked the axis mailing list about this issue a couple of times the last year but the problem has not been solved yet. We will definitely address this , please create a JIRA (if you have not create one already) -Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Release plan and road map for Axis2 1.4 release
Hi Deepal, I was facing a problem which I have described in http://www.nabble.com/RE%3A--Axis2--MTOM-Exception-with-Axis2-1.3-%22org.apache.axis2.databinding.ADBException%3A-Unexpected-subelement-Buffer%22-p14287244.html It pertains to the MTOM functionality where I get the error when the attachment element is not the last element in the message. Do you think this is a bug? If yes - I was wondering if it can be included in 1.4? Also in that thread, I have also outlined another MTOM issue (https://issues.apache.org/jira/browse/AXIS2-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541070) that has been fixed after 1.3. To get the fix, I am using the axiom jars from a nightly build with my other 1.3 jars. Finally, I am using a few wsdl2java post 1.3 fixes done by Amila. Because of this I am facing the prospect of using a mishmash of jars in production. Axi 1.4 is fine but a bugfix release earlier would be even better? - Vish. -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 19, 2007 7:52 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Release plan and road map for Axis2 1.4 release Hi! Could you please have a look at the following issue if it can be resolved to the Axis2 1.4 release. I have asked the axis mailing list about this issue a couple of times the last year but the problem has not been solved yet. We will definitely address this , please create a JIRA (if you have not create one already) -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]
[Axis2] Release plan and road map for Axis2 1.4 release
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]
[Axis2] Release plan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all; As you all know Axis2 has been around for about two years and we are still patiently waiting for the magical 1.0. As far as I can see Axis2 is feature complete and it seems to me that the time has come to seriously consider the 1.0 release. I had to postpone 0.95 release due to few blockers and I hope that we will be able to fix those soon and will be able to release 0.95 before the end of this week. And there are few dependencies and tasks that need to be fulfilled before we declare 1.0 1.The list dims suggested (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0) 2.AXIOM release , I think its better if we can do Axis2 1.0 with AXIOM release rather than SNAPSHOT 3.JIRA fixing 4.code clean up 5.I18n There is a number of JIRAs on code generation and ADB and I think it is better if we can fix them after 0.95. We will need to do another quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that boils down to the following release plan, 1.Axis2 0.95 in this week (20-25) 2.Axis2 0.96 first week of the April 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0 Comments and suggestions are warmly welcome - -- Thanks, Deepal ~Future is Open~ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+ g9YUcE97iKPFKXcjVC7xT8E= =MIjV -END PGP SIGNATURE-
Re: [Axis2] Release plan
We are making solid progress with Axis2 and greatly appreciate the efforts of the developers. I hope that the issues we have addressed in 0.94 and submitted patches for will all be addressed in both 0.95 and 1.0: Support for choice particles Support for recursive data types Support for minOccurs=0 in the 0 case, i.e. both empty arrays and omitted optional parameters Allow subelements to have the same name and a different type than their parent element Correct OMStAXWrapper.getElementText() to obey the general contract of getElementText() in the parser==null case (leave the reader at the END_ELEMENT) I believe at least some of these are addressed in the current code base, but not all are yet; e.g., I think that Ajith is trying to add the choice particle support prior to the 0.95 release. Please allow this to happen if at all possible. FYI, the patches and discussion pertaining to the above are in the attached email. Thanks for the great system, Chuck Franz Fehringer [EMAIL PROTECTED] wrote on 03/20/2006 02:57:25 AM: Will the TCP monitor be factored out (- ws-commons) in release 1.0? Greetings Franz Deepal Jayasinghe schrieb: Hi all; As you all know Axis2 has been around for about two years and we are still patiently waiting for the magical 1.0. As far as I can see Axis2 is feature complete and it seems to me that the time has come to seriously consider the 1.0 release. I had to postpone 0.95 release due to few blockers and I hope that we will be able to fix those soon and will be able to release 0.95 before the end of this week. And there are few dependencies and tasks that need to be fulfilled before we declare 1.0 1.The list dims suggested (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0) 2.AXIOM release , I think its better if we can do Axis2 1.0 with AXIOM release rather than SNAPSHOT 3.JIRA fixing 4.code clean up 5.I18n There is a number of JIRAs on code generation and ADB and I think it is better if we can fix them after 0.95. We will need to do another quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that boils down to the following release plan, 1.Axis2 0.95 in this week (20-25) 2.Axis2 0.96 first week of the April 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0 Comments and suggestions are warmly welcome -- Thanks, Deepal ~Future is Open~ ---BeginMessage--- Thanks Ajith. I need to make progress on my project and so unfortunately have to fix the issues in 0.94 as they arise. We have a fairly complicated set of types in our wsdl to support. If only 0.95 was done with all your fixes in it (including choice)... :-) FYI, there was a bug in my fixes to ADBPullParser to handle minOccurs=0. The changes to next() fully resolve the issues without any change to the constructor. Also, the fixes to deserialization (code generated for the parse() methods) uncovered a bug in OMStAXWrapper.getElementText(). In the case where parser==null (i.e., working directly on an OMElement), it did not obey the proper contract for getElementText(). Specifically, it did not advance itself to the END_ELEMENT. This caused my parse() methods to parse the same element infinitely since they were always at the START_ELEMENT. This case appears to have only occured (in my uses so far) when the entire message body was a single element of simple type (e.g., document/literal message with an xsd:string element payload). In other cases, OMStAXWrapper apparently switched to the parser!=null state, which worked properly. The attached xml.src.patch fixes OMStAXWrapper.getElementText(). The attached adb.patch contains the updated fix to ADBPullParser. I included codegen.patch again just for completeness re. all the issues covered on this thread, although it has not changed from the prior message. Looking forward to 0.95! Chuck "Ajith Ranabahu" [EMAIL PROTECTED] wrote on 03/05/2006 05:53:56 PM: Hi chuck, is this a 0.94 issue ? I've done some (significant) changes to the de-ser code lately so things look different now. We handle the min occurs properly. Unfortunately the current code handles sequence properly but not "choice" or "all" (I'll be working on that soon though) I'll fix the codegen issues but I may not be able to apply your patches directly now Ajith On 3/5/06, Chuck Williams [EMAIL PROTECTED] wrote: Hi Ajith and all, I ran into another code generation problem. minOccurs=0 elements are not supported in the 0 case. I.e., for an optional element that is not present or a zero-length array, the parsing has bugs. The core serialization in adb also fails to handle this case. For the parsing (deserialization), the argumentCount mechanism in the generated parse() methods fails when no elements for a minOccurs=0 property are present. For serialization, the next() method in the ADBPullParser fails to handle zero-length arrays as it
Re: [Axis2] Release plan
Most definitely +1! Axis2 is now ready for prime time .. and we need much wider user feedback to make it move to the next level. We won't get that until we release 1.0. I propose we change 0.96 below to the label 1.0RC to signal to everyone that this is our planned 1.0 release. That will get more attention IMO. Sanjiva. On Mon, 2006-03-20 at 17:48 +0600, Deepal Jayasinghe wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all; As you all know Axis2 has been around for about two years and we are still patiently waiting for the magical 1.0. As far as I can see Axis2 is feature complete and it seems to me that the time has come to seriously consider the 1.0 release. I had to postpone 0.95 release due to few blockers and I hope that we will be able to fix those soon and will be able to release 0.95 before the end of this week. And there are few dependencies and tasks that need to be fulfilled before we declare 1.0 1.The list dims suggested (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0) 2.AXIOM release , I think its better if we can do Axis2 1.0 with AXIOM release rather than SNAPSHOT 3.JIRA fixing 4.code clean up 5.I18n There is a number of JIRAs on code generation and ADB and I think it is better if we can fix them after 0.95. We will need to do another quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that boils down to the following release plan, 1.Axis2 0.95 in this week (20-25) 2.Axis2 0.96 first week of the April 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0 Comments and suggestions are warmly welcome - -- Thanks, Deepal ~Future is Open~ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+ g9YUcE97iKPFKXcjVC7xT8E= =MIjV -END PGP SIGNATURE-
Re: [Axis2] Release plan
On Mon, 2006-03-20 at 13:57 +0100, Franz Fehringer wrote: Will the TCP monitor be factored out (- ws-commons) in release 1.0? This is an excellent idea. However, can someone offer to do the work? Its not a huge amount but it does require refactoring the code to change Java package names etc.. Sanjiva.
