axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "duglin" <dug...@yahoo.com>
Subject Re: Fragment of deploy.xml with listeners
Date Fri, 25 May 2001 12:43:07 GMT
This seems to be headed down the path of having Axis
start-up listeners which is not a direction I think we want to go.

Having the "listener" option as an element or as
an attribute on the service element is good but I'm
not keen on the <listener> stuff.

You also didn't say what you were going to do with the
listener option value?  Where are you going to place it
and who/where is it going to be checked?

-Dug

----- Original Message -----
From: "Rob Jellinghaus" <robj@unrealities.com>
To: <axis-dev@xml.apache.org>
Sent: Thursday, May 24, 2001 10:13 PM
Subject: Fragment of deploy.xml with listeners


> Ran an earlier version by Glen, he thought it was OK....
>
> This is along the lines of Glen's "Transport" email.  This is a proposed
> extended syntax for deploy.xml (a la AdminClient.java).  Hopefully
whatever
> this is doing will also be doable via WSDD but I haven't looked yet
(sorry,
> James)....
>
> <deploy>
> <chain name="secure_http" flow="HTTPAuthHandler,URLMapper"/>
> <chain name="open_tcp" flow="TCPActionHandler"/>
> <listener name="admin_servlet" type="servlet" input_chain="secure_http">
> <servlet>SecondServlet</servlet>
> </listener>
> <listener name="open_port" type="tcp" input_chain="open_tcp">
> <port>8888</port>
> </listener>
> <service name="urn:xmltoday-delayed-quotes" pivot="stock">
> <option name="className" value="samples.stock.StockQuoteService" />
> <option name="methodName" value="getQuote" />
> <option name="listener" value="open_port"/>
> </service>
> </deploy>
>
> This deploys two chains (a secure HTTP transport input chain, and a
> wide-open TCP transport input chain).  It then defines a servlet listener
> ("admin_servlet") associated with the servlet named SecondServlet, and a
> TCP listener ("open_port") on port 8888.  Finally, it defines the stock
> service, specifying that it can only be accessed via the TCP listener.
>
> A slightly more aggressive model lets us actually *deploy classes of
> Listeners*:
>
> <listenerType name="servlet"
> class="org.apache.axis.transport.http.ServletListener"/>
> <listenerType name="tcp"
class="org.apache.axis.transport.tcp.TCPListener"/>
> ... rest as above ...
>
> Thoughts?  I am going to start implementing this tonight since this is the
> right next step in the direction of having dynamically added & removed
> transport endpoints.
>
> Cheers!
> Rob
>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


Mime
View raw message