Kedar Mhaswade wrote:
> Frankly, what pluggability means for create-domain functionality is a
> tricky thing to figure out. This is mainly because asadmin is not a
> modular VM unlike server. Thus, it can't leverage the @Contract/_at_Service
> stuff and ask the various contributing modules to create their
> configuration.
That would be nice. Any @Service that is also @Configurable and implements e.g.
getConfigurableName() for the top-most name and create(), delete(), and
change(), and may be even list() methods will be able to handle its
configuration on its own...
Regards,
-marina
And remember, it is not just about domain.xml.
>
> Some work needs to go into this because it might entail defining
> an API for various modules to implement so that we can call various
> implementing modules to do their part of domain creation.
>
> I agree, either the extensibility or the infrastructure spec should
> describe this in detail.
>
> Vince -- sorry to be deferring answering your question. But this is
> something that needs some time. Are you interested in port allocation
> part of create-domain or something else as well?
>
> -Kedar
>
> Sreenivas Munnangi wrote:
>
>> We are still working on Configuration pluggability and the issue
>> raised by you seems related to this.
>>
>> Each module can bring its own configuration which will be persisted in
>> domain.xml. Coming to the specific issue pointed by you about port
>> numbers, we need some config. validation to make sure conflicts do not
>> occur and your input is valuable for this.
>>
>> thanks
>> sreeni
>>
>> Vince Kraemer wrote:
>>
>>> Hi,
>>>
>>> I am trying to find out how extensibility interacts with a domain
>>> that the user has 'created'... not domain1... in v3.
>>>
>>> Consider the following use-case:
>>>
>>> a user creates a domain that has a 'custom' portbase, with the web
>>> distribution.
>>>
>>> The user upgrades the distribution to handle things like ejb and
>>> stuff, that requires additional ports...
>>>
>>> It seems obvious that the user will want to be able to leverage those
>>> features in their domain... so...
>>>
>>> 1. How does the domain.xml file get updated?
>>> 2. If port values are assigned in the process of updating the
>>> domain.xml... what values are assigned to these new ports?
>>> Will they just be the 'default' ports... which may overlap with
>>> port values already assigned int the domain.xml... since the user is
>>> not using the default values?
>>> Will the selected ports be offset from some 'primary' port value
>>> that is already assigned in the domain.xml?
>>>
>>> I was hoping to see this discussed in one of the one-pagers... but I
>>> cannot find it. I looked in
>>> http://wiki.glassfish.java.net/Wiki.jsp?page=GFV3ExtensibilityOnePager
>>> and
>>> https://glassfish.dev.java.net/nonav/v3/admin/planning/V3Changes/V3_AdminCLI.html,
>>> but admit I might have missed the discussion of this class of
>>> problems in those documents.
>>>
>>> vbk
>>>
>>> ---------------------------------------------------------------------
>>> 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
>