[jira] Commented: (AXIS2C-723) add new transport in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608985#action_12608985 ] Senaka Fernando commented on AXIS2C-723: Hi Danushka, Damitha, If this can be

broken link

Hello, The link on http://ws.apache.org/axis2/ (top right of the page) pointing to Axis2/C is broken (for a long time already). It is http://ws.apache.org/c where it should be http://ws.apache.org/axis2/c. Regards Franz -

Re: broken link

Thanks for pointing this. Can you add a issue for this here[1] to make sure we does not miss this. [1] - http://ws.apache.org/axis2/issue-tracking.html -Rajika On Sat, Jun 28, 2008 at 2:06 PM, Dr. Franz Fehringer [EMAIL PROTECTED] wrote: Hello, The link on http://ws.apache.org/axis2/ (top

[jira] Assigned: (AXIS2C-1152) memory leak in code generated by WSDL2C, svc_qname not freed in axis2_stub_populate_services_for_myService

[ https://issues.apache.org/jira/browse/AXIS2C-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dushshantha Chandradasa reassigned AXIS2C-1152: --- Assignee: Dushshantha Chandradasa memory leak in code generated by

[jira] Commented: (AXIS2C-1152) memory leak in code generated by WSDL2C, svc_qname not freed in axis2_stub_populate_services_for_myService

[ https://issues.apache.org/jira/browse/AXIS2C-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608993#action_12608993 ] Dushshantha Chandradasa commented on AXIS2C-1152: - Yes Frederic. We can

[jira] Resolved: (AXIS2C-1152) memory leak in code generated by WSDL2C, svc_qname not freed in axis2_stub_populate_services_for_myService

[ https://issues.apache.org/jira/browse/AXIS2C-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dushshantha Chandradasa resolved AXIS2C-1152. - Resolution: Fixed Fixed memory leak in code generated by WSDL2C,

[jira] Commented: (AXIS2C-1188) SOAP fault not working with axis2c latest revision(663886) from code generated from axis2/java using adb

[ https://issues.apache.org/jira/browse/AXIS2C-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608997#action_12608997 ] Dushshantha Chandradasa commented on AXIS2C-1188: - I was able to reproduce

[jira] Assigned: (AXIS2C-1188) SOAP fault not working with axis2c latest revision(663886) from code generated from axis2/java using adb

[ https://issues.apache.org/jira/browse/AXIS2C-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Kamburugamuva reassigned AXIS2C-1188: --- Assignee: Supun Kamburugamuva SOAP fault not working with axis2c latest

Re: Changing the http status code in the response

If your response is a success or accepted, AxisServlet will return the response code as 200 OK or 202 Accepted. You will not be able to change this. But you could change the response header to 401 Unauthorized, by setting property Constants.HTTP_RESPONSE_STATE to

Hubert H Leung is out of the office.

I will be out of the office starting 06/28/2008 and will not return until 07/07/2008. Sheldon Lee-loy is my backup from 7/2/2008 to 7/4/2008.

Questions regarding Axis1.4

Hello, I am sorry to email in this manner. But I have run into an issue that I just can't figure out. I have searched the Internet without any luck. I have a web service running under Axis1.4. One of the methods returns an array of string to the client. Each string in the array is actually

RE: [axis2] weblogic deployment

Any answers here? Just curious why I have to explode my WAR or maintain a services.list if WAR is packed even though I actually keep my aar files outside of the WAR altogether ... my Axi2.xml config file is modified to reference this location. -Original Message- From: Tony Dean

RE: [axis2] jar dependency

I'm assuming when you make a new Axis2 release, you obtain the latest versions of dependent jars and redistribute them as well. Is there any way to determine in Axis2 1.4 which dependent jars require the latest versions? At this time I do not want to update dependent jars unless there is a