Hehehe...see latest CVS. most methods are in WSHandler. for exceptions, i used WSSecurityException :). Need you to update WSS4JHandler to use the methods in WSHandler.
thanks, dims On 8/17/05, Venkat Reddy <[EMAIL PROTECTED]> wrote: > Dims, > > May be we can move all the methods of WS4JHandler into a base class, > except for handleRequest, handleResponse and processMessage. The > WSDoAllSender, WSDoAllReceiver can probably extend the base classs, > and delegate the calls (might need to wrap the JAXRPCException into an > AxisFault, or may be not - its a runtime exception). > > Please let me know how i can help you. > > - venkat > > > On 8/17/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > Werner, Venkat, > > > > In my sandbox, Am working on setting up one class hierarchy for all > > handlers (WSDoAllSender, WSDoAllReceiver, WSS4JHandler) to make it > > easier to maintain. I will check something in tomorrow, > > > > Could you both please help me smooth it out? then we can make a 1.1 > > quickly since it is a rework code and not a tiny rev (as you were > > thinking about making a release for one small bug AND the dependency > > jars). > > > > thanks, > > dims > > > > On 8/10/05, Dittmann, Werner <[EMAIL PROTECTED]> wrote: > > > Ben, > > > > > > it would be great if you can add your enhancements to > > > Venkat's changes and produce a diff. In the longer > > > term it would be feasible to support only one handler > > > type only. Due to portability I would prefer the > > > JAX-RPC handler. Currently we have to fix both > > > handlers if an error or problem shows up. This is > > > time consuming and error prone. > > > > > > Regards, > > > Werner > > > > > > > -----Ursprüngliche Nachricht----- > > > > Von: [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] > > > > Gesendet: Dienstag, 9. August 2005 16:40 > > > > An: Dittmann, Werner; [EMAIL PROTECTED] > > > > Betreff: RE: WSDoAllSender/Receiver Handler types > > > > > > > > > > > > Hi, > > > > > > > > Those changes are very similar to mine. I have FLOW, REQUEST_ONLY and > > > > RESPONSE_ONLY set up as DIRECTION, INCOMING and OUTGOING, and: > > > > > > > > 1) I set a default DIRECTION to OUTGOING for the client and > > > > INCOMING for the > > > > service, as opposed to setting it to "" by default, which can cause a > > > > handler to be set, but not used if the parameter is not > > > > explicitly set up. > > > > 2) I allow for the possibility that the user may well want to > > > > have handlers > > > > for both incoming and outgoing mssages as opposed to making > > > > them mutually > > > > exclusive. > > > > > > > > The primary problem has been addressed with Venkat's changes, > > > > however, which > > > > is beautiful! > > > > > > > > Many thanks again, > > > > > > > > Ben > > > > > > > > > -----Original Message----- > > > > > From: Dittmann, Werner [mailto:[EMAIL PROTECTED] > > > > > Sent: Tuesday, August 09, 2005 2:01 AM > > > > > To: Temko, Benjamin ; [EMAIL PROTECTED] > > > > > Subject: AW: WSDoAllSender/Receiver Handler types > > > > > > > > > > > > > > > Ben, Dims, > > > > > > > > > > pls have a look ate the latest version of the JAX-RPC > > > > > handler (Revision 1.9). Venkat checked in som modifications > > > > > that IMHO address the same problem - determine the > > > > > request / response handling. Can you pls check if these > > > > > mods are sufficient or need some enhancements? > > > > > > > > > > Thanks. > > > > > > > > > > Regards, > > > > > Werner > > > > ___________________________________________________________________ > > > > The information contained in this message and any attachment may be > > > > proprietary, confidential, and privileged or subject to the work > > > > product doctrine and thus protected from disclosure. If the reader > > > > of this message is not the intended recipient, or an employee or > > > > agent responsible for delivering this message to the intended > > > > recipient, you are hereby notified that any dissemination, > > > > distribution or copying of this communication is strictly prohibited. > > > > If you have received this communication in error, please notify me > > > > immediately by replying to this message and deleting it and all > > > > copies and backups thereof. Thank you. > > > > > > > > > > > > > > > > > -- > > Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
