|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
Grizzly configHi,
as part of Grizzly and Glassfish v3 integration we introduce the grizzly config feature, which makes possible to save/restore Grizzly configuration. In the beginning we're planning to start to support it as part of GFv3, but then want to use it also for Grizzly standalone. Here you can find draft of the grizzly config DTD and XML example. The feedback is more than welcome! :) WBR, Alexey. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE network-config SYSTEM "grizzly-config.dtd"> <network-config> <transports> <!-- Transport describes network transport and its properties.--> <!-- Optional. Those apply to all transport element--> <selection-key-handler name="defSelectionKeyHandler" classname="com.my.MyTCPSelectionKeyHandler" idle-key-timeout="30"/> <!-- Declare new my-tcp transport --> <transport name="my-tcp" classname="com.my.MyTCPSelectorHandler"> <!-- Optional. In-place declaration of the SelectionKey handler --> <selection-key-handler classname="com.my.MyTCPSelectionKeyHandler" idle-key-timeout="30"/> </transport> <!-- Overwrite predefined TLS transport settings --> <transport name="tls" selection-key-handler="defSelectionKeyHandler"> <!-- Optional list of properties --> <property name="keyStore" value="keyStorePath/"/> <property name="trustStore" value="trustStorePath/"/> </transport> </transports> <protocols> <protocol name="http" max-selectors="30" read-timeout="5000" write-timeout="30000" oob-inline="true"> <property name= "com.sun.enterprise.web.connector.grizzly.enableSnoop" value="true"/> <protocol-chain-instance-handler> <protocol-chain> <protocol-filter classname="com.sun.grizzly.filter.HttpProtocolFilter" /> </protocol-chain> </protocol-chain-instance-handler> </protocol> <protocol name="multi-protocols" byte-buffer-type="DIRECT"> <property name="com.sun.enterprise.web.connector.grizzly.enableSnoop" value="true"/> <!-- Optional --> <!-- Port Unification section describes high-level protocols and there Finders. Several protocols can share the same listener using port unification mechanism. --> <port-unification> <!-- Mandatory --> <!-- The order is important here. If a Finder is successful The next Finder will not be invoked, but instead the associated the protocol will be called --> <finder classname="com.custom.MyHttpFinder" protocol="http"> <property name="someproperty" value="somevalue"/> </finder> <finder classname="com.custom.MyIIOPFinder"> <property name="someproperty" value="somevalue"/> <protocol name="iiop"> <protocol-chain-instance-handler> <protocol-chain> <protocol-filter classname="com.sun.grizzly.filter.IiopProtocolFilter" /> </protocol-chain> </protocol-chain-instance-handler> </protocol> </finder> </port-unification> </protocol> <protocol name="https"> <property name="-Dcom.sun....maxSelector" value="30"/> <ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"> <!-- Override the properties of the transport "tls" --> <property name="keyStore" value="keyStorePath/"/> <property name="trustStore" value="trustStorePath/"/> </ssl> <protocol-chain-instance-handler> <protocol-chain> <protocol-filter classname= "com.sun.grizzly.filter.HttpsProtocolFilter" /> </protocol-chain> </protocol-chain-instance-handler> </protocol> </protocols> <listeners> <!-- Listener binds Transport to the specific port and declares Protocol(s), listener --> <thread-pool name="defaultThreadPool" classname="mypool" min-threads="2" max-threads="5" max-tasks="4096"/> <listener name="http-listener" host="localhost" port="8080" transport="my-tcp" protocol="http" thread-pool="defaultThreadPool"> <!-- Mandatory --> <property name="reuseAddress" value="true"/> </listener> <listener name="https-listener" port="8181" transport="tls" protocol="https" thread-pool="defaultThreadPool"> <!-- Optional list of properties --> <property name="root" value="${user.home}/"/> </listener> <listener name="multi-listener" host="localhost" port="8080" transport="my-tcp" protocol="multi-protocols" thread-pool="defaultThreadPool"> <property name="reuseAddress" value="true"/> </listener> </listeners> </network-config> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Grizzly configLooks very clean!!
I would even like to use config-xml on client side? Would then need a element <call-back-handler> (or is it only going to be available for grizzly 2.0?) Many greetings John -------- Original-Nachricht -------- > Datum: Wed, 23 Jul 2008 13:58:12 +0200 > Von: Oleksiy Stashok <Oleksiy.Stashok@...> > An: dev@... > Betreff: Grizzly config > Hi, > > as part of Grizzly and Glassfish v3 integration we introduce the > grizzly config feature, which makes possible to save/restore Grizzly > configuration. > In the beginning we're planning to start to support it as part of > GFv3, but then want to use it also for Grizzly standalone. > > Here you can find draft of the grizzly config DTD and XML example. > > The feedback is more than welcome! :) > > WBR, > Alexey. -- GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion! http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Grizzly configHi,
Hmm, it could be interesting. Because for GFv3 we didn't plan any client side support, but for standalone it could be interesting. Nope, it's for 1.x For 2.0 probably we may have different abstractions, so different config schema will be required. WBR, Alexey.
|
|
|
Re: Grizzly configSalut,
Oleksiy Stashok wrote: > Hi, > >> >> I would even like to use config-xml on client side? >> Would then need a element <call-back-handler> > Hmm, it could be interesting. Because for GFv3 we didn't plan any client > side support, but for standalone it could be interesting. +1 For our community, we should really think about the client side. > >> (or is it only going to be available for grizzly 2.0?) > Nope, it's for 1.x > For 2.0 probably we may have different abstractions, so different config > schema will be required. Yup! Let's target 1.9.0 :-) Can you file an issue and attach the current proposal? That looks quite good! A+ -- Jeanfrancois > > WBR, > Alexey. > >> >> >> Many greetings >> John >> >> -------- Original-Nachricht -------- >>> Datum: Wed, 23 Jul 2008 13:58:12 +0200 >>> Von: Oleksiy Stashok <Oleksiy.Stashok@... >>> <mailto:Oleksiy.Stashok@...>> >>> An: dev@... <mailto:dev@...> >>> Betreff: Grizzly config >> >>> Hi, >>> >>> as part of Grizzly and Glassfish v3 integration we introduce the >>> grizzly config feature, which makes possible to save/restore Grizzly >>> configuration. >>> In the beginning we're planning to start to support it as part of >>> GFv3, but then want to use it also for Grizzly standalone. >>> >>> Here you can find draft of the grizzly config DTD and XML example. >>> >>> The feedback is more than welcome! :) >>> >>> WBR, >>> Alexey. >> >> -- >> GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit >> Pastry Passion! >> http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@... >> For additional commands, e-mail: dev-help@... >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
| Free Forum Powered by Nabble | Forum Help |