Re: More readable LOG Macros.

2008-04-30 Thread Dinesh Premalal
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 strokes to write a log. It is no harm in keeping the above, but we can have a

Re: More readable LOG Macros.

2008-04-30 Thread Sanjaya Karunasena
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 strokes to write a

Re: More readable LOG Macros.

2008-04-30 Thread Damitha Kumarage
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 causes

[jira] Commented: (AXIS2C-1121) Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException

2008-04-30 Thread Igor (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12593261#action_12593261 ] Igor commented on AXIS2C-1121: -- Thank you Dimuthu. With snapshot everything work fine.

[jira] Resolved: (AXIS2C-1121) Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException

2008-04-30 Thread Igor (JIRA)
[ 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

Re: More readable LOG Macros.

2008-04-30 Thread Dinesh Premalal
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 this

Re: More readable LOG Macros.

2008-04-30 Thread Samisa Abeysinghe
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 unneeded

Axiom

2008-04-30 Thread Varuna Jayasiri
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

Re: More readable LOG Macros.

2008-04-30 Thread Samisa Abeysinghe
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

[jira] Updated: (AXIS2C-1123) not able to genrate c/c++ client and server side code from wsdl having complex type

2008-04-30 Thread Samisa Abeysinghe (JIRA)
[ 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

Re: More readable LOG Macros.

2008-04-30 Thread Dinesh Premalal
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 --

[jira] Resolved: (AXIS2C-1123) not able to genrate c/c++ client and server side code from wsdl having complex type

2008-04-30 Thread Samisa Abeysinghe (JIRA)
[ 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++

[jira] Commented: (AXIS2C-1121) Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException

2008-04-30 Thread Dimuthu Gamage (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12593289#action_12593289 ] Dimuthu Gamage commented on AXIS2C-1121: Unfortunately WSDL2C is not a single

Re: More readable LOG Macros.

2008-04-30 Thread Chintana Wilamuna
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 going to

Re: More readable LOG Macros.

2008-04-30 Thread Damitha Kumarage
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

Re: More readable LOG Macros.

2008-04-30 Thread Kaushalye Kapuruge
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

Re: More readable LOG Macros.

2008-04-30 Thread Chintana Wilamuna
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 give the

RE: Axiom

2008-04-30 Thread Bill Mitchell
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

[jira] Created: (AXIS2C-1124) SOAP action not parsed correctly when it is contained in the content type from a MTOM message

2008-04-30 Thread Tommy Odom (JIRA)
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

[jira] Reopened: (AXISCPP-1043) Error handling several HTTP headers in one response

2008-04-30 Thread nadir amra (JIRA)
[ 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

[Axis2] removed Annogen dependency

2008-04-30 Thread Deepal jayasinghe
Hi all, As we discussed in the mailing list I removed the annogen dependency and just use JDK support for annotation processing. So now the Axis2 code base will not work with JDK 1.4. Removing annogen from Axis2 was a major code change because Axis2 uses annogen all over the code base.

optimized mime serialization

2008-04-30 Thread superrafcio
Hi, I'am using version 1.3 of Axix 2 project with addressing (1.3), rahas (1.3), rampart (1.3) and sandesha2 (1.3) modules. I've generated client class using WSDL which was generated based on web service working under MS WCF. When application starts it notifies me that: [DEBUG] can't find any

Re: Parser already accessed

2008-04-30 Thread Saminda Abeyruwan
please set true to setAllowedRetry in HttpTransportProperties .Authenticator Saminda On Tue, Apr 29, 2008 at 8:26 PM, qing neo [EMAIL PROTECTED] wrote: I search it at mailarchive,I find a similar bug: [jira] (AXIS2-3068)http://marc.info/?l=axis-devm=119434867413763w=2, but if I use axis2

[jira] Commented: (AXIS2-3651) BeanUtil class should try and fill the xsi:type attribute with value from type table before defaulting to class name

2008-04-30 Thread Detelin Yordanov (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12593315#action_12593315 ] Detelin Yordanov commented on AXIS2-3651: - Hello guys, I'm not sure that I am

[Axis2] optimized mime serialization

2008-04-30 Thread Jaliya Ekanayake
Forwarding with Axis2 subject. Jaliya - Original Message - From: superrafcio To: axis-dev@ws.apache.org Sent: Wednesday, April 30, 2008 5:39 AM Subject: optimized mime serialization Hi, I'am using version 1.3 of Axix 2 project with addressing (1.3), rahas (1.3), rampart (1.3) and

[jira] Commented: (AXIS2-3651) BeanUtil class should try and fill the xsi:type attribute with value from type table before defaulting to class name

2008-04-30 Thread Aaron Gourley (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12593347#action_12593347 ] Aaron Gourley commented on AXIS2-3651: -- It is my feeling that if Datelin is right

[jira] Commented: (AXIS2-3651) BeanUtil class should try and fill the xsi:type attribute with value from type table before defaulting to class name

2008-04-30 Thread nadir amra (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12593365#action_12593365 ] nadir amra commented on AXIS2-3651: --- I agree with Aaron...if there is a problem on the

SOAP Over JMS problem with Axis 1.3

2008-04-30 Thread go2rk
I am developing a web service over TIBCO JMS with axis 1.3. My service is installed in jboss 4.0.4. My problem is the wsdl is not getting created for this. In the service list(http://localhost:8080/axis2/services/listServices) it is showing active status. but when I visit go to

[jira] Created: (AXIS2-3774) WSDL is not getting generated with SOAP Over JMS

2008-04-30 Thread Ramakrishna (JIRA)
WSDL is not getting generated with SOAP Over JMS Key: AXIS2-3774 URL: https://issues.apache.org/jira/browse/AXIS2-3774 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: samples

Re: [Axis2] optimized mime serialization

2008-04-30 Thread Thilina Gunarathne
Hi, AFAIK you need to create an axis2 repository containing the required modules mar files (mtom policy, sandesha, rampart..) . Then you need to use that repository to create a configuration context and pass it to the constructor of the generated stub... IIRC generated stub has constructors that