[jira] Commented: (AXISCPP-990) missing cpp files in Distribution.sln
[ http://issues.apache.org/jira/browse/AXISCPP-990?page=comments#action_12428374 ] John Hawkins commented on AXISCPP-990: -- Really looks like you've not got the rc process in the shell path (or perhaps one of its dependents). I would test that when you run vsvars32 and then do rc from the cmd line that it works. if it doesn't then it's your vc setup that's wrong. missing cpp files in Distribution.sln - Key: AXISCPP-990 URL: http://issues.apache.org/jira/browse/AXISCPP-990 Project: Axis-C++ Issue Type: Bug Components: Build - libtools Affects Versions: 1.6 Beta Environment: MS Windows XP SP2, MS VS 2005 Reporter: Leonid Krankurs Priority: Blocker Attachments: problem.txt flies are missing in Zip files from 03-Mar-2006 axis-c-win32-current-bin.zip axis-c/source/win32/axis-c-1.6b-Win32-trace-src.zip (looks like have the same content) missing files in Distribution.sln SimpleAxisServer project: c1xx : fatal error C1083: Cannot open source file: '..\..\..\src\server\simple_axis_server\ServerHelper.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\..\..\src\common\AxisSocketUtils.cpp': No such file or directory AxisServer project: c1xx : fatal error C1083: Cannot open source file: '..\src\common\Packet.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\common\AxisException.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\common\AxisTime.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\soap\SoapParserExpat.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\wsdd\WSDDDocumentExpat.cpp': No such file or directory AxisClient project: c1xx : fatal error C1083: Cannot open source file: '..\src\common\AxisException.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\common\AxisTime.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\AxisTransport.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Channel.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\common\Packet.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Receiver.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Sender.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\soap\SoapParserExpat.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Transport.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\TransportFactory.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Url.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\wsdd\WSDDDocumentExpat.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Url.cpp': No such file or directory found in \graveyard AxisSocketUtils.cpp Channel.cpp Url.cpp (also found in src\transport\axis3) PLEASE!!! HELP!!! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXISCPP-990) missing cpp files in Distribution.sln
[ http://issues.apache.org/jira/browse/AXISCPP-990?page=comments#action_12428381 ] Leonid Krankurs commented on AXISCPP-990: - I've got to build some components, except i faced with: 1. the tpipv6.h probled and some casting stuff while compile - actually as everybody have 2 failed to build HTTPSSLChannel (it is not critical however ) - it wants OpenSSL to be installed - the Axis C++ build doc does not reference OpenSSL 3. should one expect that VC 6.0, 2kx projects of AXIS C++ get fixed - to build using native MS way? Thank you, Leonid missing cpp files in Distribution.sln - Key: AXISCPP-990 URL: http://issues.apache.org/jira/browse/AXISCPP-990 Project: Axis-C++ Issue Type: Bug Components: Build - libtools Affects Versions: 1.6 Beta Environment: MS Windows XP SP2, MS VS 2005 Reporter: Leonid Krankurs Priority: Blocker Attachments: problem.txt flies are missing in Zip files from 03-Mar-2006 axis-c-win32-current-bin.zip axis-c/source/win32/axis-c-1.6b-Win32-trace-src.zip (looks like have the same content) missing files in Distribution.sln SimpleAxisServer project: c1xx : fatal error C1083: Cannot open source file: '..\..\..\src\server\simple_axis_server\ServerHelper.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\..\..\src\common\AxisSocketUtils.cpp': No such file or directory AxisServer project: c1xx : fatal error C1083: Cannot open source file: '..\src\common\Packet.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\common\AxisException.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\common\AxisTime.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\soap\SoapParserExpat.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\wsdd\WSDDDocumentExpat.cpp': No such file or directory AxisClient project: c1xx : fatal error C1083: Cannot open source file: '..\src\common\AxisException.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\common\AxisTime.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\AxisTransport.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Channel.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\common\Packet.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Receiver.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Sender.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\soap\SoapParserExpat.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Transport.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\TransportFactory.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Url.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\wsdd\WSDDDocumentExpat.cpp': No such file or directory c1xx : fatal error C1083: Cannot open source file: '..\src\transport\axis\Url.cpp': No such file or directory found in \graveyard AxisSocketUtils.cpp Channel.cpp Url.cpp (also found in src\transport\axis3) PLEASE!!! HELP!!! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXISCPP-992) AxisIOStream vs SoapTransport ( Removing transport specific stuff from SoapSerializer and SoapDeSerializer)
AxisIOStream vs SoapTransport ( Removing transport specific stuff from SoapSerializer and SoapDeSerializer) --- Key: AXISCPP-992 URL: http://issues.apache.org/jira/browse/AXISCPP-992 Project: Axis-C++ Issue Type: Improvement Reporter: kamlesh The SoapDeSerializer and SoapSerializer api for setting the stream takes a SOAPTransport instead of AxisIOStream. For ex: int setInputStream(SOAPTransport* pInputStream); Could it be refactored to take a AxisIOStream instead ? It would be nice if the transport specific stuff is handled outside of the serializer and deserializer in a separate class. This would allow anyone to easily implement a sub-type of AxisIOStream and pass it to the serializer and deserialer( for instance I have a custom AxisIOStream based on stringstream, however I can't use it since the serializer and deserializer take a SoapTransport) Let me know if this is feasible or not ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1038) Removing an unnecessary statement
Removing an unnecessary statement - Key: AXIS2-1038 URL: http://issues.apache.org/jira/browse/AXIS2-1038 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: core Reporter: Jochen Wiedmann Priority: Trivial The patch below removes an unnecessary statement: Index: modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java === --- modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(revision 431324) +++ modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(working copy) @@ -99,7 +99,6 @@ result = (OMElement) method.invoke(obj, args); AxisService service = msgContext.getAxisService(); -service.getTargetNamespace(); result.declareNamespace(service.getTargetNamespace(), service.getTargetNamespacePrefix()); OMElement bodyContent; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1038) Removing an unnecessary statement
[ http://issues.apache.org/jira/browse/AXIS2-1038?page=comments#action_12428373 ] Davanum Srinivas commented on AXIS2-1038: - Jochen Why don't you do it yourself :) you have karma :) :) -- dims Removing an unnecessary statement - Key: AXIS2-1038 URL: http://issues.apache.org/jira/browse/AXIS2-1038 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: core Reporter: Jochen Wiedmann Priority: Trivial The patch below removes an unnecessary statement: Index: modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java === --- modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(revision 431324) +++ modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(working copy) @@ -99,7 +99,6 @@ result = (OMElement) method.invoke(obj, args); AxisService service = msgContext.getAxisService(); -service.getTargetNamespace(); result.declareNamespace(service.getTargetNamespace(), service.getTargetNamespacePrefix()); OMElement bodyContent; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1038) Removing an unnecessary statement
[ http://issues.apache.org/jira/browse/AXIS2-1038?page=comments#action_12428375 ] Jochen Wiedmann commented on AXIS2-1038: Dims, I might have the necessary permissions in terms of SVN and Unix. Nevertheless, I am no voted member of the Axis2 project and I would personally consider it to be abusing my privileges. Removing an unnecessary statement - Key: AXIS2-1038 URL: http://issues.apache.org/jira/browse/AXIS2-1038 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: core Reporter: Jochen Wiedmann Priority: Trivial The patch below removes an unnecessary statement: Index: modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java === --- modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(revision 431324) +++ modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(working copy) @@ -99,7 +99,6 @@ result = (OMElement) method.invoke(obj, args); AxisService service = msgContext.getAxisService(); -service.getTargetNamespace(); result.declareNamespace(service.getTargetNamespace(), service.getTargetNamespacePrefix()); OMElement bodyContent; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1039) Operation- and EnpointInterface- Description metdata improvements
Operation- and EnpointInterface- Description metdata improvements - Key: AXIS2-1039 URL: http://issues.apache.org/jira/browse/AXIS2-1039 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Jeff Barrett Improvements to the metadata processing including - Package protect methods accessing the annotations directly - Provide defaults (per JAX-WS spec) for annotations - Provide getters for metadata associated with JAX-WS annotations Also provide additional tests and refactoring of ProxyDescriptor based on the above. I have a patch I will submit shortly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-184) Returning a large number of items throws a StackOverFlowError
[ http://issues.apache.org/jira/browse/AXIS2-184?page=comments#action_12428422 ] Ben McKenzie commented on AXIS2-184: I noticed that Axis2 1.0 has been released, but this issue is not fixed. This is preventing me from being able to use it, as I need to be able to pull large data sets. Returning a large number of items throws a StackOverFlowError - Key: AXIS2-184 URL: http://issues.apache.org/jira/browse/AXIS2-184 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: om Affects Versions: 0.91 Environment: tomcat5, gentoo linux, java 1.5.0_04, kernel 2.6.11-gentoo-r5 Reporter: Ben McKenzie Assigned To: Davanum Srinivas Attachments: DataServiceSkeleton.java, DLDataService.wsdl, newoutput.log When returning a large number of items from a SOAP (40,000) using several arrays, I get a java.lang.StackOverflowError I will attach the entire stack trace, as it is very long. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-184) Returning a large number of items throws a StackOverFlowError
[ http://issues.apache.org/jira/browse/AXIS2-184?page=comments#action_12428423 ] Ben McKenzie commented on AXIS2-184: Is there an alternate method for runnign with large data sets? I would think that other users would be hitting this same problem. Returning a large number of items throws a StackOverFlowError - Key: AXIS2-184 URL: http://issues.apache.org/jira/browse/AXIS2-184 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: om Affects Versions: 0.91 Environment: tomcat5, gentoo linux, java 1.5.0_04, kernel 2.6.11-gentoo-r5 Reporter: Ben McKenzie Assigned To: Davanum Srinivas Attachments: DataServiceSkeleton.java, DLDataService.wsdl, newoutput.log When returning a large number of items from a SOAP (40,000) using several arrays, I get a java.lang.StackOverflowError I will attach the entire stack trace, as it is very long. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-184) Returning a large number of items throws a StackOverFlowError
[ http://issues.apache.org/jira/browse/AXIS2-184?page=comments#action_12428424 ] Davanum Srinivas commented on AXIS2-184: Ben, I'd recommend trying the nightly build with ADB (not XMLBeans). -- dims Returning a large number of items throws a StackOverFlowError - Key: AXIS2-184 URL: http://issues.apache.org/jira/browse/AXIS2-184 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: om Affects Versions: 0.91 Environment: tomcat5, gentoo linux, java 1.5.0_04, kernel 2.6.11-gentoo-r5 Reporter: Ben McKenzie Assigned To: Davanum Srinivas Attachments: DataServiceSkeleton.java, DLDataService.wsdl, newoutput.log When returning a large number of items from a SOAP (40,000) using several arrays, I get a java.lang.StackOverflowError I will attach the entire stack trace, as it is very long. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-1034) JAXWS: First pass at server side Java bean dispatcher.
[ http://issues.apache.org/jira/browse/AXIS2-1034?page=all ] Nick Gallardo closed AXIS2-1034. Resolution: Fixed Fixed. JAXWS: First pass at server side Java bean dispatcher. -- Key: AXIS2-1034 URL: http://issues.apache.org/jira/browse/AXIS2-1034 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Attachments: 1034-patch.txt I'm working on a first pass of the code that will be used to dispatch requests to server side Java bean endpoints. For this first iteration, only endpoints that are based on Doc/Lit Wrapped WSDLs will be supported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-1034) JAXWS: First pass at server side Java bean dispatcher.
[ http://issues.apache.org/jira/browse/AXIS2-1034?page=all ] Nick Gallardo reassigned AXIS2-1034: Assignee: Nick Gallardo JAXWS: First pass at server side Java bean dispatcher. -- Key: AXIS2-1034 URL: http://issues.apache.org/jira/browse/AXIS2-1034 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Attachments: 1034-patch.txt I'm working on a first pass of the code that will be used to dispatch requests to server side Java bean endpoints. For this first iteration, only endpoints that are based on Doc/Lit Wrapped WSDLs will be supported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1039) Operation- and EnpointInterface- Description metdata improvements
[ http://issues.apache.org/jira/browse/AXIS2-1039?page=all ] Jeff Barrett updated AXIS2-1039: Attachment: patch.txt Changes as described in Description. Operation- and EnpointInterface- Description metdata improvements - Key: AXIS2-1039 URL: http://issues.apache.org/jira/browse/AXIS2-1039 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Jeff Barrett Attachments: patch.txt Improvements to the metadata processing including - Package protect methods accessing the annotations directly - Provide defaults (per JAX-WS spec) for annotations - Provide getters for metadata associated with JAX-WS annotations Also provide additional tests and refactoring of ProxyDescriptor based on the above. I have a patch I will submit shortly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-965) Need a way to build AxisServices for all ports/services in a wsld.
[ http://issues.apache.org/jira/browse/AXIS2-965?page=all ] Lori VanGulick updated AXIS2-965: - Attachment: revised-JIRA965patch.txt I have updated this patch to the new kernel module. I have verified that the tests still pass. Need a way to build AxisServices for all ports/services in a wsld. -- Key: AXIS2-965 URL: http://issues.apache.org/jira/browse/AXIS2-965 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: core Reporter: Lori VanGulick Attachments: AXIS2-965patch.txt, revised-JIRA965patch.txt WSDL 11 allows multiple services per wsdl file, and multiple ports per service. Currently unless a service and port name are specified, WSDL11ToAxisServiceBuilder will only return the first port on the first service. I would like to provide an extension to WSDL11ToAxisServiceBuilder that would take a wsdl file and return a List of AxisService objects, one for each port in the wsdl. To make this more efficient I will need to make some minor changes to org.apache.axis2.description.WSDL11ToAxisServiceBuilder.java, i.e. - restructuring in the populateService method so that all the processing that is not specific to an AxisService is only done one time. Move this code to a new method, setup(). Setup code will include reading in the wsdl file, processing policies, imports, etc. - make some methods and fields protected instead of private so they can be accessed by subclasses. The new extension is proposed to be org.appache.axis2.description.WSDL11ToAllAxisServicesBuilder. It has a public method, popluateAllServices() which operates as follows - calls the setup() method on the parent. - iterates through all the services and all the ports in the wsdl, setting serviceName and portName on the parent. - calls up to populateService() on the parent. This will return an AxisService specific to the service and port name specified. - changes the name on the AxisService to the port name instead of the service name, so it can be uniquely identified. - returns the List of AxisService objects, one for each port in the wsdl I will also make corresponding changes for WSDL 2.0 in org.apache.axis2.description.WSDL20ToAxisServiceBuilder.java and create WSDL20ToAllAxisServicesBuilder.java. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Time to have next release
Dims, Great stuff - thanks for that. I'll pass this on to woden-dev and keep my eyes peeled for any updates. Kind Regards, Graham. _ Graham C Turrell CEng, MBCS Chartered IT Practitioner WebSphere ESB Foundation Technologies DE3F16 / MP 211 IBM Labs Hursley Park Winchester, Hampshire England. SO21 2JN Tel +44-(0)1962-815018 email: [EMAIL PROTECTED] No army can withstand the force of an idea whose time has come.. -Victor Hugo Davanum Srinivas [EMAIL PROTECTED] wrote on 15/08/2006 18:50:39: Graham, I am ploughing thru the JIRA and looking at dependencies. I want to come up with a list of JIRA items in the next couple of days that we can debate on. we may need 3-4 weeks as we also need to push thru the releases of all the dependent projects. thanks, -- dims On 8/15/06, Graham Turrell [EMAIL PROTECTED] wrote: Hi List, I realise Apachecon Asia is still underway, but I'm wondering if there have been further thoughts this week on a ballpark/finger-in-the-air timeframe for a 1.1 release? The reason for asking is really to assist our own medium-term planning in the woden-dev camp, and of course we'll be keeping a lurking eye on the list as your plans firm up:) Thanks, Graham. On 8/8/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi All; After Axis2 1.0 release we have done a number of feature improvements and bug fixing , so I think its time to think about the next release. And of course there were many request for a release in the mailing list too. I think we can do a release after ApacheCon Asia ( I am bit busy with apacheCon) , with the above improvements + bug fixes . I update the wiki (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.1 ) , and need to identify the JIRAs we need to fix before next release too :). Please be kind enough to make your suggestions on this release. Here is my +1 for the next release Axis2 1.1, Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2][VOTE] handling WSDL's multiple services/ports (JIRA-965)
Vote: Accept the changes for JIRA-965 as an interim solution. Hi, I have submitted a patch for JIRA-965 which contains an extension to WSDL11ToAxisServiceBuilder which will retrieve all the ports on all the services in the WSDL and return them as a List of AxisService objects. Only users of the new extension would see the new behavior. Existing users of WSDL11ToAxisServiceBuilder will not be affected. I have verified that all the tests still pass with the patch. The patch also contains cooresponding changes for WSDL20ToAxisServiceBuilder, and a new test for the new extensions. Concerns have been expressed here on the mailing list that this is not the correct solution to the problem. A more correct solution would be to add an axisEndpoint object. The details of this change have yet to be worked out, but it seems clear to me that this will be a significant change which we would not want to undertake at this point given that we are trying to stabilize Axis2 for a 1.1 release. I need this functionality as soon as possible, so I would like to be able to commit my change as an interim solution. Once Axis2 1.1 is complete I would like to revisit the topic of adding axisEndpoint and work out all the details at that point. Thanks, Lori. Lori Van Gulick WebSphere Development IBM Austin (512) 838-7929
Re: [Axis2][VOTE] handling WSDL's multiple services/ports (JIRA-965)
+1 from me. On 8/16/06, Lori Van Gulick [EMAIL PROTECTED] wrote: Vote: Accept the changes for JIRA-965 as an interim solution. Hi, I have submitted a patch for JIRA-965 which contains an extension to WSDL11ToAxisServiceBuilder which will retrieve all the ports on all the services in the WSDL and return them as a List of AxisService objects. Only users of the new extension would see the new behavior. Existing users of WSDL11ToAxisServiceBuilder will not be affected. I have verified that all the tests still pass with the patch. The patch also contains cooresponding changes for WSDL20ToAxisServiceBuilder, and a new test for the new extensions. Concerns have been expressed here on the mailing list that this is not the correct solution to the problem. A more correct solution would be to add an axisEndpoint object. The details of this change have yet to be worked out, but it seems clear to me that this will be a significant change which we would not want to undertake at this point given that we are trying to stabilize Axis2 for a 1.1 release. I need this functionality as soon as possible, so I would like to be able to commit my change as an interim solution. Once Axis2 1.1 is complete I would like to revisit the topic of adding axisEndpoint and work out all the details at that point. Thanks, Lori. Lori Van Gulick WebSphere Development IBM Austin (512) 838-7929 -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2][VOTE] handling WSDL's multiple services/ports (JIRA-965)
Don't really need a vote on this. i'll check it in right now. thanks, dims On 8/16/06, Davanum Srinivas [EMAIL PROTECTED] wrote: +1 from me. On 8/16/06, Lori Van Gulick [EMAIL PROTECTED] wrote: Vote: Accept the changes for JIRA-965 as an interim solution. Hi, I have submitted a patch for JIRA-965 which contains an extension to WSDL11ToAxisServiceBuilder which will retrieve all the ports on all the services in the WSDL and return them as a List of AxisService objects. Only users of the new extension would see the new behavior. Existing users of WSDL11ToAxisServiceBuilder will not be affected. I have verified that all the tests still pass with the patch. The patch also contains cooresponding changes for WSDL20ToAxisServiceBuilder, and a new test for the new extensions. Concerns have been expressed here on the mailing list that this is not the correct solution to the problem. A more correct solution would be to add an axisEndpoint object. The details of this change have yet to be worked out, but it seems clear to me that this will be a significant change which we would not want to undertake at this point given that we are trying to stabilize Axis2 for a 1.1 release. I need this functionality as soon as possible, so I would like to be able to commit my change as an interim solution. Once Axis2 1.1 is complete I would like to revisit the topic of adding axisEndpoint and work out all the details at that point. Thanks, Lori. Lori Van Gulick WebSphere Development IBM Austin (512) 838-7929 -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-965) Need a way to build AxisServices for all ports/services in a wsld.
[ http://issues.apache.org/jira/browse/AXIS2-965?page=all ] Davanum Srinivas resolved AXIS2-965. Resolution: Fixed Applied. thanks, dims Need a way to build AxisServices for all ports/services in a wsld. -- Key: AXIS2-965 URL: http://issues.apache.org/jira/browse/AXIS2-965 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: core Reporter: Lori VanGulick Attachments: AXIS2-965patch.txt, revised-JIRA965patch.txt WSDL 11 allows multiple services per wsdl file, and multiple ports per service. Currently unless a service and port name are specified, WSDL11ToAxisServiceBuilder will only return the first port on the first service. I would like to provide an extension to WSDL11ToAxisServiceBuilder that would take a wsdl file and return a List of AxisService objects, one for each port in the wsdl. To make this more efficient I will need to make some minor changes to org.apache.axis2.description.WSDL11ToAxisServiceBuilder.java, i.e. - restructuring in the populateService method so that all the processing that is not specific to an AxisService is only done one time. Move this code to a new method, setup(). Setup code will include reading in the wsdl file, processing policies, imports, etc. - make some methods and fields protected instead of private so they can be accessed by subclasses. The new extension is proposed to be org.appache.axis2.description.WSDL11ToAllAxisServicesBuilder. It has a public method, popluateAllServices() which operates as follows - calls the setup() method on the parent. - iterates through all the services and all the ports in the wsdl, setting serviceName and portName on the parent. - calls up to populateService() on the parent. This will return an AxisService specific to the service and port name specified. - changes the name on the AxisService to the port name instead of the service name, so it can be uniquely identified. - returns the List of AxisService objects, one for each port in the wsdl I will also make corresponding changes for WSDL 2.0 in org.apache.axis2.description.WSDL20ToAxisServiceBuilder.java and create WSDL20ToAllAxisServicesBuilder.java. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2][VOTE] handling WSDL's multiple services/ports (JIRA-965)
Hi, Are we talking about generating code for multiple services/ports at the same time ? we could have modified the codegen to run across the diffrent ports/services in seperate passes! Ajith On 8/16/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Don't really need a vote on this. i'll check it in right now. thanks, dims On 8/16/06, Davanum Srinivas [EMAIL PROTECTED] wrote: +1 from me. On 8/16/06, Lori Van Gulick [EMAIL PROTECTED] wrote: Vote: Accept the changes for JIRA-965 as an interim solution. Hi, I have submitted a patch for JIRA-965 which contains an extension to WSDL11ToAxisServiceBuilder which will retrieve all the ports on all the services in the WSDL and return them as a List of AxisService objects. Only users of the new extension would see the new behavior. Existing users of WSDL11ToAxisServiceBuilder will not be affected. I have verified that all the tests still pass with the patch. The patch also contains cooresponding changes for WSDL20ToAxisServiceBuilder, and a new test for the new extensions. Concerns have been expressed here on the mailing list that this is not the correct solution to the problem. A more correct solution would be to add an axisEndpoint object. The details of this change have yet to be worked out, but it seems clear to me that this will be a significant change which we would not want to undertake at this point given that we are trying to stabilize Axis2 for a 1.1 release. I need this functionality as soon as possible, so I would like to be able to commit my change as an interim solution. Once Axis2 1.1 is complete I would like to revisit the topic of adding axisEndpoint and work out all the details at that point. Thanks, Lori. Lori Van Gulick WebSphere Development IBM Austin (512) 838-7929 -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-1039) Operation- and EnpointInterface- Description metdata improvements
[ http://issues.apache.org/jira/browse/AXIS2-1039?page=all ] Nick Gallardo reassigned AXIS2-1039: Assignee: Nick Gallardo Operation- and EnpointInterface- Description metdata improvements - Key: AXIS2-1039 URL: http://issues.apache.org/jira/browse/AXIS2-1039 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Jeff Barrett Assigned To: Nick Gallardo Attachments: patch.txt Improvements to the metadata processing including - Package protect methods accessing the annotations directly - Provide defaults (per JAX-WS spec) for annotations - Provide getters for metadata associated with JAX-WS annotations Also provide additional tests and refactoring of ProxyDescriptor based on the above. I have a patch I will submit shortly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS-2541) Deserializing dates in attributes
Deserializing dates in attributes
-
Key: AXIS-2541
URL: http://issues.apache.org/jira/browse/AXIS-2541
Project: Apache Axis
Issue Type: Bug
Affects Versions: 1.2.1, 1.4
Environment: JDK1.5, Windows, Axis 1.2.1 and 1.4
Reporter: Michael Becke
Dates are not correctly deserialized when used as in the following WSDL:
?xml version=1.0?
definitions name=TestDates
xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
targetNamespace=http://ws.apache.org/test;
xmlns:tns=http://ws.apache.org/test;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
types
xs:schema
targetNamespace=http://ws.apache.org/test;
xmlns:tns=http://ws.apache.org/test;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
elementFormDefault=qualified
xs:element name=DateRequest
xs:complexType
xs:all
xs:element name=DateValue
type=tns:DateValueType minOccurs=1 maxOccurs=1 /
/xs:all
/xs:complexType
/xs:element
xs:complexType name=DateValueType
xs:attribute name=date type=xs:date /
xs:attribute name=value type=xs:decimal /
/xs:complexType
xs:element name=DateResponse
xs:complexType
xs:all
xs:element name=Date type=xs:date
minOccurs=1 maxOccurs=1 /
/xs:all
/xs:complexType
/xs:element
/xs:schema
/types
message name=TestRequestMsg
part name=body element=tns:DateRequest/
/message
message name=TestResponseMsg
part name=body element=tns:DateResponse/
/message
portType name=TestPortType
operation name=TestDates
input message=tns:TestRequestMsg/
output message=tns:TestResponseMsg/
/operation
/portType
binding name=TestSoapBinding type=tns:TestPortType
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
operation name=TestDates
soap:operation soapAction=http://ws.apache.org/
input
soap:body use=literal/
/input
output
soap:body use=literal/
/output
/operation
/binding
service name=TestService
documentation/documentation
port name=TestService binding=tns:TestSoapBinding
soap:address location=http://localhost/axis/ws/TestService/
/port
/service
/definitions
I am using WSDL2Java to gerate the client/server for this service. Once
generated and installed, calling the service produces the following exception:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.NumberFormatException: For input string:
quot;2006-08-16quot;
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:mbecke
java.lang.NumberFormatException: For input string: 2006-08-16
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
[jira] Commented: (AXIS-2540) Multiple threads can modify targetURL in HTTPSender
[ http://issues.apache.org/jira/browse/AXIS-2540?page=comments#action_12428543 ] Muruga Chinnananchi commented on AXIS-2540: --- This fix applies to all the previous 1.x releases also. Multiple threads can modify targetURL in HTTPSender --- Key: AXIS-2540 URL: http://issues.apache.org/jira/browse/AXIS-2540 Project: Apache Axis Issue Type: Bug Components: Basic Architecture Affects Versions: 1.4 Environment: all platforms Reporter: Muruga Chinnananchi Priority: Critical Attachments: HTTPSender.java the targetURL in HTTPSender is shared by multiple threads, in a highly concurrent and multi-threaded environment, and multiple threads modifies the targetURL and the messages endup going to wrong endpoint. Our customers experienced this problem in production environment and we created a simple test case to reproduce this, just place Thread.sleep(1000) right before calling writeToSocket ( ) and try to send messages from multiple threads to different endpoints. you would notice the messages going to wrong endpoints. Fix: Remove the targetURL instance variable in HTTPSender.java and make it local to the public void invoke(MessageContext msgContext) throws AxisFault method. I am attaching the fixed HTTPSender.java. I fixed it on top of 1.4 release source. I thought it would benefit others who uses wsif-axis in multi-threaded environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1040) Basic Authentication lock up
Basic Authentication lock up
Key: AXIS2-1040
URL: http://issues.apache.org/jira/browse/AXIS2-1040
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.0
Environment: Windows 2003 with Sharepoint Portal Server, configured to
use IIS basic authentication.
Reporter: jeff ling
First, I can use browser (Firefox) connect and login to the site, so
authentication on the server side doesn't have issue.
But when I use Axis to do the same, I got into an infinite loop. The following
messages are repeated over and over:
[EMAIL PROTECTED]:37:39 DEBUG [main] (StAXUtils.java:126) - XMLStreamWriter is
com.ctc.wstx.sw.SimpleNsStreamWriter
[EMAIL PROTECTED]:37:39 DEBUG [main] (OMSourcedElementImpl.java:520) -
serialize
{http://microsoft.com/webservices/SharePointPortalServer/UserProfileService}GetUserProfileByIndex
to XMLStreamWriter
[EMAIL PROTECTED]:37:39 DEBUG [main] (EntityEnclosingMethod.java:504) - Request
body sent
[EMAIL PROTECTED]:37:39 DEBUG [main] (HttpMethodDirector.java:837) -
Authorization required
[EMAIL PROTECTED]:37:39 DEBUG [main] (AuthChallengeProcessor.java:89) -
Supported authentication schemes in the order of preference: [ntlm, digest,
basic]
[EMAIL PROTECTED]:37:39 DEBUG [main] (AuthChallengeProcessor.java:110) -
Challenge for ntlm authentication scheme not available
[EMAIL PROTECTED]:37:39 DEBUG [main] (AuthChallengeProcessor.java:110) -
Challenge for digest authentication scheme not available
[EMAIL PROTECTED]:37:39 INFO [main] (AuthChallengeProcessor.java:100) - basic
authentication scheme selected
[EMAIL PROTECTED]:37:39 DEBUG [main] (AuthChallengeProcessor.java:154) - Using
authentication scheme: basic
[EMAIL PROTECTED]:37:39 DEBUG [main] (AuthChallengeProcessor.java:162) -
Authorization challenge processed
[EMAIL PROTECTED]:37:39 DEBUG [main] (HttpMethodDirector.java:706) -
Authentication scope: BASIC 'soto.corp.google.com'@soto.corp.google.com:2003
[EMAIL PROTECTED]:37:39 DEBUG [main] (HttpMethodDirector.java:855) -
Credentials required
[EMAIL PROTECTED]:37:39 DEBUG [main] (HttpMethodDirector.java:869) - BASIC
'soto.corp.google.com'@soto.corp.google.com:2003 new credentials given
[EMAIL PROTECTED]:37:40 DEBUG [main] (HttpMethodDirector.java:193) - Retry
authentication
[EMAIL PROTECTED]:37:40 DEBUG [main] (HttpMethodBase.java:921) - Resorting to
protocol version default close connection policy
[EMAIL PROTECTED]:37:40 DEBUG [main] (HttpMethodBase.java:925) - Should NOT
close connection, using HTTP/1.1
[EMAIL PROTECTED]:37:40 DEBUG [main] (HttpConnection.java:1175) - Connection is
locked. Call to releaseConnection() ignored.
[EMAIL PROTECTED]:37:40 DEBUG [main] (HttpMethodDirector.java:277) -
Authenticating with BASIC 'soto.corp.google.com'@soto.corp.google.com:2003
[EMAIL PROTECTED]:37:40 DEBUG [main] (HttpMethodParams.java:355) - Credential
charset not configured, using HTTP element charset
[EMAIL PROTECTED]:37:40 DEBUG [main] (HttpMethodBase.java:1235) - Adding Host
request header
The same client works when connecting to another web site with basic
authentication. So I am not sure what was the cause here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
