Hi Yonny

Unless you are very familiar with the scenario Oleg is trying to explain, the current non-blocking http/s transport we are going to check into the Axis2 trunk this week would solve your problems for sure. It will not expose anything too advanced for one to work with, and would handle a huge number of concurrent connections well with a much smaller thread pool. So I suggest that you try to use it for your scenario as well.

If you want to look how this operates right now - today,.. you could download Apache Synapse 1.0 and try the bundled Axis2 server we ship with it. Its a http/s configuration which uses Axis2 1.2 and the Synapse download is only around 20M and there is enough documentation to help you get started

asankha

Yonny Hao wrote:
 I also agree that adding a simple SSL feature to SimpleHTTPServer is more useful, because in some cases, we just want secure the conversation

2007/6/19, Sanjiva Weerawarana < [EMAIL PROTECTED]>:
Oleg- I think an https listener associated with SimpleHTTPServer would be
very useful. In fact, I'd like to see the non-blocking HTTP transport from
Synapse brought over to this land and for that to be the default used in
SimpleHTTPServer .. which then would not be just simple but rather
SimpleScalableHTTPServer :).

Sanjiva.

Oleg Kalnichevski wrote:
> On Mon, 2007-06-18 at 21:36 +0800, Yonny Hao wrote:
>> Hi Oleg
>> Thank you for your timely reply.
>> Yes, I'm very interested in the SSL Http Server that can be used in
>> Axis2, so would you please email me? Thank you very much.
>>
>> Best Regards
>> Yonny
>>
>
> Yonny,
>
> I do not see a reason why this cannot be discussed on the axis-dev
> list.
>
> Adding SSL support to SimpleHttpServer would only require a trivial
> change to the DefaultConnectionListener [1]. Essentially all it takes is
> a custom server socket factory injected into DefaultConnectionListener
> upon configuration.
>
> A more important question is whether adding SSL support to
> SimpleHttpServer makes sense or whether Axis developers would rather see
> people use a servlet engine for such scenarios.
>
> Oleg
>
> [1]
> http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/http/server/DefaultConnectionListener.java
>
>
>> 2007/6/18, Oleg Kalnichevski <[EMAIL PROTECTED]>:
>>         On Mon, 2007-06-18 at 19:01 +0800, Yonny Hao wrote:
>>         >
>>         > Hi All
>>         > I developed a WS and deploy it in Axis2-1.2. I want to let
>>         the WS
>>         > included a SSL-secured endpoint and show the https endpoint
>>         info in
>>         > WSDL when request ?wsdl url. I opened the 8443 port of
>>         tomcat5.5 to
>>         > receive https request, then I added the following lines to
>>         axis2.xml
>>         > <transportReceiver name="https"
>>         >                        class=" org.apache.axis2.transport
>>         > .http.SimpleHTTPServer">
>>         >         <parameter name="port">8443</parameter>
>>         > </transportReceiver>
>>         >
>>         > , at last I configure my WS' services.xml to use the https
>>         transport,
>>         > adding below code.
>>         > <transports>
>>         >    <transport>https</transport>
>>         > </transports>
>>         > but after I startup the tomcat, it throws
>>         >
>>         > Jun 18, 2007 5:52:13 PM
>>         >
>>         org.apache.axis2.transport.http.server.DefaultConnectionListenerFailureHandler failed
>>         > WARNING: Attempt number 1 of 10 to reestalish connection
>>         listener
>>         >
>>         [EMAIL PROTECTED] due to failure
>>         > java.net.BindException: Address already in use: JVM_Bind
>>         >     at java.net.PlainSocketImpl.socketBind(Native Method)
>>         >     at java.net.PlainSocketImpl.bind
>>         (PlainSocketImpl.java:359)
>>         >     at java.net.ServerSocket.bind(ServerSocket.java :319)
>>         >     at java.net.ServerSocket.<init>(ServerSocket.java:185)
>>         >     at java.net.ServerSocket.<init>(ServerSocket.java:97)
>>         >     at
>>         >
>>         org.apache.axis2.transport.http.server.DefaultConnectionListener.run(DefaultConnectionListener.java:82)
>>         >     at
>>         >
>>         edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
>>         > $Worker.runTask( ThreadPoolExecutor.java :665)
>>         >     at
>>         >
>>         edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
>>         > $Worker.run( ThreadPoolExecutor.java:690)
>>         >     at java.lang.Thread.run(Thread.java:619)
>>         >
>>         > my configuration is correct? Is there anybody to tell me how
>>         to deal
>>         > with it?
>>
>>         Yonny,
>>
>>         As far as I know Axis2 SimpleHttpServer does not currently
>>         support SSL
>>         out of the box (one can implement a custom listener, though).
>>         If there
>>         is interest, I could contribute one
>>
>>         Oleg
>>
>>
>>         >
>>         > Thanks
>>         >
>>         > --
>>         > Yonny Hao
>>
>>
>>         ---------------------------------------------------------------------
>>         To unsubscribe, e-mail: [EMAIL PROTECTED]
>>         For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>> --
>> Yonny Hao
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

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




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

Reply via email to