Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Subject: Fw: Re:changes
To: axis-c-dev@ws.apache.org
Message-ID: 
 <OF48B199B6.A237AE83-ON80256F2D.00429756-80256F2D.0043A5E2@uk.ibm.com>
From: Mark Whitlock <mark_whitlock@uk.ibm.com>
Date: Thu, 14 Oct 2004 13:18:53 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


Hi,
I have moved AXIS_SEVERITY_LEVEL to AxisTrace.h since applications never
need it. This should solve Valentin's immediate problem. I agree with John
that the rest of the work should be done in 1.4. I am interested in this
problem because I am interested in reworking the C bindings in 1.5 (and
removing them in 1.4).
Mark
Mark Whitlock
IBM

----- Forwarded by Mark Whitlock/UK/IBM on 14/10/2004 13:07 -----
                                                                           
             "sanjaya                                                      
             singharage"                                                   
             <sanjayas@opensou                                          To 
             rce.lk>                   "Apache AXIS C Developers List"     
                                       <axis-c-dev@ws.apache.org>          
             14/10/2004 12:07                                           cc 
                                                                           
                                                                   Subject 
             Please respond to         Re: changes                         
              "Apache AXIS C                                               
             Developers List"                                              
                                                                           
                                                                           
To avoid any confusion, the use of prefixes for the AXIS_SEVERITY_LEVEL
does
not have to do anything with the compilation issue described by bugs 172
and
162. What would be nice is to have the compilation issue that the transport
has with AxisTrace be solved so that the tranport module can be tested for
tracing too.

sanjaya.

----- Original Message -----
From: "sanjaya singharage" <sanjayas@opensource.lk>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Sent: Thursday, October 14, 2004 4:41 PM
Subject: Re: changes


> I took up the task of adding a prefix to  AXIS_SEVERITY_LEVEL but did not
> continue because the transport project would not compile with
> ENABLE_AXISTRACE turned on. This issue would be still there with the new
> transport. Please read the bugs 172 and 162.
>
> sanjaya.
>
> >
> > Simply putting namespaces around these enums would break C
applications,
> > since C does not support namespaces. I agree this is the right solution
> for
> > C++. For C, it would be good to prefix all enums with AXIS_. I don't
think
> > AXIS_SEVERITY_LEVEL needs to be externalised anyway, since it is only
used
> > by trace and AxisTrace.h is not external. There is also a problem with
> some
> > externalised #defines like XML_Ch and SOAPACTIONHEADER which could also
> > clash.
> >
> > So I propose move AXIS_SEVERITY_LEVEL to AxisTrace.h, for C++ put
> > namespaces around all enums, for C prefix all enums with AXIS_, and for
> > *both* C and C++ prefix all #defines with AXIS_.
> >
> > Unfortunately this will require applications changing, WSDL2WS changes
and
> > stubs being regenerated when users move to 1.3. Is this critical for
1.3
> or
> > should we just move AXIS_SEVERITY_LEVEL to AxisTrace.h in 1.3 and fix
it
> > all properly for 1.4?
> >
> > I have raised JIRA AXISCPP-202 to track this problem.
> > Mark
> > Mark Whitlock
> > IBM
> >
> >
> >
>
>
>
>