You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Janne Savukoski <ja...@savukoski.name> on 2007/03/27 10:27:21 UTC

Dynamic HTTPS endpoints

Hi,

I can't get dynamic HTTPS-endpoints (provider, as in httpclient) to
work as I can't get the SSL-stuff configured. I'm just getting an npe
from CommonsHttpSSLSocketFactory:47, naturally... Is there a way to do
this? Ie. define the ssl configuration somehow. Or is the only way to
get HTTPS to work is to use static endpoints defined in the xbean.xml
(of servicemix-http)?

Regarding previous, according to the little bit what I've managed to
read from the source, it seems HTTPS can't be used with
WSDL-deployments either. Is this correct?

-janne

Re: Dynamic HTTPS endpoints

Posted by tp <au...@gmail.com>.
Hi Guillaume, 

I have a similar problem as described by Janne. I need to create dynamic
HTTPS-endpoint which requires some SSL-stuff to be configured.

Currently I'm using following piece of code to create the provider non-ssl
http endpoint:

DocumentFragment epr = URIResolver.createWSAEPR(uri);
ServiceEndpoint providerEndpoint =
getContext().resolveEndpointReference(epr);

Is it possible to add the SSL parameters dynamically - using the same
approach for creating the http endpoint?

In your post you mention that it can be done using dynamic http endpoints in
"managed mode". Can you please point me to some documentation/examples
related to this?


gnodet wrote:
> 
> On 3/27/07, Janne Savukoski <ja...@savukoski.name> wrote:
>>
>> Hi,
>>
>> I can't get dynamic HTTPS-endpoints (provider, as in httpclient) to
>> work as I can't get the SSL-stuff configured. I'm just getting an npe
>> from CommonsHttpSSLSocketFactory:47, naturally... Is there a way to do
>> this? Ie. define the ssl configuration somehow. Or is the only way to
>> get HTTPS to work is to use static endpoints defined in the xbean.xml
>> (of servicemix-http)?
> 
> 
> Yeah, it may be a bit difficult as there are several parameters that need
> to
> be
> configured for HTTPS.  However, it should be easier to use dynamic http
> endpoints
> in "managed mode": i.e. when it reuses an existing web container, such as
> when
> the apache-servicemix-web distribution.
> 
> Regarding previous, according to the little bit what I've managed to
>> read from the source, it seems HTTPS can't be used with
>> WSDL-deployments either. Is this correct?
> 
> 
> Same answer.
> 
> -janne
>>
> 
> 
> 
> -- 
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
> 
> 

-- 
View this message in context: http://www.nabble.com/Dynamic-HTTPS-endpoints-tf3471693s12049.html#a10197602
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: Dynamic HTTPS endpoints

Posted by Guillaume Nodet <gn...@gmail.com>.
On 3/27/07, Janne Savukoski <ja...@savukoski.name> wrote:
>
> Hi,
>
> I can't get dynamic HTTPS-endpoints (provider, as in httpclient) to
> work as I can't get the SSL-stuff configured. I'm just getting an npe
> from CommonsHttpSSLSocketFactory:47, naturally... Is there a way to do
> this? Ie. define the ssl configuration somehow. Or is the only way to
> get HTTPS to work is to use static endpoints defined in the xbean.xml
> (of servicemix-http)?


Yeah, it may be a bit difficult as there are several parameters that need to
be
configured for HTTPS.  However, it should be easier to use dynamic http
endpoints
in "managed mode": i.e. when it reuses an existing web container, such as
when
the apache-servicemix-web distribution.

Regarding previous, according to the little bit what I've managed to
> read from the source, it seems HTTPS can't be used with
> WSDL-deployments either. Is this correct?


Same answer.

-janne
>



-- 
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/