FWIW, similar unification strategy was requested in issue 8584
<
https://glassfish.dev.java.net/issues/show_bug.cgi?id=8584>
So, please update this issue with any new developments in this area.
Thanks,
Snjezana
Kedar Mhaswade wrote:
>
>
> Justin Lee wrote:
>
>> I wasn't aware of that directory to be honest.
>
>
> Me too. What is this folder for? If it is for autodeploying OSGi bundles
> could we reuse the existing autodeploy folder instead?
<
https://glassfish.dev.java.net/issues/show_bug.cgi?id=8584>
>>
>> Sahoo wrote:
>>
>>> Justin Lee wrote:
>>>
>>>> (Apparently new commands aren't recognized without a restart
>>>> despite all the osgi goodness involved.)
>>>
>>> Have you tried copying your jar to domain1/autodeploy-bundles/, a
>>> directory which is watched for bundle additions/updations/deletions.
>>> If it still does not work, convince admin team to detect commands at
>>> runtime instead of requiring a server restart.
>>
>
> Can you elaborate on what this means?
> AFAIK, command is looked up from habitat every time it's invoked on the
> command line. At least this is how it was and I guess it worked
> dynamically.
>
> Are we supposed to do something else to make commands available
> dynamically?
>
>>>
>>> Thanks,
>>> Sahoo
>>>
>>> ---------------------------------------------------------------------
>>> 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
>