Jan Luehe wrote:
> On 09/15/08 11:43 AM, Jeanfrancois Arcand wrote:
>
>> Salut,
>>
>> Kedar Mhaswade wrote:
>>
>>> I hope the name has no bearing here, but I am not sure. I should be able
>>> to name the JK connector as "foo", right JF?
>>
>>
>> We don't have any way to tell GF that a specific connector is mod_jk
>> enabled. Hence Amy cames with the idea (or Jan?) to have a special
>> name. For sure jdk-connector is not correct :-) It should be
>> jk-connector.
>>
>> Now using the name attribute might not be a good idea. I would instead
>> propose adding a property under <http-listener> with:
>>
>> <property name="jkSupport" value="true"/>
>>
>> so it follow our normal convention. Jan/Amy/Kedar, what do you think?
>
>
> Love the idea!
>
> As for the name of the property, I'd prefer something like "jkEnabled".
+1 we should have a uniform way to enable jk support to avoid confusion.
I assume
1. we want to change to jkEnabled from jk-connector for prelude.
2. we're keeping the v2 way (jvm-options
-Dcom.sun.enterprise.web.connector.enableJK=8009)
Correct?
Thanks,
Amy
>
> Thanks!
>
> Jan
>
>
>>
>> A+
>>
>> -- Jeanfrancois
>>
>>
>>>
>>> -Kedar
>>>
>>> Survivant 00 wrote:
>>>
>>>> note sure if I'm in the right mailing-list.
>>>>
>>>> I try the listener jk-mod for GF v3.. based on JF Arcand's blog,
>>>> but it doesn't work with b24. It's named jdk-connector not
>>>> jk-connector. Which one is the good name ?
>>>>
>>>> here the bug issue :
>>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=5975
>>>>
>>>>
>>>> thanks
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>
>