Re: dynamic security levels with WSS4J

[Robert Maier]

Werner,

Thanks for the reply, I had a feeling that it might be an Axis issue, I just hoped someone had this problem before and did something about it :) Especially since the chaining mechanism can become quite inflexible if no dynamic mechanism exists to control which handler goes in the chain and which not.

As far as I've seen the chain mechanism is based on the Chain of Responsibility design pattern, but it seems that it's a variant of that design pattern.

Would such a "meta-handler" be easily pluggable in the current Axis (not Axis2) architecture?

Thanks.
Cheers,
Robert.

On 6/22/06, Dittmann, Werner <[EMAIL PROTECTED]> wrote:

You are right, this is an Axis problem. One can solve that problem using a

"Meta-handler" that is the first one in a chain that looks into the request,

analyses the request, for example which SOAP headers are available, and

calls "sub-handlers" to process the request. Such a "Meta-Handler" could

have its own parameters that control its behaviour.

 

AFAIK there is no such "Meta-Handler" available or under construction

(hint, hint).

 

Regards,

Werner

---

Von: Robert Maier [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 22. Juni 2006 09:08
An: wss4j-dev@ws.apache.org
Betreff: dynamic security levels with WSS4J

Hi,

My name is Robert Maier, I just subscribed to this list so this is my first post. I have been following the list offline for a couple of weeks now, many of your answers have been very helpful to me, thanks.

Let me get to the point. I recently started working with WSS4J and using the mailing list and other docs I managed to have a service and a client (both using Apache Axis 1.4 as SOAP engine and WSS4J for WS-Security) communicate securely, i.e. signed and/or encrypted messages.

My current problem: I am trying to make the service more flexible, i.e. I'd like it to understand whatever SOAP Requests it receives no matter if they are signed, encrypted, both signed and encrypted or neither. At this point the service only understands one type of SOAP Request (defined in its wsdd file using the WSDoAllReceiver handler). Is there a simple way of doing this?

[ This is Axis architecture specific: Theoretically, a simple solution to this problem would be to have Axis allow a handler mechanism where not all the handlers in a chain must process the message, but so far I have been unable to find this possiility ]

Thanks.
Cheers,
Robert.