[jira] Resolved: (AXISCPP-858) client stub delete Ret; causes Debug Assertion Failed! Win32

[ http://issues.apache.org/jira/browse/AXISCPP-858?page=all ] Adrian Dick resolved AXISCPP-858: - Fix Version: 1.6 Beta Resolution: Fixed Brian, I'm going to mark this as resolved because this problem has been reported several times with

Patch licensing question

Hi, I'm sorry to bother you with this, but we may be contributing some patches and have a very simple question: When a contributor provides a patch (obviously under Apache license), is it mandatory to assign copyright to Apache Software Foundation, or can it have another copyright? (i.e.

Re: Patch licensing question

Hi, We looking into this a while back. Basically, yes it is mandatory for all files to have the Apache Software Foundation copyright statement. But, you may also include additional copyright statements where appropriate. If you need a more complete answer, trying asking on the legal mailing list

Re: Patch licensing question

Hi Adrian, I think this is all I need. Thanks a lot! El mi, 12-04-2006 a las 15:48, Adrian Dick escribi: Hi, We looking into this a while back. Basically, yes it is mandatory for all files to have the Apache Software Foundation copyright statement. But, you may also include additional

Re: streams

Axis2 sorts this out using MTOM and DataHandlers. The data can be streamed, and also doesn't need to be base64 encoded.PaulOn 4/11/06, ciaran dunn [EMAIL PROTECTED] wrote: Also, and the reason I replied to the original message, what is the nature of your data in the byte[] part. Ive worked on

[jira] Commented: (AXIS2-557) Problems when generating stubs and skeletons from wsdl

[ http://issues.apache.org/jira/browse/AXIS2-557?page=comments#action_12374167 ] Michel.Drescher commented on AXIS2-557: --- Hi, I can confirm the latter case. The exception is *exactly* the same. The command I used was as this:

[jira] Created: (AXIS2-565) Namespace vanishes using StAXOMBuilder

Namespace vanishes using StAXOMBuilder -- Key: AXIS2-565 URL: http://issues.apache.org/jira/browse/AXIS2-565 Project: Apache Axis 2.0 (Axis2) Type: Bug Versions: 0.95 Environment: Windows XP, Java 1.5 Reporter: Ant

[jira] Commented: (AXIS2-546) Multithreaded client dies with JVM_BIND address already in use

[ http://issues.apache.org/jira/browse/AXIS2-546?page=comments#action_12374174 ] rnell commented on AXIS2-546: - Please close, threads trying to launch separate listeners on same port. I needed to configure a new Context for each thread or reuse an existing

[jira] Created: (AXIS2-566) Multiple ServiceClients using the same configurationContext causes NPE

Multiple ServiceClients using the same configurationContext causes NPE -- Key: AXIS2-566 URL: http://issues.apache.org/jira/browse/AXIS2-566 Project: Apache Axis 2.0 (Axis2) Type: Bug Components:

Re: [axis2] Security failures?

Hi Ruchith: I just checked the build and it was successful. Yup - I did a total clean and rebuild from scratch yesterday night and that worked fine. Thanks! --G

[jira] Commented: (AXIS2-565) Namespace vanishes using StAXOMBuilder

[ http://issues.apache.org/jira/browse/AXIS2-565?page=comments#action_12374190 ] Ruchith Udayanga Fernando commented on AXIS2-565: - This problem seems to be fixed in the latest AXIOM code. I couldn't see any missing namespaces when I ran

[jira] Updated: (AXIS-2460) Axis 1.3 OutOfMemory error when serializing a Java Object Graph

[ http://issues.apache.org/jira/browse/AXIS-2460?page=all ] Mohit Keswani updated AXIS-2460: Attachment: javacore966834.1144250024.txt Core dump txt Axis 1.3 OutOfMemory error when serializing a Java Object Graph

[jira] Updated: (AXIS-2460) Axis 1.3 OutOfMemory error when serializing a Java Object Graph

[ http://issues.apache.org/jira/browse/AXIS-2460?page=all ] Mohit Keswani updated AXIS-2460: Attachment: ClientSourceCode.zip Axis 1.3 OutOfMemory error when serializing a Java Object Graph

Re: Axis leaking Session objects

Hello all, I also encountered the memory leak problem in SoapService. Ben's patch looks OK. But I have a question, why is there this hashtable ? sessions is private, and there is not method/accessor to read its content, we only can add new Session. This hashtable was added in version 256500. And

[jira] Created: (AXIS2-567) Slow class loading issue

Slow class loading issue Key: AXIS2-567 URL: http://issues.apache.org/jira/browse/AXIS2-567 Project: Apache Axis 2.0 (Axis2) Type: Bug Versions: 0.94 Environment: WinXP Axis2 Tomcat Reporter: rob hudson When I first connect

[jira] Created: (AXIS2-568) DeploymentEngine doesn't understand conf directory

DeploymentEngine doesn't understand conf directory -- Key: AXIS2-568 URL: http://issues.apache.org/jira/browse/AXIS2-568 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: core Versions: 0.95

[jira] Commented: (AXIS2-568) DeploymentEngine doesn't understand conf directory

[ http://issues.apache.org/jira/browse/AXIS2-568?page=comments#action_12374224 ] rnell commented on AXIS2-568: - To reproduce this bug I used: java -cp classpath org.apache.axis2.transport.jms.SimpleJMSListener -r etc/server-axis2.repo -c etc/jndi.properties

[jira] Commented: (AXIS-2461) New Mirror

[ http://issues.apache.org/jira/browse/AXIS-2461?page=comments#action_12374230 ] Bjorn Townsend commented on AXIS-2461: -- Hello, Did you mean to post this in the Axis JIRA? Perhaps you meant for it to go in Apache infrastructure? :) New Mirror

[jira] Commented: (AXIS-2460) Axis 1.3 OutOfMemory error when serializing a Java Object Graph

[ http://issues.apache.org/jira/browse/AXIS-2460?page=comments#action_12374233 ] Bjorn Townsend commented on AXIS-2460: -- Mohit, Have you changed the default memory allocation settings for your JVM? I could easily see a recordset that large exceeding

[jira] Commented: (AXIS-2460) Axis 1.3 OutOfMemory error when serializing a Java Object Graph

[ http://issues.apache.org/jira/browse/AXIS-2460?page=comments#action_12374236 ] Mohit Keswani commented on AXIS-2460: - Yes we have change the setting from initial 256M to 512M... The server seems to create the SOAP response fine. The client though

[Axis2][Axiom]Always building Object Model .. no streaming at server response flow

Hi Guys; According to http://issues.apache.org/jira/browse/AXIS2-483 it sound like axiom always build the object model before sending out the message. (e.g. If nobody accsess the body, we should write the object diectly to output stream, no need to build the tree) If that is the case there will

[jira] Commented: (AXIS2-565) Namespace vanishes using StAXOMBuilder

[ http://issues.apache.org/jira/browse/AXIS2-565?page=comments#action_12374250 ] Srinath Perera commented on AXIS2-565: -- Hi Ruchith; I thinnk my check in to STAXOMBuilder fix this. see line if(namespace == null || namespace.getPrefix() != prefix){.

[jira] Created: (AXIS2-569) When clicking on Validate on the Axis2 1.0RC1 Homepage, you get an exception about the refactored ws.commons to axiom classes

When clicking on Validate on the Axis2 1.0RC1 Homepage, you get an exception about the refactored ws.commons to axiom classes --- Key: AXIS2-569 URL:

Re: [Axis2][Axiom]Always building Object Model .. no streaming at server response flow

Hi Srinath, We've dealt with this already .. Axiom does *not* always build the object model before sending .. what it does is pull and push. The writer is responsible for turning off the tree building (caching) if the message is not needed. In any case, have you seen the recent performance

[axis2] AXIOM question

Hi folks: Could someone show me how to use AXIOM to create a SOAP Fault envelope with a given faultCode and reason string? Let's assume I have QName code and String reason sitting around. In Axis, I can do this: AxisFault fault = new AxisFault(code, reason, null, null);