Hi, Marek
> In June you wrote: "In v3, we no longer autodeploy and start system
> applications by default as part of the server start up (for
> performance reason). Things are done on demand."
>
> In retrospect, I might have misinterpreted this. I thought that if I
> register something as a system app, it will be "automagically" loaded
> lazily with the first request. Is that a correct assumtion or not?
No, it will not be loaded automatically. You have to code the logic to
have your system application loaded on demand.
For example, I think the loading of the timer service system application
is triggered by the loading of the first user application which uses
timer, and the loading of the MEJB system application is triggered by
the first look up on the MEJB.
> P.S. You can take it offline if you want, but I don't mind CCing dev
> mailing list as this conversation might be useful for other people
> too. I have tried to search the web before I wrote to the
> dev_at_glassfish alias, but I could not find any relevant information on
> this topic.
>
Yes, that's fine. We can keep the discussions on the dev alias.
Thanks,
- Hong
>
> On 2.9.2010, at 16:30, Hong Zhang wrote:
>
>> Hi, Marek
>> The system applications are handled differently in v3 compared to
>> v2 (the system application loading is no longer driven by the
>> system-applications element). Most of the system applications are
>> loaded on demand and are not even registered in the domain.xml.
>> Back in June, we had some discussions on how to support WS-TX
>> services application and I thought we agreed we would use the same
>> approach as the other system applications, load it on demand and not
>> register in the domain.xml. Can you give some details of how this
>> system application is currently handled (we can take this
>> conversation offline)?
>>
>> Thanks,
>>
>> - Hong
>>
>> Potociar Marek wrote:
>>>
>>> On 1.9.2010, at 19:39, Marina Vatkina wrote:
>>>
>>>> Do we still have <system-applications>?
>>>
>>> Yes, we do, AFAIK :)
>>>>
>>>> thanks,
>>>> -marina
>>>>
>>>> Tom Mueller wrote:
>>>>> The default domain.xml is here:
>>>>> packager/nucleus-base/lib/templates/domain.xml
>>>>>
>>>>> Just edit it and submit the change.
>>>>> Tom
>>>
>>> The problem with that approach (which I have already tried) is that
>>> this template is a common one for all GF distributions - even for
>>> those that does not include Metro.
>>>
>>> Marek
>>>
>>>>>
>>>>>
>>>>> On 9/1/2010 9:33 AM, Potociar Marek wrote:
>>>>>> Hello,
>>>>>> I am working on a "distribution-fragment" module that integrates
>>>>>> Metro WS-TX services web application into GF v3.1. As the last
>>>>>> step I need to add a new entry into the default GF 3.1 domain XML
>>>>>> under <system-applications> to register the wstx-services web app
>>>>>> as a system application in the default GF domain. How can I do that?
>>>>>>
>>>>>> Many thanks,
>>>>>> Marek
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> 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
>>
>