Sandesha2C 0.90 Release
Hi All, Apache Sandesha2/C Team is pleased to announce the release of Apache Sandesha2/C version 0.90. You can download this release from http://ws.apache.org/sandesha/sandesha2/c/download.cgi This release is supposed to be used with the Axis2C 1.0.0 distribution which is released recently. Key Features: 1. Support for WS-ReliableMessaging in both client side and server side of Axis2C. (according the the WS-ReliableMessaging specification February 2005 and WS-ReliableMessaging specification August 2006). 2. Pluggable storage framework. 3. Configurable delivery assurances. Eexactly once delivery assurance is guaranteed. 4. Support for both SOAP 1.1 and 1.2. 5. Client API, which provides features for both general and advance users. 6. Samples to test RM scenarios. 7. Interoperablity with java and .net. 8. Documentation We welcome your early feedback on this implementation. Thanks for your interest in Sandesha2/C -- Apache Sandesha2/C Team -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-623) axis2c sets deprecated win32 socket options that avoid subsequent opening of sockets
axis2c sets deprecated win32 socket options that avoid subsequent opening of sockets Key: AXIS2C-623 URL: https://issues.apache.org/jira/browse/AXIS2C-623 Project: Axis2-C Issue Type: Bug Components: transport/http Affects Versions: 1.0.0, Current (Nightly), 1.1.0 Environment: Win32 Reporter: Juergen Haeussler In util/src/network_handler.c - lines 239-240 the default behaviour of socket creation through windows API gets changed: setsockopt(INVALID_SOCKET, SOL_SOCKET, SO_OPENTYPE, (char *)sock_opt, sizeof(sock_opt)); As you can find in the MSDN documentation for SOL_SOCKET Socket Options, one should not use this options: http://msdn2.microsoft.com/en-us/library/ms740532.aspx This option avoids the subsequent opening of sockets by other APIs like Orbacus (Corba). As we did comment out these two lines, everything worked correctly. So we assumed that this code is obsolete. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2C-623) axis2c sets deprecated win32 socket options that avoid subsequent opening of sockets
[ https://issues.apache.org/jira/browse/AXIS2C-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juergen Haeussler updated AXIS2C-623: - Attachment: citation_from_msdn.jpg axis2c sets deprecated win32 socket options that avoid subsequent opening of sockets Key: AXIS2C-623 URL: https://issues.apache.org/jira/browse/AXIS2C-623 Project: Axis2-C Issue Type: Bug Components: transport/http Affects Versions: 1.0.0, Current (Nightly), 1.1.0 Environment: Win32 Reporter: Juergen Haeussler Attachments: citation_from_msdn.jpg In util/src/network_handler.c - lines 239-240 the default behaviour of socket creation through windows API gets changed: setsockopt(INVALID_SOCKET, SOL_SOCKET, SO_OPENTYPE, (char *)sock_opt, sizeof(sock_opt)); As you can find in the MSDN documentation for SOL_SOCKET Socket Options, one should not use this options: http://msdn2.microsoft.com/en-us/library/ms740532.aspx This option avoids the subsequent opening of sockets by other APIs like Orbacus (Corba). As we did comment out these two lines, everything worked correctly. So we assumed that this code is obsolete. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-624) module handlers are invoked for service even when module is not engaged for the serivce
module handlers are invoked for service even when module is not engaged for the serivce --- Key: AXIS2C-624 URL: https://issues.apache.org/jira/browse/AXIS2C-624 Project: Axis2-C Issue Type: Bug Reporter: Damitha Kumarage Priority: Blocker I can see that even when a module is not engaged to a service(globally or service wise) handlers of that module is invoked for that service. This happens both for in and out path. This must be due to a change done to the engine very recently. I can cleary remember this was working correctly when I was testing sandesha2/C for release 0.90 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Guththila Parser axutil_env addition
Hi, I would like to volunteer for adding the axutil_env to the Guththila code as this is an urgent thing to do. I think I will be able to do it quickly (most probably before Monday) and there are few other things that I have to take care as well. The approach that I'm going to take is adding the axutil_env to the Guththila structures and use it from these structures. Supun.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Improved XML parser added to the SVN trunk
And if my company makes and sells software for a living? While this might be the best parser in world, its restrictive license makes it unacceptable for Axis C IMO unless the developers want to shut off big chunk of its users. -Original Message- From: Jimmy Zhang [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 1:56 AM To: Apache AXIS C Developers List Subject: Re: Improved XML parser added to the SVN trunk because it doesn't infect... if you are not redistributing... - Original Message - From: George Stanchev [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Thursday, June 21, 2007 9:12 PM Subject: RE: Improved XML parser added to the SVN trunk I don't get it. Which common misconception would allow me to link my company's software against that parser ( if used by axis-c) without virally infecting my software? -Original Message- From: Jimmy Zhang [mailto:[EMAIL PROTECTED] Sent: Thursday, June 21, 2007 1:07 PM To: Apache AXIS C Developers List Subject: Re: Improved XML parser added to the SVN trunk http://en.wikipedia.org/wiki/GNU_General_Public_License#Common_misconceptions for a user that is a go :-) - Original Message - From: Franz Fehringer [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Thursday, June 21, 2007 1:00 AM Subject: Re: Improved XML parser added to the SVN trunk But this is GPL and therefore a nogo?! Franz Jimmy Zhang schrieb: You guys should look at VTD-XML 2.1 in C... http://vtd-xml.sf.net - Original Message - From: Supun Kamburugamuva [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Wednesday, June 20, 2007 5:50 AM Subject: Improved XML parser added to the SVN trunk Hi, I'm happy to announce that I have added the new improved XML parser to the svn head. In the process I got lot of help from Milinda in writing some code and doing all the work necessary to run it on Linux. So my special thanks goes to Milinda. I have added the new parser with same name as the previous parser(Guththila). New parser is also named Guththila and old parser was removed from the svn head. This parser was written in a short time and because of tht there are some areas that need to be completed. Some of the areas that need immediate attention are: 1. Standardizing the error handling mechanism 2. Fixing memory leaks 3. Reformatting code I'm trying to fix these issues as far as I can but I have a fairy tight schedule (I'm in the middle of my semester) so anyone who is interested, please jump in and have a look. I have written this parser with one goal in mind and that is performance and I think we can achieve fair amount of performance gain with the new parser. I'm sure, still there are lot of areas where performance can be improved. Regards, Supun. - 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] -- Dr. Franz Fehringer (Dipl. Math.) Projektleiter Touristik-Systeme ISO Software Systeme GmbH Eichendorffstrasse 29 90491 Nürnberg Germany Tel.: +49/(911) - 99594-0 mailto:[EMAIL PROTECTED] http://www.isogmbh.de Amtsgericht Nürnberg HRB 18299 Geschäftsführer: Dipl.-Inform., Dipl.-Kaufm. Harald Goeb Sitz: Nürnberg - 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] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ** - 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,
Re: Improved XML parser added to the SVN trunk
sorry thought you were just a user ... - Original Message - From: George Stanchev [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Friday, June 22, 2007 7:43 AM Subject: RE: Improved XML parser added to the SVN trunk And if my company makes and sells software for a living? While this might be the best parser in world, its restrictive license makes it unacceptable for Axis C IMO unless the developers want to shut off big chunk of its users. -Original Message- From: Jimmy Zhang [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 1:56 AM To: Apache AXIS C Developers List Subject: Re: Improved XML parser added to the SVN trunk because it doesn't infect... if you are not redistributing... - Original Message - From: George Stanchev [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Thursday, June 21, 2007 9:12 PM Subject: RE: Improved XML parser added to the SVN trunk I don't get it. Which common misconception would allow me to link my company's software against that parser ( if used by axis-c) without virally infecting my software? -Original Message- From: Jimmy Zhang [mailto:[EMAIL PROTECTED] Sent: Thursday, June 21, 2007 1:07 PM To: Apache AXIS C Developers List Subject: Re: Improved XML parser added to the SVN trunk http://en.wikipedia.org/wiki/GNU_General_Public_License#Common_misconceptions for a user that is a go :-) - Original Message - From: Franz Fehringer [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Thursday, June 21, 2007 1:00 AM Subject: Re: Improved XML parser added to the SVN trunk But this is GPL and therefore a nogo?! Franz Jimmy Zhang schrieb: You guys should look at VTD-XML 2.1 in C... http://vtd-xml.sf.net - Original Message - From: Supun Kamburugamuva [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Wednesday, June 20, 2007 5:50 AM Subject: Improved XML parser added to the SVN trunk Hi, I'm happy to announce that I have added the new improved XML parser to the svn head. In the process I got lot of help from Milinda in writing some code and doing all the work necessary to run it on Linux. So my special thanks goes to Milinda. I have added the new parser with same name as the previous parser(Guththila). New parser is also named Guththila and old parser was removed from the svn head. This parser was written in a short time and because of tht there are some areas that need to be completed. Some of the areas that need immediate attention are: 1. Standardizing the error handling mechanism 2. Fixing memory leaks 3. Reformatting code I'm trying to fix these issues as far as I can but I have a fairy tight schedule (I'm in the middle of my semester) so anyone who is interested, please jump in and have a look. I have written this parser with one goal in mind and that is performance and I think we can achieve fair amount of performance gain with the new parser. I'm sure, still there are lot of areas where performance can be improved. Regards, Supun. - 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] -- Dr. Franz Fehringer (Dipl. Math.) Projektleiter Touristik-Systeme ISO Software Systeme GmbH Eichendorffstrasse 29 90491 Nürnberg Germany Tel.: +49/(911) - 99594-0 mailto:[EMAIL PROTECTED] http://www.isogmbh.de Amtsgericht Nürnberg HRB 18299 Geschäftsführer: Dipl.-Inform., Dipl.-Kaufm. Harald Goeb Sitz: Nürnberg - 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] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL
Re: Guththila Parser axutil_env addition
Hi Supun, Supun Kamburugamuva [EMAIL PROTECTED] writes: Hi, I would like to volunteer for adding the axutil_env to the Guththila code as this is an urgent thing to do. I think I will be able to do it quickly (most probably before Monday) and there are few other things that I have to take care as well. The approach that I'm going to take is adding the axutil_env to the Guththila structures and use it from these structures. Great !!! BTW can you make sure to get all our samples (It is just 6 or 7 samples)working with Guththila too. One more thing, I would like to pass axutil_env_t to every function rather than adding axutil_env_t to Guththila structure. Because it gives more Axis2/C like feeling and good to maintain consistency in function. I'm not sure whether its only my feeling, let see what others say too :) thanks, Dinesh -- Dinesh Premalal http://xydinesh.wordpress.com GPG ID : A255955C GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Improved XML parser added to the SVN trunk
I *AM* an user of axis-c, but I also would like sell my software (that contains axis-c) without opening its source. Apache License gives me this option, GPL - not. Are you willing to license your parser under Apache or compatible license? -Original Message- From: Jimmy Zhang [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 9:18 AM To: Apache AXIS C Developers List Subject: Re: Improved XML parser added to the SVN trunk sorry thought you were just a user ... - Original Message - From: George Stanchev [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Friday, June 22, 2007 7:43 AM Subject: RE: Improved XML parser added to the SVN trunk And if my company makes and sells software for a living? While this might be the best parser in world, its restrictive license makes it unacceptable for Axis C IMO unless the developers want to shut off big chunk of its users. -Original Message- From: Jimmy Zhang [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 1:56 AM To: Apache AXIS C Developers List Subject: Re: Improved XML parser added to the SVN trunk because it doesn't infect... if you are not redistributing... - Original Message - From: George Stanchev [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Thursday, June 21, 2007 9:12 PM Subject: RE: Improved XML parser added to the SVN trunk I don't get it. Which common misconception would allow me to link my company's software against that parser ( if used by axis-c) without virally infecting my software? -Original Message- From: Jimmy Zhang [mailto:[EMAIL PROTECTED] Sent: Thursday, June 21, 2007 1:07 PM To: Apache AXIS C Developers List Subject: Re: Improved XML parser added to the SVN trunk http://en.wikipedia.org/wiki/GNU_General_Public_License#Common_misconceptions for a user that is a go :-) - Original Message - From: Franz Fehringer [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Thursday, June 21, 2007 1:00 AM Subject: Re: Improved XML parser added to the SVN trunk But this is GPL and therefore a nogo?! Franz Jimmy Zhang schrieb: You guys should look at VTD-XML 2.1 in C... http://vtd-xml.sf.net - Original Message - From: Supun Kamburugamuva [EMAIL PROTECTED] To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Sent: Wednesday, June 20, 2007 5:50 AM Subject: Improved XML parser added to the SVN trunk Hi, I'm happy to announce that I have added the new improved XML parser to the svn head. In the process I got lot of help from Milinda in writing some code and doing all the work necessary to run it on Linux. So my special thanks goes to Milinda. I have added the new parser with same name as the previous parser(Guththila). New parser is also named Guththila and old parser was removed from the svn head. This parser was written in a short time and because of tht there are some areas that need to be completed. Some of the areas that need immediate attention are: 1. Standardizing the error handling mechanism 2. Fixing memory leaks 3. Reformatting code I'm trying to fix these issues as far as I can but I have a fairy tight schedule (I'm in the middle of my semester) so anyone who is interested, please jump in and have a look. I have written this parser with one goal in mind and that is performance and I think we can achieve fair amount of performance gain with the new parser. I'm sure, still there are lot of areas where performance can be improved. Regards, Supun. - 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] -- Dr. Franz Fehringer (Dipl. Math.) Projektleiter Touristik-Systeme ISO Software Systeme GmbH Eichendorffstrasse 29 90491 Nürnberg Germany Tel.: +49/(911) - 99594-0 mailto:[EMAIL PROTECTED] http://www.isogmbh.de Amtsgericht Nürnberg HRB 18299 Geschäftsführer: Dipl.-Inform., Dipl.-Kaufm. Harald Goeb Sitz: Nürnberg - 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] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or
Re: Guththila Parser axutil_env addition
Hi, I think if we want to maintain the consistency we will have to add axutil_env to every function. So I will do it in that way. Supun. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507138 ] balaji iyer commented on AXIS2-2814: Hi Dims, Amila, After replacing the Xerces Implmentation in the endorsed folder in the JRE and generating the Stubs, I receive the following error in my client code. Is this something new ? Exception in thread main org.apache.axis2.AxisFault: Transport out has not been set at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:379) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:380) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:202) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:142 ) at com.citi.serviceclient.ThailandServiceJmsStub.CardStatementOp(ThailandSe rviceJmsStub.java:163) rgds Balaji XSI:TYPE not being generated for SOAP JMS client requests - Key: AXIS2-2814 URL: https://issues.apache.org/jira/browse/AXIS2-2814 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: Win XP, AXIS2 (1.2) Reporter: balaji iyer Assignee: Amila Chinthaka Suriarachchi Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip I'm trying to run the SOAP JMS webservice which is hosted in businessworks. I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding. However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP. The issues is that the xsi type is not being generated for JMS requests. Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] balaji iyer reopened AXIS2-2814: Sorry for re-opening this issue but, now the nightly build throws an error for soap/jms binding that Transport type is not set XSI:TYPE not being generated for SOAP JMS client requests - Key: AXIS2-2814 URL: https://issues.apache.org/jira/browse/AXIS2-2814 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: Win XP, AXIS2 (1.2) Reporter: balaji iyer Assignee: Amila Chinthaka Suriarachchi Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip I'm trying to run the SOAP JMS webservice which is hosted in businessworks. I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding. However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP. The issues is that the xsi type is not being generated for JMS requests. Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Issue Comment Edited: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507166 ] balaji iyer edited comment on AXIS2-2814 at 6/22/07 1:44 AM: - Sorry for re-opening this issue but, now the nightly build throws an error for soap/jms binding that Transport out is not set was: Sorry for re-opening this issue but, now the nightly build throws an error for soap/jms binding that Transport type is not set XSI:TYPE not being generated for SOAP JMS client requests - Key: AXIS2-2814 URL: https://issues.apache.org/jira/browse/AXIS2-2814 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: Win XP, AXIS2 (1.2) Reporter: balaji iyer Assignee: Amila Chinthaka Suriarachchi Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip I'm trying to run the SOAP JMS webservice which is hosted in businessworks. I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding. However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP. The issues is that the xsi type is not being generated for JMS requests. Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1435) Can't generate code for more than one interface using wsdl2java
[ https://issues.apache.org/jira/browse/AXIS2-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507175 ] Alexey Zavizionov commented on AXIS2-1435: -- Fix doesn't approved! Please, reopen issue. Can't generate code for more than one interface using wsdl2java --- Key: AXIS2-1435 URL: https://issues.apache.org/jira/browse/AXIS2-1435 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1 Environment: Sun JDK 1.5, WinXP Reporter: yogen Assignee: Amila Chinthaka Suriarachchi I am using wsdl2java to generate code for WSRP WSDL, find WSDL at this location: https://svn.apache.org/repos/asf/portals/wsrp4j/trunk/wsdl Ideally, command wsdl2java -d xmlbeans -p com.sample -ss -sd -g -uri wsrp_service.wsdl should generate code for all the interfaces in WSDL but wsdl2java randomly picks up anyone interface and generates the code for it. When its run subsequently to generate code for other interfaces, it says INFO: File .\src\com\sample\WSRPServiceStub.java will not be overwritten. C:\work\WSRPwsdl2java -d adb -p com.sample -ss -sd -g -uri wsrp_service.wsdl -pn WSRPServiceDescriptionService Using AXIS2_HOME: C:\software\axis2-rc1 Using JAVA_HOME://ms/dist/msjava/PROJ/sunjdk/1.5.0_04 Retrieving document at 'wsrp_v1_bindings.wsdl', relative to 'file:/C:/work/WSRP/'. Retrieving document at 'wsrp_v1_interfaces.wsdl', relative to 'file:/C:/work/WSRP/wsrp_v1_bindings.wsdl'. Retrieving schema at 'wsrp_v1_types.xsd', relative to 'file:/C:/work/WSRP/wsrp_v1_interfaces.wsdl'. Retrieving schema at 'xml.xsd', relative to 'file:/C:/work/WSRP/wsrp_v1_types.xsd'. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\WSRPServiceSkeleton.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\WSRPServiceMessageReceiverInOut.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\InvalidRegistrationException.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\OperationFailedException.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\WSRPServiceCallbackHandler.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\InvalidRegistrationException.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\OperationFailedException.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\WSRPServiceStub.java will not be overwritten. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1435) Can't generate code for more than one interface using wsdl2java
[
https://issues.apache.org/jira/browse/AXIS2-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507176
]
Alexey Zavizionov commented on AXIS2-1435:
--
I use command line
-s -ss -sd -ssi -g -d none -t -o ${src.gen.dir} -ns2p
urn:oasis:names:tc:wsrp:v1:intf=org.exoplatform.services.wsrp.intf,urn:oasis:names:tc:wsrp:v1:types=org.exoplatform.services.wsrp.type,urn:oasis:names:tc:wsrp:v1:bind=org.exoplatform.services.wsrp.bind,urn:oasis:names:tc:wsrp:v1:wsdl=org.exoplatform.services.wsrp.wsdl
-p org.exoplatform.services.wsrp.wsdl -uri wsrp_service.wsdl
Can't generate code for more than one interface using wsdl2java
---
Key: AXIS2-1435
URL: https://issues.apache.org/jira/browse/AXIS2-1435
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Environment: Sun JDK 1.5, WinXP
Reporter: yogen
Assignee: Amila Chinthaka Suriarachchi
I am using wsdl2java to generate code for WSRP WSDL, find WSDL at this
location:
https://svn.apache.org/repos/asf/portals/wsrp4j/trunk/wsdl
Ideally, command
wsdl2java -d xmlbeans -p com.sample -ss -sd -g -uri wsrp_service.wsdl
should generate code for all the interfaces in WSDL but wsdl2java randomly
picks up anyone interface and generates the code for it.
When its run subsequently to generate code for other interfaces, it says
INFO: File .\src\com\sample\WSRPServiceStub.java will not be overwritten.
C:\work\WSRPwsdl2java -d adb -p com.sample -ss -sd -g -uri wsrp_service.wsdl
-pn WSRPServiceDescriptionService
Using AXIS2_HOME: C:\software\axis2-rc1
Using JAVA_HOME://ms/dist/msjava/PROJ/sunjdk/1.5.0_04
Retrieving document at 'wsrp_v1_bindings.wsdl', relative to
'file:/C:/work/WSRP/'.
Retrieving document at 'wsrp_v1_interfaces.wsdl', relative to
'file:/C:/work/WSRP/wsrp_v1_bindings.wsdl'.
Retrieving schema at 'wsrp_v1_types.xsd', relative to
'file:/C:/work/WSRP/wsrp_v1_interfaces.wsdl'.
Retrieving schema at 'xml.xsd', relative to
'file:/C:/work/WSRP/wsrp_v1_types.xsd'.
Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File .\src\com\sample\WSRPServiceSkeleton.java will not be overwritten.
Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File .\src\com\sample\WSRPServiceMessageReceiverInOut.java will not be
overwritten.
Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File .\src\com\sample\InvalidRegistrationException.java will not be
overwritten.
Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File .\src\com\sample\OperationFailedException.java will not be
overwritten.
Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File .\src\com\sample\WSRPServiceCallbackHandler.java will not be
overwritten.
Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File .\src\com\sample\InvalidRegistrationException.java will not be
overwritten.
Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File .\src\com\sample\OperationFailedException.java will not be
overwritten.
Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File .\src\com\sample\WSRPServiceStub.java will not be overwritten.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2839) c-server stubs: memset() missing
c-server stubs: memset() missing
Key: AXIS2-2839
URL: https://issues.apache.org/jira/browse/AXIS2-2839
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: codegen
Environment: Apache Axis2 SNAPSHOT build May 16th, 2007,
Linux
Reporter: Florian Steinborn
I guess I found a problem in generated sources. I try to get in touch with Axis
and play around with all the things... I have a service that returns an array
of structures that contain all possible datatypes - also float and double.
I used this class for generating the wsdl:
public class Dat{
public long l;
public shorts;
public int i;
public String str;
public floatfl;
public double dl;
}
The generated wsdl shows
xs:element name=Dat type=ns:Dat /
xs:complexType name=Dat
xs:sequence
xs:element name=dl type=xs:double /
xs:element name=fl type=xs:float /
xs:element name=i type=xs:int /
xs:element name=str nillable=true type=xs:string /
xs:element name=l type=xs:long /
xs:element name=s type=xs:short /
/xs:sequence
/xs:complexType
When you generate C-Server stubs the constructor function
shows:
AXIS2_EXTERN axis2_Dat_t* AXIS2_CALL
axis2_Dat_create(
const axutil_env_t *env )
{
axis2_Dat_t *Dat = NULL;
AXIS2_ENV_CHECK(env, NULL);
Dat = (axis2_Dat_t *) AXIS2_MALLOC(env-
allocator, sizeof(axis2_Dat_t));
/* *** missing ***
* memset( Dat, 0, sizeof(axis2_Dat_t));
*
*/
if(NULL == Dat)
{
AXIS2_ERROR_SET(env-error, AXIS2_ERROR_NO_MEMORY, AXIS2_FAILURE);
return NULL;
}
return Dat;
}
For more safety it would be desirable if the generation would add the memset()
call.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2820) SimpleHTTP server can not handle multiple threads (more than 20)
[ https://issues.apache.org/jira/browse/AXIS2-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507188 ] Oleg Kalnichevski commented on AXIS2-2820: -- My pleasure, Davanum. If the 'NIO thingy' does catch on, you should consider getting rid of SimpleHttpServer after all. Better data throughput provided by classic I/O in some scenarios may not outweigh the complexity and managerial overhead of having to maintain multiple HTTP transport implementations. Cheers Oleg SimpleHTTP server can not handle multiple threads (more than 20) Key: AXIS2-2820 URL: https://issues.apache.org/jira/browse/AXIS2-2820 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Deepal Jayasinghe Priority: Blocker Attachments: axis2-shs.patch When use two channel to invoke a service deploy in tomcat I ran into problem , what I did was I fire up 100 threads and invoke the service 100 times. Then the invocation become very slow , when I debug the code I realized that is due to limitation in SimpleHttp server. So how if we switch to jetty or embedded tomcat. To demonstrate the issue I will create and attach the test case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2-1.2 and rampart-1.2 problems
You need to use Axis 1.2 and Rampart 1.2. Otherwise, use Axis 1.1 with rampart 1.1 Get rampart 1.2 from here: http://apache.org/dist/ws/rampart/1_2/rampart-1.2.zip On 6/21/07, Evandro_Contato [EMAIL PROTECTED] wrote: Hi Kevin The especification of rampart1.1 it requires Axis2-1.1, in test rampart1.1 and Axis2-1.2 occurs the error :( some idea? thanks Evandro Kevin TierOne wrote: Check to make sure you have the correct version of Rampart. Note that the link on this page refers to Rampart 1.1 http://ws.apache.org/axis2/modules/index.html Kevin Hi, I use axis2-1.2 and rampart-1.2 however when compiling occurs the error ERROR AxisServlet:157 - java.lang.NoSuchMethodError: org.apache.axis2.context.MessageContext.isEngaged (Ljavax/xml/namespace/QName;)Z some idea of as to decide the problem? thanks Evandro P. Contato -- View this message in context: http://www.nabble.com/Axis2-1.2-and-rampart-1.2-problems-tf3961165.html#a11242267 Sent from the Axis - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2814. - Resolution: Fixed Balaji, Please don't reuse this jira for later issues. which are totally unrelated to the original problem. thanks, dims XSI:TYPE not being generated for SOAP JMS client requests - Key: AXIS2-2814 URL: https://issues.apache.org/jira/browse/AXIS2-2814 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: Win XP, AXIS2 (1.2) Reporter: balaji iyer Assignee: Amila Chinthaka Suriarachchi Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip I'm trying to run the SOAP JMS webservice which is hosted in businessworks. I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding. However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP. The issues is that the xsi type is not being generated for JMS requests. Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2676) Issues using two different implementations of JABX in Axis and WS
[ https://issues.apache.org/jira/browse/AXIS2-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507272 ] Jochen Wiedmann commented on AXIS2-2676: As indicated, I suppose the problem is on the users side. So far no response. I'll close the issue in the next two weeks, should I still receive no reply. Issues using two different implementations of JABX in Axis and WS - Key: AXIS2-2676 URL: https://issues.apache.org/jira/browse/AXIS2-2676 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Environment: Reproduced on Mac OSX, Solaris 10, and Windows. Using Java 1.4.2 and 1.6 update 1. Reporter: Bruce Hitchcock Assignee: Jochen Wiedmann I believe there is a conflict issue when a client WS uses Apache JaxMe or JAXBI inside of Axis 2 1.1.1. My WS service successfully runs outside the container via junits. However, the following occurs when deployed inside Axis2 Here is a stack trace. The service operation is defined to take an xs:string and return an xs:string. Both are really XML however, the marshalling and unmarshalling is handled inside of XAOHelper. This is where the exception happens. I believe doesnt contain ObjectFactory.class or jaxb.index is particlular to the JAXB implementation inside the jar files include with Axis2 (Sun's impl ?) and not to Apache JaxMe. This might be and issue of not specifing and implementation at run time. Any help will be greatly appreciated. 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR com.comcast.cable.sams.tts.service.xao.XAOHelper - com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR com.comcast.cable.sams.tts.service.xao.XAOHelper - com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver - javax.xml.bind.JAXBException: com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:118) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:328) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:254) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.Exception: javax.xml.bind.JAXBException: com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index at com.comcast.cable.sams.tts.service.xao.XAOHelper.marshall(Unknown Source) at
[jira] Created: (AXIS2-2840) When there is an error on a response with a SeparateListener, the fault gets sent back with addressing marked none
When there is an error on a response with a SeparateListener, the fault gets sent back with addressing marked none -- Key: AXIS2-2840 URL: https://issues.apache.org/jira/browse/AXIS2-2840 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Paul Fremantle Fix For: 1.3 I've noticed in some case where there are faults on handling a response message, that the SOAP fault is sent back on the backchannel addressed to none. This is a side effect of the bug https://issues.apache.org/jira/browse/AXIS2-2829 where none messages are actually getting through. Otherwise I wouldn't have seen this. However, I think really we should log these somewhere, since otherwise these faults will be never seen or found. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1670) Invalid Exception when deploying a service compiled in jdk1.5 in axis2 server running in jdk 1.4
[ https://issues.apache.org/jira/browse/AXIS2-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-1670. - Resolution: Fixed Invalid Exception when deploying a service compiled in jdk1.5 in axis2 server running in jdk 1.4 Key: AXIS2-1670 URL: https://issues.apache.org/jira/browse/AXIS2-1670 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Thilina Gunarathne Assignee: Deepal Jayasinghe Priority: Blocker Axis2 throws the following misleading Exception when deploying a service compiled in jdk1.5 in axis2 server running in jdk 1.4. Caused by: org.apache.axis2.deployment.DeploymentException: ClassNotFoundException Error in loading message receiver org.tempuri.mtom.MTOMServiceMessageReceiverInOut; nested exception is: java.lang.ClassNotFoundException: org.tempuri.mtom.MTOMServiceMessageReceiverInOut at org.apache.axis2.deployment.DescriptionBuilder.loadMessageReceiver(DescriptionBuilder.java:179) at org.apache.axis2.deployment.ServiceBuilder.processOperations(ServiceBuilder.java:601) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:257) ... 12 more Caused by: java.lang.ClassNotFoundException: org.tempuri.mtom.MTOMServiceMessageReceiverInOut at java.net.URLClassLoader$1.run(URLClassLoader.java:199) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at org.apache.axis2.util.Loader.loadClass(Loader.java:158) at org.apache.axis2.util.Loader.loadClass(Loader.java:130) at org.apache.axis2.deployment.DescriptionBuilder.loadMessageReceiver(DescriptionBuilder.java:175) ... 14 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1670) Invalid Exception when deploying a service compiled in jdk1.5 in axis2 server running in jdk 1.4
[ https://issues.apache.org/jira/browse/AXIS2-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507316 ] Davanum Srinivas commented on AXIS2-1670: - Fixed in svn revision 549817 Invalid Exception when deploying a service compiled in jdk1.5 in axis2 server running in jdk 1.4 Key: AXIS2-1670 URL: https://issues.apache.org/jira/browse/AXIS2-1670 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Thilina Gunarathne Assignee: Deepal Jayasinghe Priority: Blocker Axis2 throws the following misleading Exception when deploying a service compiled in jdk1.5 in axis2 server running in jdk 1.4. Caused by: org.apache.axis2.deployment.DeploymentException: ClassNotFoundException Error in loading message receiver org.tempuri.mtom.MTOMServiceMessageReceiverInOut; nested exception is: java.lang.ClassNotFoundException: org.tempuri.mtom.MTOMServiceMessageReceiverInOut at org.apache.axis2.deployment.DescriptionBuilder.loadMessageReceiver(DescriptionBuilder.java:179) at org.apache.axis2.deployment.ServiceBuilder.processOperations(ServiceBuilder.java:601) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:257) ... 12 more Caused by: java.lang.ClassNotFoundException: org.tempuri.mtom.MTOMServiceMessageReceiverInOut at java.net.URLClassLoader$1.run(URLClassLoader.java:199) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at org.apache.axis2.util.Loader.loadClass(Loader.java:158) at org.apache.axis2.util.Loader.loadClass(Loader.java:130) at org.apache.axis2.deployment.DescriptionBuilder.loadMessageReceiver(DescriptionBuilder.java:175) ... 14 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1954) HTTP 500 error returns when issung ?xsd for a service which does not have a wsdl
[ https://issues.apache.org/jira/browse/AXIS2-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-1954. - Resolution: Fixed Fix Version/s: (was: 1.3) HTTP 500 error returns when issung ?xsd for a service which does not have a wsdl - Key: AXIS2-1954 URL: https://issues.apache.org/jira/browse/AXIS2-1954 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: admin console Affects Versions: 1.1.1 Environment: Win XP, JDK1.5, Firefox 1.5.0.9 Reporter: Charitha Kankanamge Assignee: Deepal Jayasinghe Priority: Blocker I deployed a service which was configured to use rawXMLInOutmessagereceiver. So that I did not get the wsdl when I issuing the following url and correct message returned. http://localhost:8080/axis2/services/myService?wsdl error descriptionUnable to generate WSDL for this service/description ... However when I issuing http://localhost:8080/axis2/services/myService?xsd to get the schema, I got the following error. HTTP Status 500 - java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 java.util.ArrayList.RangeCheck(ArrayList.java:546) java.util.ArrayList.get(ArrayList.java:321) org.apache.axis2.description.AxisService.addNameSpaces(AxisService.java:555) org.apache.axis2.description.AxisService.getSchema(AxisService.java:551) org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:229) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:181) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Please give a proper error message in this scenario. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1954) HTTP 500 error returns when issung ?xsd for a service which does not have a wsdl
[ https://issues.apache.org/jira/browse/AXIS2-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507328 ] Davanum Srinivas commented on AXIS2-1954: - Fixed in svn revision 549821. Charitha, please verify. thanks, dims HTTP 500 error returns when issung ?xsd for a service which does not have a wsdl - Key: AXIS2-1954 URL: https://issues.apache.org/jira/browse/AXIS2-1954 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: admin console Affects Versions: 1.1.1 Environment: Win XP, JDK1.5, Firefox 1.5.0.9 Reporter: Charitha Kankanamge Assignee: Deepal Jayasinghe Priority: Blocker I deployed a service which was configured to use rawXMLInOutmessagereceiver. So that I did not get the wsdl when I issuing the following url and correct message returned. http://localhost:8080/axis2/services/myService?wsdl error descriptionUnable to generate WSDL for this service/description ... However when I issuing http://localhost:8080/axis2/services/myService?xsd to get the schema, I got the following error. HTTP Status 500 - java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 java.util.ArrayList.RangeCheck(ArrayList.java:546) java.util.ArrayList.get(ArrayList.java:321) org.apache.axis2.description.AxisService.addNameSpaces(AxisService.java:555) org.apache.axis2.description.AxisService.getSchema(AxisService.java:551) org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:229) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:181) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Please give a proper error message in this scenario. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2144) Code generated by wsdl2java doesnot compile
[ https://issues.apache.org/jira/browse/AXIS2-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507331 ] Davanum Srinivas commented on AXIS2-2144: - Amila, Here's the codegen issue running wsdl2java with xmlbeans INFO: Resolving schema with publicId [null] and systemId [xsd\common\Definitions.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No ty pe was mapped to the name ProcessingFailureException with namespace tmf854.v1 at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:256) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped to the name ProcessingFailureException with namespace tmf 854.v1 at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1338) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:238) ... 2 more Caused by: org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped to the name ProcessingFailureException with namespace tmf854.v1 at org.apache.axis2.wsdl.databinding.TypeMappingAdapter.getTypeMappingName(TypeMappingAdapter.java:79) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:2722) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:2639) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.generateMethodElement(AxisServiceBasedMultiLanguageEmitter.java:2181) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:2082) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.createDOMDocumentForSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1998) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1929) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1297) ... 3 more Code generated by wsdl2java doesnot compile --- Key: AXIS2-2144 URL: https://issues.apache.org/jira/browse/AXIS2-2144 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.1.1 Environment: Windows XP Reporter: Kamal Kang Assignee: Amila Chinthaka Suriarachchi Priority: Blocker Attachments: tmf854.zip The code generated by wsdl2java is giving following compilation errors. Wsdl files and XSDs are attached. compile.src: [javac] Compiling 20 source files to D:\mtosi\build\classes [javac] D:\mtosi\src\tellabs\mtosi\DiscoveryServiceMessageReceiverInOut.java :67: cannot find symbol [javac] symbol : method toOM(ws.v1.tmf854.ProcessingFailureExceptionT,boole an) [javac] location: class tellabs.mtosi.DiscoveryServiceMessageReceiverInOut [javac] f.setDetail(toOM(e.getFaultMessage(),false)); [javac] ^ [javac] D:\mtosi\src\tellabs\mtosi\DiscoveryServiceStub.java:153: cannot fin d symbol [javac] symbol : method toOM(ws.v1.tmf854.HeaderT,boolean) [javac] location: class tellabs.mtosi.DiscoveryServiceStub [javac] env.getHeader().addChild(toO M(param41, optimizeContent(new javax.xml.namespace.QName(, getAllCapabilities ; [javac] ^ [javac] D:\mtosi\src\tellabs\mtosi\DiscoveryServiceStub.java:269: cannot fin d symbol [javac] symbol : method toOM(ws.v1.tmf854.HeaderT,boolean) [javac] location: class tellabs.mtosi.DiscoveryServiceStub [javac] env.getHeader().addChild( toOM(param41, optimizeContent(new javax.xml.namespace.QName(, getAllCapabilit ies; [javac] ^ [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 3 errors BUILD FAILED D:\mtosi\build.xml:47: Compile failed; see the compiler error output for details You can reproduce by generating
[Axis2][continuum] BUILD FAILURE
Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2474 Build statistics: State: Failed Previous State: Ok Started at: Fri, 22 Jun 2007 14:35:44 + Finished at: Fri, 22 Jun 2007 15:05:12 + Total time: 29m 27s Build Trigger: Schedule Exit code: 70 Building machine hostname: ws.zones.apache.org Operating system : SunOS(unknown) Java version : 1.5.0_09(Sun Microsystems Inc.) Changes dims fix commented out section /webservices/axis2/trunk/java/modules/kernel/conf/axis2.xml dims Fix for AXIS2-1670 - Invalid Exception when deploying a service compiled in jdk1.5 in axis2 server running in jdk 1.4 /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/util/Loader.java dims Fix for AXIS2-1954 - HTTP 500 error returns when issung ?xsd for a service which does not have a wsdl /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/http/ListingAgent.java Output: Snipped Output: Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-enabledRepository/conf [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-enabledRepository/conf [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-enabledRepository/modules [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-fileCache-enabledRepository [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-fileCache-enabledRepository/conf [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-fileCache-enabledRepository/conf [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-fileCache-enabledRepository/modules [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/sample/groovy [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/sample/groovy/lib [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/sample/groovy/META-INF [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/sample/groovy/sample [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/sample/groovy/sample/groovy [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/sample/groovy [javac] Compiling 1 source file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/classes [javac] Note: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/samples/deprecated/groovy/src/sample/groovy/GroovyReceiver.java uses or overrides a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/sample/groovy/sample/groovy [delete] Deleting: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/classes/sample/groovy/GroovyReceiver.class [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/sample/groovy/META-INF [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/sample/groovy/lib [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/groovyRepo [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/groovyRepo/conf [mkdir] Created dir:
[jira] Commented: (AXIS2-2798) Soap action string mismatch does not prevent web service method from running.
[
https://issues.apache.org/jira/browse/AXIS2-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507418
]
Davanum Srinivas commented on AXIS2-2798:
-
David,
You can comment out SOAPMessageBodyBasedDispatcher from the axis2.xml
thanks,
dims
Soap action string mismatch does not prevent web service method from running.
-
Key: AXIS2-2798
URL: https://issues.apache.org/jira/browse/AXIS2-2798
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows XP Pro, Tomcat 5.0.28, Axis2 1.2
Reporter: David R. Kraus
Assignee: Deepal Jayasinghe
I have an old client which sends the following SOAP action:
http://company.com/webservices/GetInfo
However the new receiving service expects a different SOAP action:
http://company.com/webservices/v2/GetInfo
The idea is that when a service becomes incompatible with previous clients,
you change the namespace to prevent older clients from accessing. So, we
added a version number to the webservice namespace, and to all SOAP actions,
to control access.
However, I discovered that the Axis2 (1.2) service actually accepted the
GetInfo action/call and performed the operation, even though the version
number was missing from the SOAP action string. When I traced through Axis2
code I saw that the SOAP action mismatch was detected, but that the service
code was able to match the operation name GetInfo by comparing the SOAP
action suffix GetInfo to the operation GetInfo, and so proceeded with
handling it.
Anyway, is this a configurable behavior? Should this be happening?
I did some tracing through Axis2 code and this is what I saw:
1. SOAPActionBasedDispatcher.findOperation can't find /GetInfo
2. AddressingBasedDispathcer.findOperation can't find /GetInfo
3. SOAPMessageBodyBasedDispatcher.findOperation is able to find GetInfo and
processing continues successfully.
Below is SOAPMessageBodyBasedDispatcher.findOperation. See comment added to
source...
public AxisOperation findOperation(AxisService service, MessageContext
messageContext)
throws AxisFault {
OMElement bodyFirstChild =
messageContext.getEnvelope().getBody().getFirstElement();
AxisOperation axisOperation = null;
if (bodyFirstChild != null){
axisOperation =
service.getOperationByMessageElementQName(bodyFirstChild.getQName());
// this is required for services uses the RPC message receiver
if (axisOperation == null){
QName operationName = new QName(bodyFirstChild.getLocalName());
axisOperation = service.getOperation(operationName);//This
is where the axisOperation is finally found successfully.
}
}
return axisOperation;
}
My interpretation of the behavior was that Axis2 was able to find the
operation GetInfo, so it continued, even thought the initial soap action
string was not matched. When I tried an example of a soap action where the
soap action suffix did not match the operation name in the WSDL, then failure
occurred as expected. So, if I had a soap action like
http://company.com/webservices/GetData2 which was associated with an
operation named GetData, then the soap action mismatch would occur as before,
but SOAPMessageBodyBasedDispatcher.findOperation could not match GetData2
with GetData, so the request failed.
thanks, Dave
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2708) Auto generated code from wsdl for Test Program not correct for Async operation
[
https://issues.apache.org/jira/browse/AXIS2-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507421
]
Davanum Srinivas commented on AXIS2-2708:
-
Amila, You fixed this already right?
thanks,
dims
Auto generated code from wsdl for Test Program not correct for Async
operation
---
Key: AXIS2-2708
URL: https://issues.apache.org/jira/browse/AXIS2-2708
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.2
Environment: Windows XP, Using Axis2 1.2
Reporter: Rahul Shinde
Assignee: Amila Chinthaka Suriarachchi
Priority: Minor
Attachments: test.wsdl
Generated the Client Endpoint for async operation from the wsdl along with
the Test Program.
wsdl2java -p asyncclient -uri http://testsrv:8080/Service.asmx?wsdl -t -s
When i run the Test program, the request is sent and the response also comes
back
but it does not invoke the appropriate method in the Callback class of the
test program
If I trace the response in the onComplete(..) method, i can see the response
there,
but when it invokes the responseXXX() method on the callback Instance, it
doesnt
call the method defined within the Callback class but rather the method in
the abstract CallbackHandler class
which has a empty implementation.
The reason for this is the receiveXX() method in the Callback class in the
Test Program
takes a different argument than the one defined in the abstract
CallbackHandler class.
The Code snippet is as follows
In ServiceServiceSoapTest class
private class tempCallbackN1000C extends
asyncclient.ServiceServiceSoapCallbackHandler
{
public tempCallbackN1000C(){ super(null);}
public void
receiveResultHelloWorld(org.apache.axis2.client.async.AsyncResult result)
{
.
public void receiveResultHelloWorld(org.apache.axis2.client.async.AsyncResult
result)
should have been
public void
receiveResultHelloWorld(asyncclient.ServiceServiceSoapStub.HelloWorldResponse
result)
This is the method in the ServiceServiceSoapCallbackHandler class
public void
receiveResultHelloWorld(asyncclient.ServiceServiceSoapStub.HelloWorldResponse
result )
{ }
Hope this helps.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2658) Service is not Valid
[ https://issues.apache.org/jira/browse/AXIS2-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2658. - Resolution: Won't Fix Service is not Valid Key: AXIS2-2658 URL: https://issues.apache.org/jira/browse/AXIS2-2658 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: RAD, Axis2.1.2, WAS 6.1 Reporter: Bhagya Kitty Assignee: Deepal Jayasinghe Attachments: AcordWinsDbLookupService.wsdl org.apache.commons.logging.impl.Jdk14Logger info The AcordWinsDbLookupService service, which is not valid, caused java.lang.NullPointerException at org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(ArchiveReader.java:228) at org.apache.axis2.deployment.repository.util.ArchiveReader.processFilesInFolder(ArchiveReader.java:425) at org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:268) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:64) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:189) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:110) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:257) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:74) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:486) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:406) at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:185) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:316) at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1119) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:149) at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99) at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:742) at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:422) at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:275) at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:272) at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88) at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157) at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:655) at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:608) at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:333) at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:549) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1295) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129) at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:567) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:948) at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1478) at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:3811) at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:3893) at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1483) at com.ibm.ws.runtime.component.ApplicationMgrImpl$ApplicationNotifier.classChanged(ApplicationMgrImpl.java:1961) at com.ibm.ws.classloader.ClassLoaderManager.checkAndNotify(ClassLoaderManager.java:558) at com.ibm.ws.classloader.ClassLoaderManager.access$000(ClassLoaderManager.java:59) at com.ibm.ws.classloader.ClassLoaderManager$ReloadTimerTask.alarm(ClassLoaderManager.java:612) at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:90) at
[jira] Commented: (AXIS2-2658) Service is not Valid
[ https://issues.apache.org/jira/browse/AXIS2-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507422 ] Davanum Srinivas commented on AXIS2-2658: - This is a bad wsdl. thanks, dims Service is not Valid Key: AXIS2-2658 URL: https://issues.apache.org/jira/browse/AXIS2-2658 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: RAD, Axis2.1.2, WAS 6.1 Reporter: Bhagya Kitty Assignee: Deepal Jayasinghe Attachments: AcordWinsDbLookupService.wsdl org.apache.commons.logging.impl.Jdk14Logger info The AcordWinsDbLookupService service, which is not valid, caused java.lang.NullPointerException at org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(ArchiveReader.java:228) at org.apache.axis2.deployment.repository.util.ArchiveReader.processFilesInFolder(ArchiveReader.java:425) at org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:268) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:64) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:189) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:110) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:257) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:74) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:486) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:406) at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:185) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:316) at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1119) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:149) at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99) at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:742) at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:422) at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:275) at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:272) at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88) at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157) at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:655) at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:608) at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:333) at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:549) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1295) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129) at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:567) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:948) at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1478) at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:3811) at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:3893) at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1483) at com.ibm.ws.runtime.component.ApplicationMgrImpl$ApplicationNotifier.classChanged(ApplicationMgrImpl.java:1961) at com.ibm.ws.classloader.ClassLoaderManager.checkAndNotify(ClassLoaderManager.java:558) at com.ibm.ws.classloader.ClassLoaderManager.access$000(ClassLoaderManager.java:59) at com.ibm.ws.classloader.ClassLoaderManager$ReloadTimerTask.alarm(ClassLoaderManager.java:612) at
[jira] Commented: (AXIS2-2640) Enum class is not known to this JAXBContext
[ https://issues.apache.org/jira/browse/AXIS2-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507423 ] Davanum Srinivas commented on AXIS2-2640: - Nikhil, Is there a patch? is this problem fixed? thanks, dims Enum class is not known to this JAXBContext --- Key: AXIS2-2640 URL: https://issues.apache.org/jira/browse/AXIS2-2640 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker User reports seeing EnumString is not known to this jaxb context. Enum string does not have @XmlType/@XmlElement annotations, only @XmlEnum. So when the JAXBContext is created using context path it is not picked up. This is resolved by checking for enums in JAXBBlockImpl marshall/unmarshallByType methods. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2616) axis2-idea-plugin's pom.xml does not work
[ https://issues.apache.org/jira/browse/AXIS2-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2616. - Resolution: Fixed axis2-idea-plugin's pom.xml does not work - Key: AXIS2-2616 URL: https://issues.apache.org/jira/browse/AXIS2-2616 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Assignee: Lahiru Sandakith it's commented out in the root pom.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2615) integration module needs a working m2 pom.xml
[ https://issues.apache.org/jira/browse/AXIS2-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2615. - Resolution: Fixed integration module needs a working m2 pom.xml -- Key: AXIS2-2615 URL: https://issues.apache.org/jira/browse/AXIS2-2615 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Assignee: David Illsley -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2619) NPE during tomcat shutdown
[ https://issues.apache.org/jira/browse/AXIS2-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507426 ] Davanum Srinivas commented on AXIS2-2619: - We can't really handle this condition. please shutdown tomcat gracefully. thanks, dims NPE during tomcat shutdown -- Key: AXIS2-2619 URL: https://issues.apache.org/jira/browse/AXIS2-2619 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Environment: axis2 1.1.1 nightly build, linux, jdk 1.5.0_04-b05 Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe If the shutdown.sh script fails to stop the server and the kill -9 command is used the following error is logged (all configuration files are ok) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) ERROR [http-8081-Processor71] - Servlet.service() for servlet AxisServlet threw exception java.lang.NullPointerException at org.apache.log4j.Category.log(Category.java:849) at org.apache.commons.logging.impl.Log4JLogger.trace(Log4JLogger.java:146) at org.apache.commons.httpclient.HttpConnection.releaseConnection(HttpConnection.java:1173) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:221) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:547) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:175) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:72) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:310) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:205) at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:614) at org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:374) at org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:338) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:138) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2619) NPE during tomcat shutdown
[ https://issues.apache.org/jira/browse/AXIS2-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2619. - Resolution: Won't Fix NPE during tomcat shutdown -- Key: AXIS2-2619 URL: https://issues.apache.org/jira/browse/AXIS2-2619 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Environment: axis2 1.1.1 nightly build, linux, jdk 1.5.0_04-b05 Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe If the shutdown.sh script fails to stop the server and the kill -9 command is used the following error is logged (all configuration files are ok) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) ERROR [http-8081-Processor71] - Servlet.service() for servlet AxisServlet threw exception java.lang.NullPointerException at org.apache.log4j.Category.log(Category.java:849) at org.apache.commons.logging.impl.Log4JLogger.trace(Log4JLogger.java:146) at org.apache.commons.httpclient.HttpConnection.releaseConnection(HttpConnection.java:1173) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:221) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:547) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:175) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:72) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:310) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:205) at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:614) at org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:374) at org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:338) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:138) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2616) axis2-idea-plugin's pom.xml does not work
[ https://issues.apache.org/jira/browse/AXIS2-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507427 ] Davanum Srinivas commented on AXIS2-2616: - Already fixed. thanks, dims axis2-idea-plugin's pom.xml does not work - Key: AXIS2-2616 URL: https://issues.apache.org/jira/browse/AXIS2-2616 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Assignee: Lahiru Sandakith it's commented out in the root pom.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2615) integration module needs a working m2 pom.xml
[ https://issues.apache.org/jira/browse/AXIS2-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507428 ] Davanum Srinivas commented on AXIS2-2615: - Already fixed. integration module needs a working m2 pom.xml -- Key: AXIS2-2615 URL: https://issues.apache.org/jira/browse/AXIS2-2615 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Assignee: David Illsley -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2610) wsdl2java tool to allow additional java classes to be added for schema generation
[ https://issues.apache.org/jira/browse/AXIS2-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2610. - Resolution: Fixed wsdl2java tool to allow additional java classes to be added for schema generation - Key: AXIS2-2610 URL: https://issues.apache.org/jira/browse/AXIS2-2610 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: Tools Reporter: Bo Xie Assignee: Deepal Jayasinghe Bo, Please log an enhancement issue in JIRA for adding support to Java2WSDL to specify additional classes for which schema needs to be generated. thanks, dims On 4/28/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: You might try JiBX or XMLBeans. On 4/27/07, Bo Xie [EMAIL PROTECTED] wrote: Hi, I need advice on how to use java2wsdl or other tools to generate XML schema from java class for operation parameters. I understand using java2wsdl, it will generate the schema for all the data type used as parameter for the operation. But I could not find a way to generate schema for any derived class types. For example, if I have a method doSomething( BaseType type). The generated schema will include schema for BaseType only. I need to handcraft the schema for devicedTypeA, devicedTypeB into the WSDL schema definition in order to pass deviceTypeA, deviceTypeB instances in doSomething operation at runtime. Thanks for your time. -Bo -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2610) wsdl2java tool to allow additional java classes to be added for schema generation
[ https://issues.apache.org/jira/browse/AXIS2-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507429 ] Davanum Srinivas commented on AXIS2-2610: - Already fixed. thanks, dims wsdl2java tool to allow additional java classes to be added for schema generation - Key: AXIS2-2610 URL: https://issues.apache.org/jira/browse/AXIS2-2610 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: Tools Reporter: Bo Xie Assignee: Deepal Jayasinghe Bo, Please log an enhancement issue in JIRA for adding support to Java2WSDL to specify additional classes for which schema needs to be generated. thanks, dims On 4/28/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: You might try JiBX or XMLBeans. On 4/27/07, Bo Xie [EMAIL PROTECTED] wrote: Hi, I need advice on how to use java2wsdl or other tools to generate XML schema from java class for operation parameters. I understand using java2wsdl, it will generate the schema for all the data type used as parameter for the operation. But I could not find a way to generate schema for any derived class types. For example, if I have a method doSomething( BaseType type). The generated schema will include schema for BaseType only. I need to handcraft the schema for devicedTypeA, devicedTypeB into the WSDL schema definition in order to pass deviceTypeA, deviceTypeB instances in doSomething operation at runtime. Thanks for your time. -Bo -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2595) HttpServiceProcessor needs hashCode and equals
[ https://issues.apache.org/jira/browse/AXIS2-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507431 ] Davanum Srinivas commented on AXIS2-2595: - Michele, could i please ask you to submit fresh patches? thanks, dims HttpServiceProcessor needs hashCode and equals -- Key: AXIS2-2595 URL: https://issues.apache.org/jira/browse/AXIS2-2595 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: nightly Environment: all Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe Attachments: DefaultHttpConnectionManager.patch, HttpServiceProcessor.patch In HttpServiceProcessor: - I've introduced an unique identifier to provide the equals and hashCode methods. The equals method is needed because HttpServiceProcessor instances are stored in a LinkedList in DefaultHttpConnectionManager. - The destroy method closes the connections, instead of calling shutdown In DefaultHttpConnectionManager: - I don't think it is necessary to store the processors in a linked list and use a callback when they are done to remove them from the list because the executor has a working queue where waiting jobs are put. - Instead of an Executor, I would use an ExecutorService (created in the constructor, now passed as reference), which can be stopped in the shutdown method. At present, instead, is would still possible to submit requests (i.e. by calling process()) after calling the shutdown (and what would happen?) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2584) AAR deployment fails with a WSDL 2 document due to spaces in path to AAR file (interpreted as a URI)
[
https://issues.apache.org/jira/browse/AXIS2-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-2584.
-
Resolution: Fixed
Fix Version/s: (was: 1.3)
AAR deployment fails with a WSDL 2 document due to spaces in path to AAR file
(interpreted as a URI)
Key: AXIS2-2584
URL: https://issues.apache.org/jira/browse/AXIS2-2584
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: deployment
Affects Versions: nightly
Environment: Windows XP, Apache Tomcat 6
Reporter: Steven E. Harris
Assignee: Keith Godwin Chapman
Attachments: ArchiveReader.java.diff, ArchiveReader.java.diff
The class org.apache.axis2.deployment.repository.util.ArchiveReader attempts
to construct a JAR-based URI in its processWSDLFile() method:
} else if (axisServiceBuilder instanceof
WSDL20ToAxisServiceBuilder) {
// trying to use the jar scheme as the base URI. I think
this can be used to handle
// wsdl 1.1 as well without using a custome URI resolver.
Need to look at it later.
axisServiceBuilder.setBaseUri(
jar:file:// +
serviceArchiveFile.getAbsolutePath() + !/ + baseURI);
}
The call to serviceArchiveFile.getAbsolutePath() creates a path string with
embedded spaces and backslashes (on Windows). The java.net.URI constructor
rejects such a path, emitting an error such as:
INFO: Trouble processing wsdl file :Illegal character in opaque part at index
13: jar:file://C:\Program
Files\\apache-tomcat-6.0.10\webapps\axis2\WEB-INF\services\my.service.aar!/META-INF/myservice.wsdl
Note that it's complaining about the backslash after the C:' part.
The fix is simple: build the new URI from yet another URI:
axisServiceBuilder.setBaseUri(
jar: + serviceArchiveFile.toURI() + !/ +
baseURI);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2584) AAR deployment fails with a WSDL 2 document due to spaces in path to AAR file (interpreted as a URI)
[
https://issues.apache.org/jira/browse/AXIS2-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507432
]
Davanum Srinivas commented on AXIS2-2584:
-
Fixed in latest svn 549858
thanks,
dims
AAR deployment fails with a WSDL 2 document due to spaces in path to AAR file
(interpreted as a URI)
Key: AXIS2-2584
URL: https://issues.apache.org/jira/browse/AXIS2-2584
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: deployment
Affects Versions: nightly
Environment: Windows XP, Apache Tomcat 6
Reporter: Steven E. Harris
Assignee: Keith Godwin Chapman
Attachments: ArchiveReader.java.diff, ArchiveReader.java.diff
The class org.apache.axis2.deployment.repository.util.ArchiveReader attempts
to construct a JAR-based URI in its processWSDLFile() method:
} else if (axisServiceBuilder instanceof
WSDL20ToAxisServiceBuilder) {
// trying to use the jar scheme as the base URI. I think
this can be used to handle
// wsdl 1.1 as well without using a custome URI resolver.
Need to look at it later.
axisServiceBuilder.setBaseUri(
jar:file:// +
serviceArchiveFile.getAbsolutePath() + !/ + baseURI);
}
The call to serviceArchiveFile.getAbsolutePath() creates a path string with
embedded spaces and backslashes (on Windows). The java.net.URI constructor
rejects such a path, emitting an error such as:
INFO: Trouble processing wsdl file :Illegal character in opaque part at index
13: jar:file://C:\Program
Files\\apache-tomcat-6.0.10\webapps\axis2\WEB-INF\services\my.service.aar!/META-INF/myservice.wsdl
Note that it's complaining about the backslash after the C:' part.
The fix is simple: build the new URI from yet another URI:
axisServiceBuilder.setBaseUri(
jar: + serviceArchiveFile.toURI() + !/ +
baseURI);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2573) processHTTPPOSTRequest() does not correctly handle the case where HTTP request header SOAPAction is empty
[
https://issues.apache.org/jira/browse/AXIS2-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-2573.
-
Resolution: Fixed
processHTTPPOSTRequest() does not correctly handle the case where HTTP
request header SOAPAction is empty
---
Key: AXIS2-2573
URL: https://issues.apache.org/jira/browse/AXIS2-2573
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: transports
Affects Versions: 1.2, 1.1.1
Environment: All
Reporter: Charles McElrea
Assignee: Keith Godwin Chapman
In HTTPTransportUtils there is a method called processHTTPPOSTRequest(). It
correctly handles the case where the HTTP request header element SOAPAction
is set to :some URI and the case where SOAPAction:, but does not handle
the case where SOAPAction: empty. Specifically line, 183 of this module:
if ((soapActionHeader != null) soapActionHeader.charAt(0) == '\'
soapActionHeader.endsWith(\)) {
soapActionHeader = soapActionHeader.substring(1,
soapActionHeader.length() - 1);
}
will generate the following exception message
StringIndexOutOfBoundsException: String index out of range: 0, since
soapActionHeader is not null but is of zero length.
FYI - This problem can be fixed with the following code which insures that
the header has at least 2 characters before using the charAt() function.
if ((soapActionHeader != null) (soapActionHeader.length() 1)) {
if (soapActionHeader.charAt(0) == '\'
soapActionHeader.endsWith(\)) {
soapActionHeader = soapActionHeader.substring(1,
soapActionHeader.length() - 1);
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2573) processHTTPPOSTRequest() does not correctly handle the case where HTTP request header SOAPAction is empty
[
https://issues.apache.org/jira/browse/AXIS2-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507434
]
Davanum Srinivas commented on AXIS2-2573:
-
Already fixed.
thanks,
dims
processHTTPPOSTRequest() does not correctly handle the case where HTTP
request header SOAPAction is empty
---
Key: AXIS2-2573
URL: https://issues.apache.org/jira/browse/AXIS2-2573
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: transports
Affects Versions: 1.2, 1.1.1
Environment: All
Reporter: Charles McElrea
Assignee: Keith Godwin Chapman
In HTTPTransportUtils there is a method called processHTTPPOSTRequest(). It
correctly handles the case where the HTTP request header element SOAPAction
is set to :some URI and the case where SOAPAction:, but does not handle
the case where SOAPAction: empty. Specifically line, 183 of this module:
if ((soapActionHeader != null) soapActionHeader.charAt(0) == '\'
soapActionHeader.endsWith(\)) {
soapActionHeader = soapActionHeader.substring(1,
soapActionHeader.length() - 1);
}
will generate the following exception message
StringIndexOutOfBoundsException: String index out of range: 0, since
soapActionHeader is not null but is of zero length.
FYI - This problem can be fixed with the following code which insures that
the header has at least 2 characters before using the charAt() function.
if ((soapActionHeader != null) (soapActionHeader.length() 1)) {
if (soapActionHeader.charAt(0) == '\'
soapActionHeader.endsWith(\)) {
soapActionHeader = soapActionHeader.substring(1,
soapActionHeader.length() - 1);
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2640) Enum class is not known to this JAXBContext
[ https://issues.apache.org/jira/browse/AXIS2-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507435 ] Nikhil Thaker commented on AXIS2-2640: -- Dims - Issue has been resolved. I will be comitting the patch soon. Nikhil Thaker office: 512 838 9964 [EMAIL PROTECTED] Davanum Srinivas (JIRA) [EMAIL PROTECTED] 06/22/2007 10:51 AM To Nikhil V Thaker/Columbus/[EMAIL PROTECTED] cc Subject [jira] Commented: (AXIS2-2640) Enum class is not known to this JAXBContext [ https://issues.apache.org/jira/browse/AXIS2-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507423 ] Davanum Srinivas commented on AXIS2-2640: - Nikhil, Is there a patch? is this problem fixed? thanks, dims string does not have @XmlType/@XmlElement annotations, is not picked up. marshall/unmarshallByType methods. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. Enum class is not known to this JAXBContext --- Key: AXIS2-2640 URL: https://issues.apache.org/jira/browse/AXIS2-2640 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker User reports seeing EnumString is not known to this jaxb context. Enum string does not have @XmlType/@XmlElement annotations, only @XmlEnum. So when the JAXBContext is created using context path it is not picked up. This is resolved by checking for enums in JAXBBlockImpl marshall/unmarshallByType methods. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2567) Service activation with hotupdate not correct
[ https://issues.apache.org/jira/browse/AXIS2-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2567. - Resolution: Fixed Service activation with hotupdate not correct - Key: AXIS2-2567 URL: https://issues.apache.org/jira/browse/AXIS2-2567 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: deployment Affects Versions: nightly Reporter: nadir amra Assignee: Deepal Jayasinghe Running with latest build. hotupdate set to true in axis2.xml. An exploded POJO service is deployed and AXIS2 engine activates the service. From the ADMIN console, deactivate the service. If you click on the Available Services link you will find the service still active. For aar files, this seems to work fine. However, if the aar file is updated, the state goes to active. I would think in this case it should still be inactive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2567) Service activation with hotupdate not correct
[ https://issues.apache.org/jira/browse/AXIS2-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507436 ] Davanum Srinivas commented on AXIS2-2567: - Deepal, this is fixed now. right? thanks, dims Service activation with hotupdate not correct - Key: AXIS2-2567 URL: https://issues.apache.org/jira/browse/AXIS2-2567 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: deployment Affects Versions: nightly Reporter: nadir amra Assignee: Deepal Jayasinghe Running with latest build. hotupdate set to true in axis2.xml. An exploded POJO service is deployed and AXIS2 engine activates the service. From the ADMIN console, deactivate the service. If you click on the Available Services link you will find the service still active. For aar files, this seems to work fine. However, if the aar file is updated, the state goes to active. I would think in this case it should still be inactive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2539) Add support for the Endpoint.publish() API
[ https://issues.apache.org/jira/browse/AXIS2-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507438 ] Davanum Srinivas commented on AXIS2-2539: - Nick, Can we close this now? thanks, dims Add support for the Endpoint.publish() API -- Key: AXIS2-2539 URL: https://issues.apache.org/jira/browse/AXIS2-2539 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nick Gallardo Assignee: Nick Gallardo This JIRA will be used for adding more support to the JAX-WS dynamic Endpoint API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2543) Need to ensure we are generating wsdl only for SOAP 11 based bindings
[ https://issues.apache.org/jira/browse/AXIS2-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507437 ] Davanum Srinivas commented on AXIS2-2543: - Roy, Rich, Will this be fixed for 1.3? I don't see a patch thanks, dims Need to ensure we are generating wsdl only for SOAP 11 based bindings -- Key: AXIS2-2543 URL: https://issues.apache.org/jira/browse/AXIS2-2543 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Rich Scheuerle Priority: Minor Per the JAXWS spec. we should generate WSDL only for SOAP 11 bindings. However, the current logic is skewed so that we are generating WSDL for anything other than SOAP 12 bindings (i.e. XML/HTTP). This BT fixes that problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2][continuum] BUILD SUCCESSFUL
Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2477 Build statistics: State: Ok Previous State: Failed Started at: Fri, 22 Jun 2007 16:47:10 + Finished at: Fri, 22 Jun 2007 17:27:35 + Total time: 40m 24s Build Trigger: Schedule Exit code: 0 Building machine hostname: ws.zones.apache.org Operating system : SunOS(unknown) Java version : 1.5.0_09(Sun Microsystems Inc.) Changes rott LogicalMessageImpl should not be caching a local copy of message object /webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/handler/LogicalMessageContext.java /webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/handler/LogicalMessageImpl.java dims Fix for AXIS2-2584 - AAR deployment fails with a WSDL 2 document due to spaces in path to AAR file (interpreted as a URI) /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/ArchiveReader.java Output: Snipped Output: classes Running post goal: java:prepare-filesystem java:compile: [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes/META-INF [echo] Compiling to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes [javac] Compiling 2 source files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes java:jar-resources: Copying 2 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes/META-INF test:test: java:prepare-filesystem: Running post goal: java:prepare-filesystem java:compile: [echo] Compiling to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes java:jar-resources: test:prepare-filesystem: [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-reports test:test-resources: Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes test:compile: [javac] Compiling 1 source file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes [junit] Running org.apache.axis2.policy.model.MTOMAssertionTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.475 sec jar:jar: [jar] Building jar: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/axis2-mtompolicy-SNAPSHOT.jar jar:install: [echo] Installing... Uploading to org.apache.axis2/jars/axis2-mtompolicy-SNAPSHOT.jar: (8K) Uploading to org.apache.axis2/poms/axis2-mtompolicy-SNAPSHOT.pom: (13K) + | Executing multiproject:install-callback Apache Axis 2.0 - ping | Memory: 43M/59M + DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml build:end: build:start: multiproject:install-callback: [echo] Running jar:install for Apache Axis 2.0 - ping java:prepare-filesystem: [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes Running post goal: java:prepare-filesystem java:compile: [echo] Compiling to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes [javac] Compiling 3 source files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes [javac] Note: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/src/org/apache/axis2/ping/PingMessageReceiver.java uses or overrides a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. Running post goal: java:compile [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes/META-INF [copy] Copying 1 file to
[jira] Closed: (AXIS2-2640) Enum class is not known to this JAXBContext
[ https://issues.apache.org/jira/browse/AXIS2-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker closed AXIS2-2640. Enum class is not known to this JAXBContext --- Key: AXIS2-2640 URL: https://issues.apache.org/jira/browse/AXIS2-2640 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker User reports seeing EnumString is not known to this jaxb context. Enum string does not have @XmlType/@XmlElement annotations, only @XmlEnum. So when the JAXBContext is created using context path it is not picked up. This is resolved by checking for enums in JAXBBlockImpl marshall/unmarshallByType methods. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2640) Enum class is not known to this JAXBContext
[ https://issues.apache.org/jira/browse/AXIS2-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker resolved AXIS2-2640. -- Resolution: Fixed patch attached to JIRA Axis2-2841 resolves this issue. Axis2-2841 has been resolved with Revision 549873. Revision #549873 Enum class is not known to this JAXBContext --- Key: AXIS2-2640 URL: https://issues.apache.org/jira/browse/AXIS2-2640 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker User reports seeing EnumString is not known to this jaxb context. Enum string does not have @XmlType/@XmlElement annotations, only @XmlEnum. So when the JAXBContext is created using context path it is not picked up. This is resolved by checking for enums in JAXBBlockImpl marshall/unmarshallByType methods. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2841) Array Unmarshalling Failure on start from java RPC Case
[ https://issues.apache.org/jira/browse/AXIS2-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker resolved AXIS2-2841. -- Resolution: Fixed Revision #549873 Array Unmarshalling Failure on start from java RPC Case --- Key: AXIS2-2841 URL: https://issues.apache.org/jira/browse/AXIS2-2841 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker Attachments: JIRA_2841_UnmarshallingRPCStringArray.txt In start from java case for RPC the Unmarshalling of request fails when the server implementation has a String[] defnied as input parameter to the operation while the sei defines a wrapped StringArray with ListString. This scenario only happens in start from java case. I will provide the fix for this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] Handler interface (cleanup(), flowComplete() and errors)
A few questions about the Handler interface based on recent conversations: 1) cleanup() never gets called. Can we remove it now that we've got flowComplete()? 2) flowComplete() seems somewhat flawed in that there is currently no way (AFAICT) to conclusively determine whether it is being called as a result of a fault/thrown exception or due to the normal termination of processing. This leaves no easy way for Handler developers to do rollbacks of any work they've done. It appears we used to have revoke(), which I think seems like the right thing (it's easier to code an explicit fault handler API than it is to remember to check for something that the compiler won't tell you about), but that was apparently replaced with flowComplete()? PROPOSAL - add a failureReason field (of type Exception) to MessageContext, and ensure that the engine ALWAYS sets this if we have to back out the processing chain due to an error. Leave flowComplete() as is, but now implementors can mc.getFailureReason() and react appropriately. 3) Why are we forcing every Handler to keep a pointer to it's HandlerDesc? We only call this in a couple of places (Phase), and IMHO it clutters up the interface unnecessarily. It seems like Phase should be keeping HandlerDescs, and those should be pointing to Handlers... that would more loosely and cleanly decouple the two classes. Comments/thoughts? Thanks, --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] JIRA Issues for Axis2 1.3 - 2 Buckets
Team, There are 2 buckets now. Any JIRA we want to fix for 1.3 should be marked by setting the Fix Version to 1.3. If we *SHOULD NOT* release 1.3 if a specific JIRA is *NOT FIXED*, then please make it a blocker. If you are making a new JIRA a blocker, please set the Fix Version to 1.3 as well. Is this agreeable? thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2482) Hot update fails when an annotated pojo is deployed
[ https://issues.apache.org/jira/browse/AXIS2-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507440 ] Davanum Srinivas commented on AXIS2-2482: - Deepal, this is fixed now right? thanks, dims Hot update fails when an annotated pojo is deployed --- Key: AXIS2-2482 URL: https://issues.apache.org/jira/browse/AXIS2-2482 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: winxp, jdk15, tomcat 6.0.10 Reporter: Charitha Kankanamge Assignee: Deepal Jayasinghe Hotupdate does not work when a pojo annotated class is deployed. Following exception can be seen in tomcat logs when updating and deploying a pojo annotated class. org.apache.axis2.AxisFault: Two services cannot have same name. A service with the pingserviceService.pingservicePort name already exists in the system. at org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:266) at org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:252) at org.apache.axis2.deployment.POJODeployer.deploy(POJODeployer.java:111) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:586) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:61 ) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:76) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Steps to reproduce: === 1. Create an annotated pojo (Set hotupdate=true in axis2.xml) 2. Depoy it on tomcat 3. Modify the class 4. Replace the pojo class with changed one -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2841) Array Unmarshalling Failure on start from java RPC Case
[ https://issues.apache.org/jira/browse/AXIS2-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker updated AXIS2-2841: - Attachment: JIRA_2841_UnmarshallingRPCStringArray.txt Array Unmarshalling Failure on start from java RPC Case --- Key: AXIS2-2841 URL: https://issues.apache.org/jira/browse/AXIS2-2841 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker Attachments: JIRA_2841_UnmarshallingRPCStringArray.txt In start from java case for RPC the Unmarshalling of request fails when the server implementation has a String[] defnied as input parameter to the operation while the sei defines a wrapped StringArray with ListString. This scenario only happens in start from java case. I will provide the fix for this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2610) wsdl2java tool to allow additional java classes to be added for schema generation
[ https://issues.apache.org/jira/browse/AXIS2-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507446 ] Bo Xie commented on AXIS2-2610: --- Hi Dims, Thanks for the good news. How do I get the fix? Any doc on the new command options? Thanks, -Bo wsdl2java tool to allow additional java classes to be added for schema generation - Key: AXIS2-2610 URL: https://issues.apache.org/jira/browse/AXIS2-2610 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: Tools Reporter: Bo Xie Assignee: Deepal Jayasinghe Bo, Please log an enhancement issue in JIRA for adding support to Java2WSDL to specify additional classes for which schema needs to be generated. thanks, dims On 4/28/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: You might try JiBX or XMLBeans. On 4/27/07, Bo Xie [EMAIL PROTECTED] wrote: Hi, I need advice on how to use java2wsdl or other tools to generate XML schema from java class for operation parameters. I understand using java2wsdl, it will generate the schema for all the data type used as parameter for the operation. But I could not find a way to generate schema for any derived class types. For example, if I have a method doSomething( BaseType type). The generated schema will include schema for BaseType only. I need to handcraft the schema for devicedTypeA, devicedTypeB into the WSDL schema definition in order to pass deviceTypeA, deviceTypeB instances in doSomething operation at runtime. Thanks for your time. -Bo -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2841) Array Unmarshalling Failure on start from java RPC Case
Array Unmarshalling Failure on start from java RPC Case --- Key: AXIS2-2841 URL: https://issues.apache.org/jira/browse/AXIS2-2841 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker In start from java case for RPC the Unmarshalling of request fails when the server implementation has a String[] defnied as input parameter to the operation while the sei defines a wrapped StringArray with ListString. This scenario only happens in start from java case. I will provide the fix for this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2482) Hot update fails when an annotated pojo is deployed
[ https://issues.apache.org/jira/browse/AXIS2-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2482. - Resolution: Fixed Hot update fails when an annotated pojo is deployed --- Key: AXIS2-2482 URL: https://issues.apache.org/jira/browse/AXIS2-2482 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: winxp, jdk15, tomcat 6.0.10 Reporter: Charitha Kankanamge Assignee: Deepal Jayasinghe Hotupdate does not work when a pojo annotated class is deployed. Following exception can be seen in tomcat logs when updating and deploying a pojo annotated class. org.apache.axis2.AxisFault: Two services cannot have same name. A service with the pingserviceService.pingservicePort name already exists in the system. at org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:266) at org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:252) at org.apache.axis2.deployment.POJODeployer.deploy(POJODeployer.java:111) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:586) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:61 ) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:76) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Steps to reproduce: === 1. Create an annotated pojo (Set hotupdate=true in axis2.xml) 2. Depoy it on tomcat 3. Modify the class 4. Replace the pojo class with changed one -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2478) Documentation should be provided for POJO annotation feature
[ https://issues.apache.org/jira/browse/AXIS2-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2478: Assignee: Chatra Nakkawita (was: Deepal Jayasinghe) Documentation should be provided for POJO annotation feature Key: AXIS2-2478 URL: https://issues.apache.org/jira/browse/AXIS2-2478 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation Affects Versions: 1.2 Reporter: Charitha Kankanamge Assignee: Chatra Nakkawita User guides/documents should be provided for POJO annotation support. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-2841) Array Unmarshalling Failure on start from java RPC Case
[ https://issues.apache.org/jira/browse/AXIS2-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker closed AXIS2-2841. This JIRA also resolves issue in JIRA Axis2-2640 Array Unmarshalling Failure on start from java RPC Case --- Key: AXIS2-2841 URL: https://issues.apache.org/jira/browse/AXIS2-2841 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker Attachments: JIRA_2841_UnmarshallingRPCStringArray.txt In start from java case for RPC the Unmarshalling of request fails when the server implementation has a String[] defnied as input parameter to the operation while the sei defines a wrapped StringArray with ListString. This scenario only happens in start from java case. I will provide the fix for this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Work started: (AXIS2-2640) Enum class is not known to this JAXBContext
[ https://issues.apache.org/jira/browse/AXIS2-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AXIS2-2640 started by Nikhil Thaker. Enum class is not known to this JAXBContext --- Key: AXIS2-2640 URL: https://issues.apache.org/jira/browse/AXIS2-2640 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker User reports seeing EnumString is not known to this jaxb context. Enum string does not have @XmlType/@XmlElement annotations, only @XmlEnum. So when the JAXBContext is created using context path it is not picked up. This is resolved by checking for enums in JAXBBlockImpl marshall/unmarshallByType methods. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2584) AAR deployment fails with a WSDL 2 document due to spaces in path to AAR file (interpreted as a URI)
[
https://issues.apache.org/jira/browse/AXIS2-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507456
]
Steven E. Harris commented on AXIS2-2584:
-
Thanks for following through with this one.
AAR deployment fails with a WSDL 2 document due to spaces in path to AAR file
(interpreted as a URI)
Key: AXIS2-2584
URL: https://issues.apache.org/jira/browse/AXIS2-2584
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: deployment
Affects Versions: nightly
Environment: Windows XP, Apache Tomcat 6
Reporter: Steven E. Harris
Assignee: Keith Godwin Chapman
Attachments: ArchiveReader.java.diff, ArchiveReader.java.diff
The class org.apache.axis2.deployment.repository.util.ArchiveReader attempts
to construct a JAR-based URI in its processWSDLFile() method:
} else if (axisServiceBuilder instanceof
WSDL20ToAxisServiceBuilder) {
// trying to use the jar scheme as the base URI. I think
this can be used to handle
// wsdl 1.1 as well without using a custome URI resolver.
Need to look at it later.
axisServiceBuilder.setBaseUri(
jar:file:// +
serviceArchiveFile.getAbsolutePath() + !/ + baseURI);
}
The call to serviceArchiveFile.getAbsolutePath() creates a path string with
embedded spaces and backslashes (on Windows). The java.net.URI constructor
rejects such a path, emitting an error such as:
INFO: Trouble processing wsdl file :Illegal character in opaque part at index
13: jar:file://C:\Program
Files\\apache-tomcat-6.0.10\webapps\axis2\WEB-INF\services\my.service.aar!/META-INF/myservice.wsdl
Note that it's complaining about the backslash after the C:' part.
The fix is simple: build the new URI from yet another URI:
axisServiceBuilder.setBaseUri(
jar: + serviceArchiveFile.toURI() + !/ +
baseURI);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2610) wsdl2java tool to allow additional java classes to be added for schema generation
[ https://issues.apache.org/jira/browse/AXIS2-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507471 ] Davanum Srinivas commented on AXIS2-2610: - Java2WSDL has the following option -xc extra class : Extra class for which schematype must be generated. Please use that, you can use several -xc 's if you have many classes. Please use latest nightly build. thanks, dims wsdl2java tool to allow additional java classes to be added for schema generation - Key: AXIS2-2610 URL: https://issues.apache.org/jira/browse/AXIS2-2610 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: Tools Reporter: Bo Xie Assignee: Deepal Jayasinghe Bo, Please log an enhancement issue in JIRA for adding support to Java2WSDL to specify additional classes for which schema needs to be generated. thanks, dims On 4/28/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: You might try JiBX or XMLBeans. On 4/27/07, Bo Xie [EMAIL PROTECTED] wrote: Hi, I need advice on how to use java2wsdl or other tools to generate XML schema from java class for operation parameters. I understand using java2wsdl, it will generate the schema for all the data type used as parameter for the operation. But I could not find a way to generate schema for any derived class types. For example, if I have a method doSomething( BaseType type). The generated schema will include schema for BaseType only. I need to handcraft the schema for devicedTypeA, devicedTypeB into the WSDL schema definition in order to pass deviceTypeA, deviceTypeB instances in doSomething operation at runtime. Thanks for your time. -Bo -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r549910 - /webservices/axis2/trunk/java/modules/kernel/project.xml
Chinthaka,
What *exactly* did you change :( Please keep formatting changes
separate from actual changes :(
thanks,
dims
On 6/22/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: chinthaka
Date: Fri Jun 22 11:01:42 2007
New Revision: 549910
URL: http://svn.apache.org/viewvc?view=revrev=549910
Log:
Adding SSL extensions in to project.xml. Eventhough code that uses those
classes are excluded from the build my poor IDE is not smart enough to detect
maven settings ;)
BTW, I can see Synapse name in Axis2. I hope this will be removed soon :)
Modified:
webservices/axis2/trunk/java/modules/kernel/project.xml
Modified: webservices/axis2/trunk/java/modules/kernel/project.xml
URL:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/project.xml?view=diffrev=549910r1=549909r2=549910
==
--- webservices/axis2/trunk/java/modules/kernel/project.xml (original)
+++ webservices/axis2/trunk/java/modules/kernel/project.xml Fri Jun 22 11:01:42
2007
@@ -23,10 +23,11 @@
nameApache Axis 2.0 - Kernel/name
idaxis2-kernel/id
groupIdorg.apache.axis2/groupId
-descriptionCore Parts of Axis 2.0. This includes Axis 2.0 engine, Client API,
Addressing support, etc.,/description
+descriptionCore Parts of Axis 2.0. This includes Axis 2.0 engine, Client
API, Addressing support, etc.,
+/description
dependencies
- dependency
+dependency
groupIdorg.apache.ws.commons.axiom/groupId
artifactIdaxiom-api/artifactId
version${axiom.version}/version
@@ -38,7 +39,7 @@
/dependency
!-- external JARs --
-
+
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
@@ -63,14 +64,14 @@
moduletrue/module
/properties
/dependency
- dependency
-groupIdservletapi/groupId
-artifactIdservletapi/artifactId
-version${servletapi.version}/version
-properties
- moduletrue/module
-/properties
- /dependency
+dependency
+groupIdservletapi/groupId
+artifactIdservletapi/artifactId
+version${servletapi.version}/version
+properties
+moduletrue/module
+/properties
+/dependency
dependency
groupIdcommons-httpclient/groupId
artifactIdcommons-httpclient/artifactId
@@ -87,14 +88,14 @@
moduletrue/module
/properties
/dependency
- dependency
- groupIdcommons-fileupload/groupId
- artifactIdcommons-fileupload/artifactId
- version${commons.fileupload.version}/version
- properties
- moduletrue/module
- /properties
- /dependency
+dependency
+groupIdcommons-fileupload/groupId
+artifactIdcommons-fileupload/artifactId
+version${commons.fileupload.version}/version
+properties
+moduletrue/module
+/properties
+/dependency
dependency
groupIdhttpcomponents-httpcore/groupId
artifactIdjakarta-httpcore/artifactId
@@ -102,7 +103,7 @@
properties
moduletrue/module
/properties
-/dependency
+/dependency
dependency
groupIdhttpcomponents-httpcore/groupId
artifactIdjakarta-httpcore-nio/artifactId
@@ -110,9 +111,9 @@
properties
moduletrue/module
/properties
-/dependency
+/dependency
!--added this to support to keep WSDL information in AxisService--
- dependency
+dependency
groupIdorg.apache.ws.commons.schema/groupId
artifactIdXmlSchema/artifactId
version${XmlSchema.version}/version
@@ -157,20 +158,20 @@
moduletrue/module
/properties
/dependency
-
- dependency
- groupIdjaxen/groupId
- artifactIdjaxen/artifactId
- version${jaxen.version}/version
- properties
- moduletrue/module
- /properties
- urlhttp://www.ibiblio.org/maven/jaxen/jars//url
-/dependency
-
- !--for java2wsdl generation we use JAM , so there should be a dependency
on the annogen jar or--
+
+dependency
+groupIdjaxen/groupId
+artifactIdjaxen/artifactId
+version${jaxen.version}/version
+properties
+moduletrue/module
+/properties
+urlhttp://www.ibiblio.org/maven/jaxen/jars//url
+/dependency
+
+!--for java2wsdl generation we use JAM , so there should be a dependency
on the annogen jar or--
!--XML Beans--
- dependency
+dependency
Re: [axis2] Handler interface (cleanup(), flowComplete() and errors)
Glen, +1 to #1 and #2. I think we should leave #3 as-is. If we do just #1 and #2, people who already have classes that implement Handler's will not have to change anything. thanks, dims On 6/22/07, Glen Daniels [EMAIL PROTECTED] wrote: A few questions about the Handler interface based on recent conversations: 1) cleanup() never gets called. Can we remove it now that we've got flowComplete()? 2) flowComplete() seems somewhat flawed in that there is currently no way (AFAICT) to conclusively determine whether it is being called as a result of a fault/thrown exception or due to the normal termination of processing. This leaves no easy way for Handler developers to do rollbacks of any work they've done. It appears we used to have revoke(), which I think seems like the right thing (it's easier to code an explicit fault handler API than it is to remember to check for something that the compiler won't tell you about), but that was apparently replaced with flowComplete()? PROPOSAL - add a failureReason field (of type Exception) to MessageContext, and ensure that the engine ALWAYS sets this if we have to back out the processing chain due to an error. Leave flowComplete() as is, but now implementors can mc.getFailureReason() and react appropriately. 3) Why are we forcing every Handler to keep a pointer to it's HandlerDesc? We only call this in a couple of places (Phase), and IMHO it clutters up the interface unnecessarily. It seems like Phase should be keeping HandlerDescs, and those should be pointing to Handlers... that would more loosely and cleanly decouple the two classes. Comments/thoughts? Thanks, --Glen - 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]
[jira] Assigned: (AXIS2-2842) SOAPMessageContext.getHeaders() returns null
[ https://issues.apache.org/jira/browse/AXIS2-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker reassigned AXIS2-2842: Assignee: Nikhil Thaker SOAPMessageContext.getHeaders() returns null Key: AXIS2-2842 URL: https://issues.apache.org/jira/browse/AXIS2-2842 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker SOAPMessageContext.getHeaders() returns a null. While testing the Handler code I found that we get a NullPointerException as the getHeader() method on SOAPMessageContext is not implemented correctly. I will provide the implementation to return correct headers from this method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2842) SOAPMessageContext.getHeaders() returns null
SOAPMessageContext.getHeaders() returns null Key: AXIS2-2842 URL: https://issues.apache.org/jira/browse/AXIS2-2842 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker SOAPMessageContext.getHeaders() returns a null. While testing the Handler code I found that we get a NullPointerException as the getHeader() method on SOAPMessageContext is not implemented correctly. I will provide the implementation to return correct headers from this method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2842) SOAPMessageContext.getHeaders() returns null
[ https://issues.apache.org/jira/browse/AXIS2-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker resolved AXIS2-2842. -- Resolution: Fixed Revision #549938 SOAPMessageContext.getHeaders() returns null Key: AXIS2-2842 URL: https://issues.apache.org/jira/browse/AXIS2-2842 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker SOAPMessageContext.getHeaders() returns a null. While testing the Handler code I found that we get a NullPointerException as the getHeader() method on SOAPMessageContext is not implemented correctly. I will provide the implementation to return correct headers from this method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Handler interface (cleanup(), flowComplete() and errors)
Hi Glen, On Fri, 2007-06-22 at 12:52 -0400, Glen Daniels wrote: A few questions about the Handler interface based on recent conversations: 1) cleanup() never gets called. Can we remove it now that we've got flowComplete()? I had always assumed that cleanup() was the counterpart to init(), and thus would be called when a handler was deregistered thereby providing the handler with the ability to release resources that it had acquired. I'm happy to have it removed until someone actually needs that type of functionality. 2) flowComplete() seems somewhat flawed in that there is currently no way (AFAICT) to conclusively determine whether it is being called as a result of a fault/thrown exception or due to the normal termination of processing. This leaves no easy way for Handler developers to do rollbacks of any work they've done. It appears we used to have revoke(), which I think seems like the right thing (it's easier to code an explicit fault handler API than it is to remember to check for something that the compiler won't tell you about), but that was apparently replaced with flowComplete()? PROPOSAL - add a failureReason field (of type Exception) to MessageContext, and ensure that the engine ALWAYS sets this if we have to back out the processing chain due to an error. Leave flowComplete() as is, but now implementors can mc.getFailureReason() and react appropriately. +1 3) Why are we forcing every Handler to keep a pointer to it's HandlerDesc? We only call this in a couple of places (Phase), and IMHO it clutters up the interface unnecessarily. It seems like Phase should be keeping HandlerDescs, and those should be pointing to Handlers... that would more loosely and cleanly decouple the two classes. I assume that you mean removing the getHandlerDesc() method (and not removing the HandlerDescription being passed into the Handler) -- +1 if we're already modifying the Handler interface to remove the cleanup() method. Comments/thoughts? If we're only going to do (1) or (3), but not both, then perhaps we shouldn't do either unless it provides a great enough improvement to the code quality such that it's worth forcing users to modify their implementations. Thanks, --Glen - 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]
[jira] Resolved: (AXIS2-1053) ConcurrentModificationException when concurrent threads try to engage the Addressing module
[ https://issues.apache.org/jira/browse/AXIS2-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-1053. - Resolution: Fixed Fix Version/s: (was: 1.3) ConcurrentModificationException when concurrent threads try to engage the Addressing module --- Key: AXIS2-1053 URL: https://issues.apache.org/jira/browse/AXIS2-1053 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Environment: Windows XP SP2, mac OS X 10.4.7, jdk 1.5.0_06, axis2 nightly build 17/08/06 Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe Priority: Blocker Attachments: test.tar.gz Multiple sender objects are used to concurrently send (asynchronous) messages. The threads are created using a ExecutorService object and each thread creates a ServiceClient using the provided configuration, which is: ConfigurationContext configurationContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(null, null); HttpClient httpClient = new HttpClient(new MultiThreadedHttpConnectionManager()); configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE); configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, httpClient); The problem arises when the threads try to (concurrently) engage the Addressing module: Exception in thread pool-1-thread-2 java.util.ConcurrentModificationException [java] at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) [java] at java.util.AbstractList$Itr.next(AbstractList.java:420) [java] at org.apache.axis2.engine.Phase.addHandler(Phase.java:136) [java] at org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:64) [java] at org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:191) [java] at org.apache.axis2.description.AxisOperation.engageModuleToOperation(AxisOperation.java:154) [java] at org.apache.axis2.description.AxisOperation.engageModule(AxisOperation.java:128) [java] at org.apache.axis2.description.AxisService.engageModule(AxisService.java:479) [java] at org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:271) [java] at ncl.qosp.test.functional.client.Sender.run(Sender.java:134) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) [java] at java.lang.Thread.run(Thread.java:613) Please find attached a sample application (a readme file including the build instructions is probvided) to reproduce the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1053) ConcurrentModificationException when concurrent threads try to engage the Addressing module
[ https://issues.apache.org/jira/browse/AXIS2-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507503 ] Davanum Srinivas commented on AXIS2-1053: - Fixed in svn revision 549954 thanks, dims ConcurrentModificationException when concurrent threads try to engage the Addressing module --- Key: AXIS2-1053 URL: https://issues.apache.org/jira/browse/AXIS2-1053 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Environment: Windows XP SP2, mac OS X 10.4.7, jdk 1.5.0_06, axis2 nightly build 17/08/06 Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe Priority: Blocker Attachments: test.tar.gz Multiple sender objects are used to concurrently send (asynchronous) messages. The threads are created using a ExecutorService object and each thread creates a ServiceClient using the provided configuration, which is: ConfigurationContext configurationContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(null, null); HttpClient httpClient = new HttpClient(new MultiThreadedHttpConnectionManager()); configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE); configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, httpClient); The problem arises when the threads try to (concurrently) engage the Addressing module: Exception in thread pool-1-thread-2 java.util.ConcurrentModificationException [java] at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) [java] at java.util.AbstractList$Itr.next(AbstractList.java:420) [java] at org.apache.axis2.engine.Phase.addHandler(Phase.java:136) [java] at org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:64) [java] at org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:191) [java] at org.apache.axis2.description.AxisOperation.engageModuleToOperation(AxisOperation.java:154) [java] at org.apache.axis2.description.AxisOperation.engageModule(AxisOperation.java:128) [java] at org.apache.axis2.description.AxisService.engageModule(AxisService.java:479) [java] at org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:271) [java] at ncl.qosp.test.functional.client.Sender.run(Sender.java:134) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) [java] at java.lang.Thread.run(Thread.java:613) Please find attached a sample application (a readme file including the build instructions is probvided) to reproduce the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2306) wsdl2java.sh not working
[ https://issues.apache.org/jira/browse/AXIS2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2306. - Resolution: Fixed Fix Version/s: (was: 1.3) wsdl2java.sh not working Key: AXIS2-2306 URL: https://issues.apache.org/jira/browse/AXIS2-2306 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1, 1.1 Environment: Ubuntu 6.10. GNU bash, version 3.1.17(1)-release (i486-pc-linux-gnu) Reporter: Jose Antonio Assignee: Srianth Perera Priority: Blocker When trying to run wsld2java.sh for example in the following form: /opt/axis2-1.1.1/bin/wsdl2java.sh -ss -g -sn PriorService -uri ./wsdl/wsctx.wsdl -o ./PriorService I get the following: Using AXIS2_HOME: /opt/axis2-1.1.1 Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun-1.5.0.08 Invalid thread stack size: -Xss Could not create the Java virtual machine. I looked at the wsdl2java.sh file and I've found this: . `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2Java $* Instead, changing it to: `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2Java $* works for me. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2306) wsdl2java.sh not working
[ https://issues.apache.org/jira/browse/AXIS2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507512 ] Davanum Srinivas commented on AXIS2-2306: - Already fixed. i don't see a '.' in the latest wsdl2java.sh wsdl2java.sh not working Key: AXIS2-2306 URL: https://issues.apache.org/jira/browse/AXIS2-2306 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1, 1.1 Environment: Ubuntu 6.10. GNU bash, version 3.1.17(1)-release (i486-pc-linux-gnu) Reporter: Jose Antonio Assignee: Srianth Perera Priority: Blocker When trying to run wsld2java.sh for example in the following form: /opt/axis2-1.1.1/bin/wsdl2java.sh -ss -g -sn PriorService -uri ./wsdl/wsctx.wsdl -o ./PriorService I get the following: Using AXIS2_HOME: /opt/axis2-1.1.1 Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun-1.5.0.08 Invalid thread stack size: -Xss Could not create the Java virtual machine. I looked at the wsdl2java.sh file and I've found this: . `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2Java $* Instead, changing it to: `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2Java $* works for me. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1694) generate.service ant target creates an invalid service archive for pojoguidespring sample
[ https://issues.apache.org/jira/browse/AXIS2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-1694. - Resolution: Fixed Fix Version/s: (was: 1.3) generate.service ant target creates an invalid service archive for pojoguidespring sample - Key: AXIS2-1694 URL: https://issues.apache.org/jira/browse/AXIS2-1694 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: samples Affects Versions: 1.3 Environment: JDK 1.5, Win XP Reporter: Charitha Kankanamge Assignee: Sanka Samaranayake Priority: Blocker I went through instructions given in the pojoguide.html and README file located at Axis_Home/samples/pojoguidespring. However weatherServiceSpring.aar was deployed as a faulty service in both tomcat and Axis2servers. Following error was given in the logs. Invalid service WeatherSpringService.aar due to Processing Operations Modules IOException parsing XML document from class path resource [applicationContext.xml]; nested exception is java.io.FileNotFoundException: class path resource [applicationContext.xml] cannot be opened because it does not exist; This occurs when ant generate.service creates the archive, it does not add applicationContext.xml file in to the service archive. I manually added this applicationContext file to the service archive and it worked properly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1694) generate.service ant target creates an invalid service archive for pojoguidespring sample
[
https://issues.apache.org/jira/browse/AXIS2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507517
]
Davanum Srinivas commented on AXIS2-1694:
-
I can see the following line in build.xml now. Guess that does the trick.
copy file=src/applicationContext.xml
tofile=${dest.dir.classes}/applicationContext.xml overwrite=true /
thanks,
dims
generate.service ant target creates an invalid service archive for
pojoguidespring sample
-
Key: AXIS2-1694
URL: https://issues.apache.org/jira/browse/AXIS2-1694
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: samples
Affects Versions: 1.3
Environment: JDK 1.5, Win XP
Reporter: Charitha Kankanamge
Assignee: Sanka Samaranayake
Priority: Blocker
I went through instructions given in the pojoguide.html and README file
located at Axis_Home/samples/pojoguidespring. However
weatherServiceSpring.aar was deployed as a faulty service in both tomcat and
Axis2servers.
Following error was given in the logs.
Invalid service WeatherSpringService.aar due to Processing Operations
Modules IOException parsing XML document from class path resource
[applicationContext.xml]; nested exception is java.io.FileNotFoundException:
class path resource [applicationContext.xml] cannot be opened because it does
not exist;
This occurs when ant generate.service creates the archive, it does not add
applicationContext.xml file in to the service archive. I manually added this
applicationContext file to the service archive and it worked properly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2287) input line is too long error when executing the tools in Windows 2000
[ https://issues.apache.org/jira/browse/AXIS2-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2287. - Resolution: Fixed Fix Version/s: (was: 1.3) input line is too long error when executing the tools in Windows 2000 --- Key: AXIS2-2287 URL: https://issues.apache.org/jira/browse/AXIS2-2287 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.1.1 Environment: Windows 2000 Reporter: Gabriel Belingueres Assignee: Deepal Jayasinghe Priority: Blocker Hi, When trying to run the axis tools (which are .bat files) in Windows 2000, the following error is displayed: La línea escrita es demasiado larga. (in Win 2k spanish) or (in english should be) The input line is too long. This occurs because the Windows 2000 line length limit is shorter than in Win XP, and the AXIS2_CLASS_PATH content is too long. To make it work, just change the % by ! arround AXIS2_CLASS_PATH when calling the JVM: From: %_RUNJAVA% %JAVA_OPTS% -cp %AXIS2_CLASS_PATH% To: %_RUNJAVA% %JAVA_OPTS% -cp !AXIS2_CLASS_PATH! .. Regards, Gabriel -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2287) input line is too long error when executing the tools in Windows 2000
[ https://issues.apache.org/jira/browse/AXIS2-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507515 ] Davanum Srinivas commented on AXIS2-2287: - Fixed in svn revision 549961 input line is too long error when executing the tools in Windows 2000 --- Key: AXIS2-2287 URL: https://issues.apache.org/jira/browse/AXIS2-2287 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.1.1 Environment: Windows 2000 Reporter: Gabriel Belingueres Assignee: Deepal Jayasinghe Priority: Blocker Hi, When trying to run the axis tools (which are .bat files) in Windows 2000, the following error is displayed: La línea escrita es demasiado larga. (in Win 2k spanish) or (in english should be) The input line is too long. This occurs because the Windows 2000 line length limit is shorter than in Win XP, and the AXIS2_CLASS_PATH content is too long. To make it work, just change the % by ! arround AXIS2_CLASS_PATH when calling the JVM: From: %_RUNJAVA% %JAVA_OPTS% -cp %AXIS2_CLASS_PATH% To: %_RUNJAVA% %JAVA_OPTS% -cp !AXIS2_CLASS_PATH! .. Regards, Gabriel -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (AXIS2-1053) ConcurrentModificationException when concurrent threads try to engage the Addressing module
[ https://issues.apache.org/jira/browse/AXIS2-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michele Mazzucco reopened AXIS2-1053: - Dims, I'm not sure about this change. If you want to make the access to handlers thread safe you should synchronize other methods as well. Michele ConcurrentModificationException when concurrent threads try to engage the Addressing module --- Key: AXIS2-1053 URL: https://issues.apache.org/jira/browse/AXIS2-1053 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Environment: Windows XP SP2, mac OS X 10.4.7, jdk 1.5.0_06, axis2 nightly build 17/08/06 Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe Priority: Blocker Attachments: test.tar.gz Multiple sender objects are used to concurrently send (asynchronous) messages. The threads are created using a ExecutorService object and each thread creates a ServiceClient using the provided configuration, which is: ConfigurationContext configurationContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(null, null); HttpClient httpClient = new HttpClient(new MultiThreadedHttpConnectionManager()); configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE); configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, httpClient); The problem arises when the threads try to (concurrently) engage the Addressing module: Exception in thread pool-1-thread-2 java.util.ConcurrentModificationException [java] at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) [java] at java.util.AbstractList$Itr.next(AbstractList.java:420) [java] at org.apache.axis2.engine.Phase.addHandler(Phase.java:136) [java] at org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:64) [java] at org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:191) [java] at org.apache.axis2.description.AxisOperation.engageModuleToOperation(AxisOperation.java:154) [java] at org.apache.axis2.description.AxisOperation.engageModule(AxisOperation.java:128) [java] at org.apache.axis2.description.AxisService.engageModule(AxisService.java:479) [java] at org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:271) [java] at ncl.qosp.test.functional.client.Sender.run(Sender.java:134) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) [java] at java.lang.Thread.run(Thread.java:613) Please find attached a sample application (a readme file including the build instructions is probvided) to reproduce the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2595) HttpServiceProcessor needs hashCode and equals
[ https://issues.apache.org/jira/browse/AXIS2-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507529 ] Michele Mazzucco commented on AXIS2-2595: - Dims, they should be ok. The last time you changed those classes it was 09 April. Or you want me to make the proposed changes in DefaultHttpConnectionManager as well (i.e. remove the list)? Michele HttpServiceProcessor needs hashCode and equals -- Key: AXIS2-2595 URL: https://issues.apache.org/jira/browse/AXIS2-2595 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: nightly Environment: all Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe Attachments: DefaultHttpConnectionManager.patch, HttpServiceProcessor.patch In HttpServiceProcessor: - I've introduced an unique identifier to provide the equals and hashCode methods. The equals method is needed because HttpServiceProcessor instances are stored in a LinkedList in DefaultHttpConnectionManager. - The destroy method closes the connections, instead of calling shutdown In DefaultHttpConnectionManager: - I don't think it is necessary to store the processors in a linked list and use a callback when they are done to remove them from the list because the executor has a working queue where waiting jobs are put. - Instead of an Executor, I would use an ExecutorService (created in the constructor, now passed as reference), which can be stopped in the shutdown method. At present, instead, is would still possible to submit requests (i.e. by calling process()) after calling the shutdown (and what would happen?) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1053) ConcurrentModificationException when concurrent threads try to engage the Addressing module
[ https://issues.apache.org/jira/browse/AXIS2-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-1053. - Resolution: Fixed Michele, As discussed on the list, we will start synchronizing stuff only when we see a breakage scenario. (See discussion for HashMap thingy) thanks, dims ConcurrentModificationException when concurrent threads try to engage the Addressing module --- Key: AXIS2-1053 URL: https://issues.apache.org/jira/browse/AXIS2-1053 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Environment: Windows XP SP2, mac OS X 10.4.7, jdk 1.5.0_06, axis2 nightly build 17/08/06 Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe Priority: Blocker Attachments: test.tar.gz Multiple sender objects are used to concurrently send (asynchronous) messages. The threads are created using a ExecutorService object and each thread creates a ServiceClient using the provided configuration, which is: ConfigurationContext configurationContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(null, null); HttpClient httpClient = new HttpClient(new MultiThreadedHttpConnectionManager()); configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE); configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, httpClient); The problem arises when the threads try to (concurrently) engage the Addressing module: Exception in thread pool-1-thread-2 java.util.ConcurrentModificationException [java] at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) [java] at java.util.AbstractList$Itr.next(AbstractList.java:420) [java] at org.apache.axis2.engine.Phase.addHandler(Phase.java:136) [java] at org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:64) [java] at org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:191) [java] at org.apache.axis2.description.AxisOperation.engageModuleToOperation(AxisOperation.java:154) [java] at org.apache.axis2.description.AxisOperation.engageModule(AxisOperation.java:128) [java] at org.apache.axis2.description.AxisService.engageModule(AxisService.java:479) [java] at org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:271) [java] at ncl.qosp.test.functional.client.Sender.run(Sender.java:134) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) [java] at java.lang.Thread.run(Thread.java:613) Please find attached a sample application (a readme file including the build instructions is probvided) to reproduce the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2595) HttpServiceProcessor needs hashCode and equals
[ https://issues.apache.org/jira/browse/AXIS2-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2595. - Resolution: Fixed Fixed in svn revision 549993. thanks, dims HttpServiceProcessor needs hashCode and equals -- Key: AXIS2-2595 URL: https://issues.apache.org/jira/browse/AXIS2-2595 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: nightly Environment: all Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe Attachments: DefaultHttpConnectionManager.patch, HttpServiceProcessor.patch In HttpServiceProcessor: - I've introduced an unique identifier to provide the equals and hashCode methods. The equals method is needed because HttpServiceProcessor instances are stored in a LinkedList in DefaultHttpConnectionManager. - The destroy method closes the connections, instead of calling shutdown In DefaultHttpConnectionManager: - I don't think it is necessary to store the processors in a linked list and use a callback when they are done to remove them from the list because the executor has a working queue where waiting jobs are put. - Instead of an Executor, I would use an ExecutorService (created in the constructor, now passed as reference), which can be stopped in the shutdown method. At present, instead, is would still possible to submit requests (i.e. by calling process()) after calling the shutdown (and what would happen?) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1304) Enabling engage/disengage modules to AxisMessage
[ https://issues.apache.org/jira/browse/AXIS2-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507552 ] Davanum Srinivas commented on AXIS2-1304: - Glen, Is this fixed yet? thanks, dims Enabling engage/disengage modules to AxisMessage Key: AXIS2-1304 URL: https://issues.apache.org/jira/browse/AXIS2-1304 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: kernel Environment: Linux version 2.6.17-gentoo ([EMAIL PROTECTED]) (gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)) java version 1.4.2_12 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03) Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode) Reporter: Sanka Samaranayake Assignee: Deepal Jayasinghe Priority: Blocker Fix For: 1.3 In order to support policies that are attached at message levels, it is necessary to enabling module engagement/ disengagement on AxisMessage -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1575) Axis2 does not decodes SOAP responses using the character encoding set on the response's XML declaration. Problem converting from iso-8859-1 to utf-8.
[ https://issues.apache.org/jira/browse/AXIS2-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-1575. - Resolution: Fixed Fix Version/s: (was: 1.3) Axis2 does not decodes SOAP responses using the character encoding set on the response's XML declaration. Problem converting from iso-8859-1 to utf-8. -- Key: AXIS2-1575 URL: https://issues.apache.org/jira/browse/AXIS2-1575 Project: Axis 2.0 (Axis2) Issue Type: Improvement Affects Versions: 1.0 Environment: Windows XP + java 1.5 + axis2 1.0. I'm using client-side axis2 code. no server-side axis is involved. Reporter: Bruno Negrao Assignee: Deepal Jayasinghe Priority: Blocker My SOAP server (it isn't axis2 based) sends SOAP responses like this one shown at the end of this message. The soap server does not set the 'Content-type' http header as was expected so it's not possible to get the charset used in the response body from that. But the server defines the character encoding on the response's XML declaration, example: ?xml version=1.0 encoding=iso-8859-1? Axis2 is ignoring the character enconding defining on the XML declaration and is decoding all the strings sent as if they were UTF-8. The result is I cannot display the words correctly here on the client-side. The OMElement.getText() method returns crazy utf-8 characters instead of my latin characters (like á ó ç ã ê, etc). I proved that axis2 uses utf-8 to decode the network inputstream when I ran the following method on the OMElement returned as response: response.getXMLStreamReader().getCharacterEncodingScheme() It returns 'utf-8' and it should return 'iso-8859-1'. Not only it returns utf-8 but it is indeed using utf-8 to decode the inputstream, what is wrong for this situation. The improvement I'm asking here is update axis2 so it obey to the encoding definition on the response's XML declaration. thank you, bruno. AN EXAMPLE OF A SOAP RESPONSE SENT FROM MY SOAP SERVER: HTTP/1.0 200 OK Content-length: 1269 ?xml version=1.0 encoding=iso-8859-1? soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body AgendaPesquisa status0/status ListaContatosPesquisa tipoC/tipo donolucia/dono posicao177/posicao nomeAbricó Gimarães/nome email/email /ListaContatosPesquisa /AgendaPesquisa /soap:Body /soap:Envelope -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1575) Axis2 does not decodes SOAP responses using the character encoding set on the response's XML declaration. Problem converting from iso-8859-1 to utf-8.
[ https://issues.apache.org/jira/browse/AXIS2-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507551 ] Davanum Srinivas commented on AXIS2-1575: - Fixed in svn revision 549996 -- dims Axis2 does not decodes SOAP responses using the character encoding set on the response's XML declaration. Problem converting from iso-8859-1 to utf-8. -- Key: AXIS2-1575 URL: https://issues.apache.org/jira/browse/AXIS2-1575 Project: Axis 2.0 (Axis2) Issue Type: Improvement Affects Versions: 1.0 Environment: Windows XP + java 1.5 + axis2 1.0. I'm using client-side axis2 code. no server-side axis is involved. Reporter: Bruno Negrao Assignee: Deepal Jayasinghe Priority: Blocker My SOAP server (it isn't axis2 based) sends SOAP responses like this one shown at the end of this message. The soap server does not set the 'Content-type' http header as was expected so it's not possible to get the charset used in the response body from that. But the server defines the character encoding on the response's XML declaration, example: ?xml version=1.0 encoding=iso-8859-1? Axis2 is ignoring the character enconding defining on the XML declaration and is decoding all the strings sent as if they were UTF-8. The result is I cannot display the words correctly here on the client-side. The OMElement.getText() method returns crazy utf-8 characters instead of my latin characters (like á ó ç ã ê, etc). I proved that axis2 uses utf-8 to decode the network inputstream when I ran the following method on the OMElement returned as response: response.getXMLStreamReader().getCharacterEncodingScheme() It returns 'utf-8' and it should return 'iso-8859-1'. Not only it returns utf-8 but it is indeed using utf-8 to decode the inputstream, what is wrong for this situation. The improvement I'm asking here is update axis2 so it obey to the encoding definition on the response's XML declaration. thank you, bruno. AN EXAMPLE OF A SOAP RESPONSE SENT FROM MY SOAP SERVER: HTTP/1.0 200 OK Content-length: 1269 ?xml version=1.0 encoding=iso-8859-1? soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body AgendaPesquisa status0/status ListaContatosPesquisa tipoC/tipo donolucia/dono posicao177/posicao nomeAbricó Gimarães/nome email/email /ListaContatosPesquisa /AgendaPesquisa /soap:Body /soap:Envelope -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2843) Axis2 publish the WSDL converting AxisFault class to anyType
Axis2 publish the WSDL converting AxisFault class to anyType -- Key: AXIS2-2843 URL: https://issues.apache.org/jira/browse/AXIS2-2843 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: rpc Affects Versions: 1.2 Environment: Windows XP, JBoss4.0.5GA, JDK1.5.0_11, Axis2 Reporter: Lytton Cheng Use the AxisFault Class for Exception throwing. Axis2 publish the WSDL with anyType for the fault. with RPC style. We except the type is AxisFault. .NET generates the class base on WSDL, but the exception class can't be generated, because of the anyType. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
