We just filed this
https://grizzly.dev.java.net/issues/show_bug.cgi?id=557 to make a little
more semantic sense. ThreadPool elements have to live somewhere under
NetworkConfig at a minimum for grizzly-config to be usable in grizzly
standalone.
Jerome Dochez wrote:
> I am a bit confused as well. I understand the ThreadPool configured
> interface went into the grizzly-config module, however I don't
> understand why there would be a reference from iiop-listeners to
> threadpools defined in network-listeners.
>
> jerome
>
> On Apr 22, 2009, at 1:37 PM, Justin Lee wrote:
>
>> No other questions/complaints? Can I commit this?
>>
>> Justin Lee wrote:
>>>
>>>
>>> Kedar Mhaswade wrote:
>>>>
>>>>
>>>> OK. Thanks.
>>>> So the plan is iiop-listeners stay wherever they are, but will
>>>> reference
>>>> thread-pools from under network-listeners?
>>> Correct.
>>>>
>>>> Does it make more sense then to make ORB initialize from
>>>> convenient network-listeners and deprecate the iiop-listener(s)
>>>> element(s)?
>>> I could go either way on this one. As I understand it, though, the
>>> ORB code needs a much different thread pool than, say, HTTP processing.
>>>>
>>>> I guess we will need a blanket compatibility waiver for affected
>>>> dotted names.
>>> There's a request for this in already, actually.
>>>>
>>>> -Kedar
>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Kedar
>>>>>>
>>>>>> Justin Lee wrote:
>>>>>>> Attached are the diffs for integrating the new version of
>>>>>>> grizzly-config that should hopefully fix the open issues against
>>>>>>> it. There is also a fix for a test that broke from the
>>>>>>> grizzly-config merge last week.
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>