Hi JDice,
Sorry for such late response.
Please look at Deployer and FromURIDeployer, both have deploy methods that
accept as first parameter GrizzlyWebServer.
So in both cases deployer doesn't encapsulate GWS.
For embedding WarDeployer you should use it directly and not rely on
GrizzlyWebServerDeployer.
I'm preparing talk for Devoxx about it, so will publish something in next
days.
Basic concept is following:
Create GWS, create Deployer, create Deployable, Deployer.deploy(GWS,
Deployable) and GWS.start()
HTH,
Hubert.
On Fri, Nov 13, 2009 at 7:06 PM, JDice <rolls.royal25_at_gmail.com> wrote:
>
> Grizzly Deployer encapsulates the GrizzlyWebServer, it it not possible to
> configure GrizzlyServer with different parameters and also add any dynamic
> adapters. This would help if we use Deployer in emebbed mode along with
> application. Is there any plan to support that?
> --
> View this message in context:
> http://old.nabble.com/Expose-GrizzlyWebServer-from-the-Deployer-tp26340810p26340810.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>