> -----Original Message-----
> From: Fred Dushin [mailto:[EMAIL PROTECTED]
> Sent: 09 March 2007 10:46
> To: [email protected]
> Subject: Re: Accessing Connection-based info from the transport
>
> One other thing -- I did not "refactor" the callout to the
> JettySSLListenerFactory to do this work, because there in no
> information in the SSL code that is needed to retrieve this
> information. It would make sense to have the lookup of the
> TLS Session information in the https namespace, but doing so
> introduces an artifical separation that's not really needed.
> Besides, there are already SSL abstractions in the http
> namespace, so the proposed change introduces no fundamental
> differences in behavior.
Well the only SSL visibility in the org.cxf.transport.http code is
simply to retrieve the configured SSL{Client|Server}Policy so as to pass
these on to the org.cxf.transport.https code, which then interprets and
applies the SSL policies.
As far as the org.cxf.transport.http code is concerned, the
SSL{Client|Server}Policy types are completely opaque, and the only
reason these are even visible in this code was a side-effect of how the
http-conf schema was defined (i.e. including references to types defined
in the security schema).
So I would like to maintain this separation between the http and https
code.
Cheers,
Eoghan
> Thanks,
> -Fred
>
> On Mar 9, 2007, at 5:37 AM, Fred Dushin wrote:
>
> > A new patch has been uploaded. Unfortunately, Jira does
> not seem to
> > allow me to remove the old one.
> >
> > Most of the changes Eoghan suggested have been incorporated. In
> > particular
> >
> > * Scratched the idea of a ContextInfo type, since no one took the
> > bait
> > * Added a TLSessionInfo struct (or the best Java has) to carry TLS
> > Session data
> > to the org.apache.cxf.security.transport namespace (API package)
> > * Supported in the Jetty and servlet http transports (http
> and http2)
> > (We gotta fix that!)
> > * Refactored Message and Exchange interfaces (and Impls) to now
> > extend
> > from a common base type -- not strictly needed, but definitely a
> > tidy cleanup
> > in the API
> >
> > Patch is off rev 516352.
> >
> > If someone could quickly review and install the patch, I'd be much
> > obliged.
> >
> > I have no ontological commitments to the proposed changes -- mostly
> > just the idea, so please feel free to morph the proposal to
> the idiom
> > du jour (As long as I can extract the needed information out of the
> > transport!).
> >
> > Thanks!
> > -Fred
> >
> > Here's a listing of the changes, as seen from my snapshot:
> >
> > 05:20:09 spock:~/src/apache/cxf/cxf-445> svn status
> > M rt/transports/http/src/main/java/org/apache/cxf/transport/
> > http/JettyHTTPDestination.java
> > M rt/transports/http/src/main/java/org/apache/cxf/transport/
> > servlet/ServletController.java
> > M rt/transports/http2/src/test/java/org/apache/cxf/transport/
> > http/JettyHTTPDestinationTest.java
> > M rt/transports/http2/src/main/java/org/apache/cxf/transport/
> > http/JettyHTTPDestination.java
> > M rt/transports/http2/src/main/java/org/apache/cxf/transport/
> > servlet/ServletController.java
> > M api/src/main/java/org/apache/cxf/message/Exchange.java
> > M api/src/main/java/org/apache/cxf/message/ExchangeImpl.java
> > M api/src/main/java/org/apache/cxf/message/Message.java
> > A api/src/main/java/org/apache/cxf/message/StringMap.java
> > M api/src/main/java/org/apache/cxf/message/MessageImpl.java
> > A api/src/main/java/org/apache/cxf/message/StringMapImpl.java
> > A api/src/main/java/org/apache/cxf/security
> > A api/src/main/java/org/apache/cxf/security/transport
> > A api/src/main/java/org/apache/cxf/security/transport/
> > TLSSessionInfo.java
>
>