Kaushalye Kapuruge <[EMAIL PROTECTED]> writes:
> +1. But when it comes to submodule prefix, could this be a problem?
> Say I need to use prefix
> [rampart][oxs] for OMXMLSecurity and
> [rampart][util] for Utility module etc.
> Would that be a big issue if we give the freedom of passing the prefix?
[
https://issues.apache.org/jira/browse/AXISCPP-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra reopened AXISCPP-1043:
-
Investigating...I think there is a problem.
> Error handling several HTTP headers in one response
SOAP action not parsed correctly when it is contained in the content type from
a MTOM message
-
Key: AXIS2C-1124
URL: https://issues.apache.org/jira/browse/AXIS2C-1124
Varuna,
There is a processing difference in a multi-threaded environment. If you
are using an iterator, you are using a structure that is allocated and
attached to the tree. So if two threads are operating at the same point in
the same tree at the same time, they will be using the one iterator a
On Wed, Apr 30, 2008 at 5:01 PM, Kaushalye Kapuruge <[EMAIL PROTECTED]> wrote:
> +1. But when it comes to submodule prefix, could this be a problem? Say I
> need to use prefix
> [rampart][oxs] for OMXMLSecurity and
> [rampart][util] for Utility module etc.
> Would that be a big issue if we giv
Chintana Wilamuna wrote:
On Wed, Apr 30, 2008 at 10:51 AM, Ruwan Janapriya <[EMAIL PROTECTED]> wrote:
AXIS2_DEBUG_MSG(env->log, "[Project XYZ] Debug Message Tik Tak Too");
also the above macro name AXIS2_DEBUG_MSG is open for better (short) name
suggestions. Since the env->log part has the
Varuna,
"Varuna Jayasiri" <[EMAIL PROTECTED]> writes:
> What's the difference between children iterator and the
> axiom_node_get_next_sibling? Is there a difference in the way they are
> processed?
I couldn't recall where is used children iterator last time :), If you
look into children iterato
Chintana Wilamuna wrote:
On Wed, Apr 30, 2008 at 10:51 AM, Ruwan Janapriya <[EMAIL PROTECTED]> wrote:
AXIS2_DEBUG_MSG(env->log, "[Project XYZ] Debug Message Tik Tak Too");
also the above macro name AXIS2_DEBUG_MSG is open for better (short) name
suggestions. Since the env->log part has the
On Wed, Apr 30, 2008 at 10:51 AM, Ruwan Janapriya <[EMAIL PROTECTED]> wrote:
> AXIS2_DEBUG_MSG(env->log, "[Project XYZ] Debug Message Tik Tak Too");
>
> also the above macro name AXIS2_DEBUG_MSG is open for better (short) name
> suggestions. Since the env->log part has the information that we are
[
https://issues.apache.org/jira/browse/AXIS2C-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593289#action_12593289
]
Dimuthu Gamage commented on AXIS2C-1121:
Unfortunately WSDL2C is not a single '.j
[
https://issues.apache.org/jira/browse/AXIS2C-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-1123.
---
Resolution: Fixed
Works with latest nightly build
> not able to genrate c/c++ clien
Samisa Abeysinghe <[EMAIL PROTECTED]> writes:
> But that does not follow out convention. AXIS2_ is the prefix, and
> LOG_ is the name of the struct. So as per our conventions it has to
> be, AXIS2_LOG_DEBUG_MSG
I think AXIS2_LOG_DEBUG_MSG is the correct name for that macro.
thanks,
Dinesh
--
htt
[
https://issues.apache.org/jira/browse/AXIS2C-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe updated AXIS2C-1123:
--
Fix Version/s: (was: 1.3.0)
> not able to genrate c/c++ client and server side cod
Hi All,
There are a couple of things about AXIOM I'm not clear about. Thought of
asking it from you before going through the code. Please don't mind if they
are stupid questions :)
What's the difference between children iterator and the
axiom_node_get_next_sibling? Is there a difference in the
Sanjaya Karunasena wrote:
On Wednesday 30 April 2008, Dinesh Premalal wrote:
"Ruwan Janapriya" <[EMAIL PROTECTED]> writes:
AXIS2_LOG_DEBUG (env->log, AXIS2_LOG_SI, "[Project XYZ] Debug Message Tik
Tak Too");
I feel the above macro is little bit less readable, also atleast causes
unneed
Dinesh Premalal wrote:
Hi Damitha/All,
Damitha Kumarage <[EMAIL PROTECTED]> writes:
This is a good thing to do +1. We need to do a global replace in the
current code base.
I would like to keep the current code base as it is , and adapt for
new macro for future modifications. Because
Hi Damitha/All,
Damitha Kumarage <[EMAIL PROTECTED]> writes:
> This is a good thing to do +1. We need to do a global replace in the
> current code base.
>
I would like to keep the current code base as it is , and adapt for
new macro for future modifications. Because there may be others who
used t
Hi Ruwan,
Ruwan Janapriya wrote:
Hi Devs,
Currently in AXIS2C we are using following Macros to log DEBUG, INFO,
ERROR etc.. messages.
AXIS2_LOG_DEBUG (env->log, AXIS2_LOG_SI, "[Project XYZ] Debug Message
Tik Tak Too");
I feel the above macro is little bit less readable, also atleast
caus
[
https://issues.apache.org/jira/browse/AXIS2C-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor resolved AXIS2C-1121.
--
Resolution: Fixed
Fix Version/s: Current (Nightly)
Problems with WSDL2C generator resolved in nightly r
[
https://issues.apache.org/jira/browse/AXIS2C-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593261#action_12593261
]
Igor commented on AXIS2C-1121:
--
Thank you Dimuthu.
With snapshot everything work fine.
> Exc
On Wednesday 30 April 2008, Dinesh Premalal wrote:
> "Ruwan Janapriya" <[EMAIL PROTECTED]> writes:
> > AXIS2_LOG_DEBUG (env->log, AXIS2_LOG_SI, "[Project XYZ] Debug Message Tik
> > Tak Too");
> >
> > I feel the above macro is little bit less readable, also atleast causes
> > unneeded extra key stro
21 matches
Mail list logo
