[Axis2]Renewing Guththila

Hi devs, Hope to do following modifications to guththila code in order to minimize memory leaks and enhance the performance of guththila xml parser.guththila_reader 1.Replace guththila_environment, guththila_allocator, guththila_error with axis2_environment,

[jira] Closed: (AXIS2C-9) No method to get the charset encoding in xml document when using thr Guththila parser

[ http://issues.apache.org/jira/browse/AXIS2C-9?page=all ] Dinesh Premalal closed AXIS2C-9. Fix Version/s: Current (Nightly) Resolution: Fixed added method to get encoding version No method to get the charset encoding in xml document when using

[jira] Closed: (AXIS2C-43) Buffer growth not working in guththila

[ http://issues.apache.org/jira/browse/AXIS2C-43?page=all ] Dinesh Premalal closed AXIS2C-43. - Fix Version/s: Current (Nightly) Resolution: Fixed Buffer growth not working in guththila --

[jira] Created: (AXISCPP-987) wsdl parameter ordering not preserved

wsdl parameter ordering not preserved - Key: AXISCPP-987 URL: http://issues.apache.org/jira/browse/AXISCPP-987 Project: Axis-C++ Issue Type: Bug Components: WSDD Processing Reporter:

[jira] Closed: (AXIS2C-214) axis2_env_create_all function segfaults when log creation fails

[ http://issues.apache.org/jira/browse/AXIS2C-214?page=all ] Nandika Jayawardana closed AXIS2C-214. -- Resolution: Fixed Assignee: Nandika Jayawardana This issue is fixed now axis2_env_create_all function segfaults when log creation fails

[jira] Created: (AXIS2C-215) When sandesha2 is added as a global module to axis2.xml client seg faults

When sandesha2 is added as a global module to axis2.xml client seg faults - Key: AXIS2C-215 URL: http://issues.apache.org/jira/browse/AXIS2C-215 Project: Axis2-C Issue

[jira] Commented: (AXISCPP-986) ANT Build failed

[ http://issues.apache.org/jira/browse/AXISCPP-986?page=comments#action_12423307 ] Manfred Pauli commented on AXISCPP-986: --- I tried to compile with C++ 6.0 but it didn't work, so I started another try with Ant and VC++ 8.0 Compiler. Now

Re: [Axis2]Renewing Guththila

Dinesh Premalal wrote: Hi devs, Hope to do following modifications to guththila code in order to minimize memory leaks and enhance the performance of guththila xml parser. Good to hear this. We need guththila up and running very badly IMHO. guththila_reader

[jira] Commented: (AXISCPP-986) ANT Build failed

[ http://issues.apache.org/jira/browse/AXISCPP-986?page=comments#action_12423312 ] Manfred Pauli commented on AXISCPP-986: --- Now I tried to run the ANT tool with the source, that can be downloaded (not svn) and I get a lot of java errors.

[jira] Updated: (AXISCPP-986) ANT Build failed

[ http://issues.apache.org/jira/browse/AXISCPP-986?page=all ] Manfred Pauli updated AXISCPP-986: -- Attachment: log1.txt ANT Build failed Key: AXISCPP-986 URL:

[jira] Commented: (AXISCPP-986) ANT Build failed

[ http://issues.apache.org/jira/browse/AXISCPP-986?page=comments#action_12423326 ] Adrian Dick commented on AXISCPP-986: - Hi, It really isn't clear to me how you're trying to compile the code, but there seem to be a lot of

Re: [jira] Commented: (AXISCPP-986) ANT Build failed

To me the latest Java errors simply say, that the compiler exes (especially the resource compiler rc) are not found. Greetings Franz Adrian Dick (JIRA) schrieb: [ http://issues.apache.org/jira/browse/AXISCPP-986?page=comments#action_12423326 ] Adrian Dick commented on

[jira] Commented: (AXISCPP-978) deserializing of arrays of complex types with optional elements broken

[ http://issues.apache.org/jira/browse/AXISCPP-978?page=comments#action_12423494 ] nadir amra commented on AXISCPP-978: I am looking at this issue, and I see there are three total occurrences (including what Franz mentions above) in the

Re: [Axis2] diclient or dyclient

Hi, Samisa Abeysinghe wrote: We have the dynamic client sample in diclient folder. Shall I rename this to dyclient, or better yet dynamic_client as this is a sample and we better be clear with names. I have renamed this to dynamic_client thanks Damitha Thanks, Samisa...

[Axis2] Moving listener_manager.h to the global include

Hi All, The listener_manager which is implemented in core/clientapi is required by the sandesha2 module. At the moment the header file is named as listener_manager.h and is located inside core/clientapi. So the functionality is not visible to the module writers. Can we move this header to global

[jira] Commented: (AXIS2-922) WSDL2Java generates incorrect code for multiple faults

[ http://issues.apache.org/jira/browse/AXIS2-922?page=comments#action_12423243 ] Ajith Harshana Ranabahu commented on AXIS2-922: --- Your WSDL file does not contain the bindings for the faults. Put this section in the binding and see

[jira] Created: (AXIS2-929) need to Update the Axiom tutorial to reflect Axiom-1.0.jar (need to made the examples compile , need to fix the namespace samples)

need to Update the Axiom tutorial to reflect Axiom-1.0.jar (need to made the examples compile , need to fix the namespace samples) --- Key: AXIS2-929

[jira] Commented: (AXIS2-929) need to Update the Axiom tutorial to reflect Axiom-1.0.jar (need to made the examples compile , need to fix the namespace samples)

[ http://issues.apache.org/jira/browse/AXIS2-929?page=comments#action_12423296 ] Eran Chinthaka commented on AXIS2-929: -- Can you please create a diff and attach here? Its much easy to review a diff than the complete file. need to Update

[jira] Resolved: (AXIS2-736) [ADB] Feedback from Wendy's POC

[ http://issues.apache.org/jira/browse/AXIS2-736?page=all ] Ajith Harshana Ranabahu resolved AXIS2-736. --- Resolution: Fixed The only valid problem in this is #1 I've changed the template to generate the method signature in proper camel case

[jira] Updated: (AXIS2-929) need to Update the Axiom tutorial to reflect Axiom-1.0.jar (need to made the examples compile , need to fix the namespace samples)

[ http://issues.apache.org/jira/browse/AXIS2-929?page=all ] Lahiru Sandakith updated AXIS2-929: --- Attachment: axiom_1_0_tute_patch attaching the diff of the modifications to the OMTutorial.html as the patch Thanks need to Update the Axiom tutorial

Why Axis XML signature verification problem is not completely solved by enableNamespacePrefixOptimization parameter

Hi all, i first encountered the XML signature verification problem generated by the serialization mechanism of Axis 1.x when starting to use wss4j SAML support based on OpenSAML 1.0.1. To create an SAML assertion uses org.opensaml.SAMLAssertion that creates assertions this way: Assertion

[jira] Commented: (AXIS2-788) Outbound MAP EPRs overwritten with values from the response message

[ http://issues.apache.org/jira/browse/AXIS2-788?page=comments#action_12423313 ] Deepal Jayasinghe commented on AXIS2-788: - I checked it , as I can see the issue is fixed now can you please check and confirm Outbound MAP EPRs

[jira] Updated: (AXIS2-929) need to Update the Axiom tutorial to reflect Axiom-1.0.jar (need to made the examples compile , need to fix the namespace samples)

[ http://issues.apache.org/jira/browse/AXIS2-929?page=all ] Lahiru Sandakith updated AXIS2-929: --- Attachment: OMTutorial_html_patch_new this is the new one pls ignore the previous one need to Update the Axiom tutorial to reflect Axiom-1.0.jar (need

[jira] Created: (AXIS2-930) JAXWS: NPE in XMLSpineImpl when no header block exists

JAXWS: NPE in XMLSpineImpl when no header block exists -- Key: AXIS2-930 URL: http://issues.apache.org/jira/browse/AXIS2-930 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug

[jira] Assigned: (AXIS2-910) JAXWS: Update AxisInvocationController to use the OperationClient instead of the ServiceClient

[ http://issues.apache.org/jira/browse/AXIS2-910?page=all ] Bill Nagy reassigned AXIS2-910: --- Assignee: Bill Nagy (was: Rich Scheuerle) JAXWS: Update AxisInvocationController to use the OperationClient instead of the ServiceClient

[jira] Updated: (AXIS2-930) JAXWS: NPE in XMLSpineImpl when no header block exists

[ http://issues.apache.org/jira/browse/AXIS2-930?page=all ] Nick Gallardo updated AXIS2-930: Attachment: test-patch.txt Added a new test to the MessageTests (testStringOutflow3) that tests for this condition. JAXWS: NPE in XMLSpineImpl when no header

[jira] Updated: (AXIS2-930) JAXWS: NPE in XMLSpineImpl when no header block exists

[ http://issues.apache.org/jira/browse/AXIS2-930?page=all ] Nick Gallardo updated AXIS2-930: Attachment: src-patch.txt Added the check for the null. JAXWS: NPE in XMLSpineImpl when no header block exists

[jira] Commented: (AXIS2-922) WSDL2Java generates incorrect code for multiple faults

[ http://issues.apache.org/jira/browse/AXIS2-922?page=comments#action_12423337 ] Dave Cowing commented on AXIS2-922: --- I updated the wsdl as you suggested and still observed the same behavior. Only one fault sub-class generated in Skeleton +

[jira] Updated: (AXIS2-922) WSDL2Java generates incorrect code for multiple faults

[ http://issues.apache.org/jira/browse/AXIS2-922?page=all ] Dave Cowing updated AXIS2-922: -- Attachment: Services.wsdl updated wsdl with faults in binding WSDL2Java generates incorrect code for multiple faults

[Axis2] REMINDER : Axis IRC chat TOMORROW

Hi folks! This is an automatic reminder that the weekly Axis2 developer chat will be occurring tomorrow, July 26, at: 5AM SF, 8AM Boston, 1PM London, 5:30PM Colombo, 10PM Melbourne The chat takes place on the freenode IRC network, (use server irc.freenode.net), on channel #apache-axis, and is

Re: [Axis2] REMINDER : Axis IRC chat TOMORROW

robert lazarski wrote: The last few weeks this didn't happen. Time to pull the plug? OK I'm gonna shut off the reminder for now in favor of ad-hoc mails if/when IRC chats are called for. If anyone would like it reinstated, let's discuss. --Glen

[jira] Created: (AXIS2-931) WSDL2Java generated fault exceptions don't provide a way to specify an exception message or cause.

WSDL2Java generated fault exceptions don't provide a way to specify an exception message or cause. -- Key: AXIS2-931 URL:

[jira] Commented: (AXIS2-931) WSDL2Java generated fault exceptions don't provide a way to specify an exception message or cause.

[ http://issues.apache.org/jira/browse/AXIS2-931?page=comments#action_12423432 ] Derek Foster commented on AXIS2-931: Actually, on consideration, I'd also like to see some additional constructors: FailureException(String message,

[jira] Commented: (AXIS2-928) Not all added header elements are included in outgoing SOAP header unless run under debugger - bug in OMElement caching?

[ http://issues.apache.org/jira/browse/AXIS2-928?page=comments#action_12423454 ] Derek Foster commented on AXIS2-928: The version I was running when I reported this was the nightly build from about four days ago. I just downloaded and

[jira] Commented: (AXIS2-927) ADBXMLStreamReaderTest Failure....Appears to OM Related

[ http://issues.apache.org/jira/browse/AXIS2-927?page=comments#action_12423508 ] Davanum Srinivas commented on AXIS2-927: Rich, Can we please close this now? thanks, dims ADBXMLStreamReaderTest FailureAppears to OM Related

[jira] Commented: (AXIS2-892) Need Documentation for MTOM data binding

[ http://issues.apache.org/jira/browse/AXIS2-892?page=comments#action_12423512 ] robert lazarski commented on AXIS2-892: --- I added a databinding section, so far using xmlbeans. I plan on adding an ADB section ASAP. I'm an MTOM newbie so if