Hi Thiago,
Do you think we will be able to observe significant differences if we make
some functions inline?
Supun.
On Sat, Nov 22, 2008 at 12:50 AM, Thiago Rafael Becker
[EMAIL PROTECTED] wrote:
Hi, all
I was looking at the recursive functions and below are my findings.
In the case of
[
https://issues.apache.org/jira/browse/AXIS2-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650032#action_12650032
]
[EMAIL PROTECTED] commented on AXIS2-2149:
I am using axis2-1.4. i see
Wrong port number in generated WSDL
---
Key: AXIS2-4144
URL: https://issues.apache.org/jira/browse/AXIS2-4144
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: wsdl
Affects Versions: 1.4.1
[
https://issues.apache.org/jira/browse/AXIS2-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650094#action_12650094
]
Keith Godwin Chapman commented on AXIS2-4144:
-
Are you using a proxy of some
Nandana,
I have been playing with this for a while. In the case where the
service throws a fault there is no axisMessage in the msgCtx when we get
to axis2/context/MessageContext. One can use the FLOW variable to figure
out if it is an in or out message. The following patch works for me for
A null value for a Dispatch invocation using the XML/HTTP binding should be
acceptable while using HTTP GET method
--
Key: AXIS2-4145
URL:
