axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roshan Weerasuriya <ros...@opensource.lk>
Subject Re: Handler API issues
Date Tue, 03 Aug 2004 10:40:47 GMT
hi Sharanka and Adrian,

> I hate to be a bother, but could you also make provisions to allow a
> handler
> to get (and set) element attribute values? Taking the following
element as
> an example:
> 
> <wsse:Password Type="...#PasswordDigest">
> 
> It would be nice (actually, it would be essential) if the value for
'Type'
> could be set and later obtained by the handler code.

Done. 

Adrian, thanks for the patch for the setters. I also included the
getters for Attributes.

Roshan

On Sat, 2004-07-31 at 23:13, Roshan Weerasuriya wrote:
> hi Adrian,
> 
> I have applied your patch to the code base and after testing I will
> commit it.
> 
> Roshan
> 
> On Fri, 2004-07-30 at 14:14, John Hawkins wrote:
> > 
> > Adrian -we can check easily enough and if not can put them in HEAD.
> > 
> > 
> > John Hawkins
> > 
> > 
> >                                                                            
> >              Adrian                                                        
> >              Dick/UK/IBM@IBMGB                                             
> >                                                                         To 
> >              30/07/2004 08:14          "Apache AXIS C Developers List"     
> >                                        <axis-c-dev@ws.apache.org>        
 
> >                                                                         cc 
> >              Please respond to                                             
> >               "Apache AXIS C                                       Subject 
> >              Developers List"          Re: Handler API issues              
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Hi,
> > 
> > We have also been needing the functionality you are looking for, and have
> > submitted a number of patches in this area:
> >    Provide attributes on HeaderBlock      (see:
> >    http://marc.theaimsgroup.com/?l=axis-c-dev&m=108815005717273&w=2 )
> >    Provide attributes on ComplexElement  (see:
> >    http://marc.theaimsgroup.com/?l=axis-c-dev&m=108997505225595&w=2 )
> > 
> > I'm certain these are not in the 1.2 release, but due to being away
> > recently, I'm not too certain if they're in the current development
> > codebase.  Can anyone advise?
> > 
> > Regards,
> > Adrian
> > _______________________________________
> > Adrian Dick (adrian.dick@uk.ibm.com)
> > 
> > 
> > 
> > 
> >              "Sharanka Perera"
> >              <sharanka@opensou
> >              rce.lk>                                                    To
> >                                        "Roshan Weerasuriya"
> >              29-07-04 17:48            <roshan@opensource.lk>
> >                                                                         cc
> >                                        "Apache AXIS C Developers List"
> >              Please respond to         <axis-c-dev@ws.apache.org>
> >               "Apache AXIS C                                       Subject
> >              Developers List"          Re: Handler API issues
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Hi Roshan, all,
> > 
> > Thanks for your help, and for the timely inclusion of the 'getLocalName'
> > call :)
> > 
> > I hate to be a bother, but could you also make provisions to allow a
> > handler
> > to get (and set) element attribute values? Taking the following element as
> > an example:
> > 
> > <wsse:Password Type="...#PasswordDigest">
> > 
> > It would be nice (actually, it would be essential) if the value for 'Type'
> > could be set and later obtained by the handler code.
> > 
> > Thanks again!
> > 
> > Sharanka
> > 
> > 
> > ----- Original Message -----
> > From: "Roshan Weerasuriya" <roshan@opensource.lk>
> > To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
> > Sent: Monday, July 26, 2004 7:36 PM
> > Subject: Re: Handler API issues
> > 
> > 
> > > Hi,
> > >
> > > >The API does not appear to make provisions to allow a handler to obtain
> > > > data from the client application.
> > >
> > > >Is it likely that this feature will be implemented any time soon?
> > >
> > > Yes, this has to be added to the Stub base class....... I will check and
> > > try to add this.....
> > >
> > > 2. When a handler gets data from a header block, instead of laboriously
> > > > parsing the resulting DOM tree, isn't it possible to simply "get" an
> > > > element, complex or otherwise, similar to what
> > > > "getHeaderBlock('element-name', 'namespace')" does? I don't think the
> > > > handler API provides this right now, but it would make a very useful
> > > > feature, IMHO, for future handler development efforts as well.
> > >
> > > Yes I guess that would be a good idea. Will look for this as well.
> > >
> > > Roshan
> > >
> > >
> > >
> > >
> > > On Sun, 2004-07-25 at 22:39, Sharanka Perera wrote:
> > > > Hi,
> > > >
> > > > I'm working on a security handler for the Apache ws-fx project called
> > wss4c.
> > > > I have two questions regarding the current handler API:
> > > >
> > > > 1. The API does not appear to make provisions to allow a handler to
> > obtain
> > > > data from the client application. For instace, if the client were to
> > pass an
> > > > username & password pair to the SOAP engine, the handler wouldn't
be
> > able to
> > > > get it. Ideally, this should be facilitated in the following manner-
> > > >
> > > > String sProVal1 = pIMsg-getProperty("username");
> > > > String sProVal2 = pIMsg-getProperty("password");
> > > >
> > > >
> > > > Is it likely that this feature will be implemented any time soon?
> > > >
> > > > 2. When a handler gets data from a header block, instead of laboriously
> > > > parsing the resulting DOM tree, isn't it possible to simply "get" an
> > > > element, complex or otherwise, similar to what
> > > > "getHeaderBlock('element-name', 'namespace')" does? I don't think the
> > > > handler API provides this right now, but it would make a very useful
> > > > feature, IMHO, for future handler development efforts as well.
> > > >
> > > > Thanks,
> > > >
> > > > Sharanka
> > > >
> > > >
> > > >
> > >
> > >
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 


Mime
View raw message