On Oct 21, 2009, at 10:37 AM, Sahoo wrote:
> Not every property is a VM property. Some can still be set in a
> running VM. e.g., -DANTLR_USE_DIRECT_CLASS_LOADING=true.
actually this should work today already. is it really not working ?
> Same will hold good if we want to move OSGi confguration information
> to domain.xml.
>
the problem is that reading domain.xml represents starting a fair
number of bundles (all config-api related modules) so starting those
before OSGi kicks in seems unrealistic, certainly at this point.
> Sahoo
>
> Jerome Dochez wrote:
>> it's not like you will be able to set the VM properties on the
>> already running vm, which is why start-domain is reading it.
>> I guess I am failing to understand why you would want to have out
>> bootstrap code parse the domain.xml when doing java -jar ?
>>
>>
>> On Oct 21, 2009, at 10:13 AM, Sahoo wrote:
>>
>>> Currently asadmin start-domain parses domain.xml, but if server is
>>> started via java -jar, it is not parsed by our bootstrap code.
>>> Why? We can put some check to avoid double parsing. Any comments?
>>>
>>> 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
>