The default node would look like below. It is at the same level as then
'configs' element and it does have default values as below. The
corresponding server element that would refer to it is also included below.
If we don't have this default node element then we need to figure out
what we are going to do with the 'node-ref' attribute (it should point
to an existing 'node' element) in 'server' element. We can either force
the user to create a node element (bothersome for developers that will
be running everything on their local machines) or we can create it for
them (won't happen for m2). Currently 'node-agent-ref' is being used
in several places to figure out which host to connect to and run
commands but we want to transition away from that in m3.
proposed default node element:
<nodes>
<node name="localhost" nodehost="localhost"
nodehome=${com.sun.aas.installRoot}>
</node>
<nodes>
<server node-agent-ref="bear.sfbay.sun.com" name="instance1"
node-ref="localhost" config-ref="instance1-config">
Carla
Jerome Dochez wrote:
> On 6/14/10 10:56 PM, Carla Mott wrote:
>> Hi,
>>
>> I'd like to add a default node element to domain.xml much like there
>> is a default-config element. For m2 we want to move towards
>> requiring a node-ref (new) attribute to server element. This new
>> node-ref attribute will point to a node element which information
>> about the host where the instance is running and in the case of a
>> developer it is localhost. I don't want to have to required a
>> developer to create a node with localhost info when he creates an
>> instance. It would be nice to have a default node that we refer to
>> when creating an instance if noderef option is not specified.
>>
>> What is the process for adding to domain.xml? Do I just add the node
>> element to domain.xml file in packager/nucleus-base?
>>
>>
>> Carla
> no, I don't think this is the right approach.
>
> so this default node would be located where ?
> does it also has default attributes ?