Sorry for the confusion. I thought you were asking a more basic question.
Would it be possible to define a new element for the domain.xml, maybe
something that isn't under system-applications, that would have the
basic structure for the element in the system config module
(admin/config-api), with the intelligence there to detect whether metro
is installed and then to do the right thing only if it is? This is how
clustering works. The Cluster class that supports the <cluster> element
is shipped in all releases, but the code there is prepared to deal with
the case where the other cluster JAR files are not installed. This
allows a <cluster> element to be in the domain.xml at any time, even
though the cluster software isn't installed.
Tom
On 9/2/2010 6:37 AM, 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
>