Ken Hofsass wrote:
> One general thing which is also related to STS support: I was thinking
> 'endpointAddress' maybe should be some sort of map object rather than
> just a string... maybe with the portname as the key. I'm not sure
> that's exactly right but it's probably closer than only taking the first
> endpoint address.
Rather than making it a map, I suggest you inject as many variables as
you need (just like we inject different port objects.)
> Another is that I was thinking the 'sts' element and 'isSTS' booleans,
> etc. should maybe be renamed more like 'system-service' or soemthing
> like that for clarity. In case there are other 'system' web services
> besides STS which need accessed, in particular for
> Transaction/Coordination. And that multiple 'system' webservices can be
> supported simultaneously (which I think is already the case or is at
> least partially supported). The case for secure transactions would
> require both an STS and a coordinator service, I think.
+1.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com