This sounds good to me. Probably the best solution would be to make a 
protected send() method that had little-to-no envelope manipulation, and 
just put the XML content on the wire and returned what came back (if 
anything). I think SimpleSoapClient already has such a method, but it 
could be improved a little (by abstracting out the tracing and call to 
createMessage()). Once this has been done, it should be pretty 
straightforward to override SimpleSoapClient's default (HTTP) behavior and 
use a different protocol/API.

Dan



"Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 05/02/2007 
04:01:42 AM:

> Perhaps in the long run, would it be good to have Muse flexible enough
> so that the protocol can easily be specified/configured?  Right now, the
> Muse architecture is tightly coupled with HTTP.  If we can specify it to
> use HTTPS or some other protocol, or be able to plugin our own "protocol
> handler" classes so that SOAP messages can be sent over any protocol,
> this would be great!  The Muse core can then be used in any type of
> application, even non-server based.
> 
> Right now, the SimpleSoapClient code directly uses an HttpURLConnection.
> Perhaps that can be abstracted out, and another class can be plugged in
> to manage the connection?  If there's any other classes that make a
> remote connection to a client, they will need to be included in this
> update, too, so I'm not sure how work this will involve.
> 
> 
> 
> -----Original Message-----
> From: Oliver Waeldrich (JIRA) [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, May 02, 2007 12:50 AM
> To: [email protected]
> Subject: [jira] Updated: (MUSE-223) Add capability to specify a
> SSLSocketFactory for HTTPS based connections in SimpleSoapClient.
> 
> 
>      [
> https://issues.apache.org/jira/browse/MUSE-223?page=com.atlassian.jira.p
> lugin.system.issuetabpanels:all-tabpanel ]
> 
> Oliver Waeldrich updated MUSE-223:
> ----------------------------------
> 
>     Attachment: muse-223-patch.txt
> 
> Created a patch for this issue.
> 
> Implementations can now implement an AbstractResourceClient and pass a
> SimpleSoapClient on creation. The connection handler can be added to the
> SimpleSoapClient and is invoked directly before and after a SOAP mesage
> is sent.
> 
> This functionality can be used e.g. to set the desired SSLSocketFactory
> object for the SOAP connection.
> 
> > Add capability to specify a SSLSocketFactory for HTTPS based
> connections in SimpleSoapClient.
> > ----------------------------------------------------------------------
> > -----------------------
> >
> >                 Key: MUSE-223
> >                 URL: https://issues.apache.org/jira/browse/MUSE-223
> >             Project: Muse
> >          Issue Type: New Feature
> >          Components: Core Engine - Resource and Capability APIs
> >            Reporter: Oliver Waeldrich
> >         Assigned To: Dan Jemiolo
> >             Fix For: 2.3.0
> >
> >         Attachments: extension.zip, muse-223-patch.txt
> >
> >
> > In order to use certificate based client authentication with MUSE we 
> > would like to specify a SSLSocketFactory to be used when communicating
> 
> > with a MUSE server. Even though it is possible to specify a default 
> > SSLSocketFactory (see HttpsURLConnection.setDefaultSSLSocketFactory())
> > this is not feasible for environments, where e.g. a client needs to 
> > communicate with multiple server instances using different
> credentials.
> > Therefore I would suggest an extension to the SimpleSoapClient to 
> > specify a SSLSocketFactory  for https connections and to extend the
> client's send-functionality as indicated by the code below.
> >     HttpURLConnection connection =
> (HttpURLConnection)url.openConnection();
> >     if (connection instanceof HttpsURLConnection)
> >         if (mySSLSocketFactoryInstance =! null) {
> >
> ((HttpsURLConnection)connection).setSSLSocketFactory(mySSLSocketFactoryI
> nstance);
> >         }
> >     }
> 
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to