Hi,
> Well, the comment suggests that the "grizzly-config configuration"
> will obviate this method but it doesn't really elaborate. I'm still
> trying to grok this code so I'm not entirely sure how grizzly-config
> addresses the needs met by this method.
As I understand correctly we don't create NetworkProxy if jkEnabled is
true. When it's true - web container should use it's own transport
mechanisms inherited from Tomcat.
Can you pls. remind me what we decided to do with jkEnabled attribute,
do we support it in grizzly config?
Basically I think, what was meant by comment, is that once we will
have grizzly-config - we don't need to check jkEnabled property, but
just create NetworkProxy.
WBR,
Alexey.
>
>
> Jeanfrancois Arcand wrote:
>> Salut,
>>
>> Justin Lee wrote:
>>> In this method I found this comment:
>>> // Do not create listener when mod_ajp/jk is enabled. This
>>> // should never happens one the grizzly-config configuration
>>> // will be used.
>>>
>>> Does this mean that I can remove this method then? It seems to be
>>> used only internally by the configuration code anyway...
>>
>> Remove the implementation? Can you elaborate a little? This method
>> is required IMO, but I haven't followed the grizzly glue code
>> closely so I might be wrong.
>>
>> A+
>>
>> - jeanfrancois
>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>