Re: [ptp-dev] Updated Resource Manager Schema

[Greg Watson <g.watson@xxxxxxxxxxxx>]

Al,

No, nothing that complicated. I think you've clarified how it works for me. 

However, I have another question. The "on-start-up" command will also generate a (large) list of arbitrary attributes and default values. These attributes must then be used to create an attribute list with the default values in editable fields. How would this be achieved?

Greg

On Jan 19, 2011, at 8:50 AM, Albert L. Rossi wrote:

> Hi Greg,
> 
> To answer your second question, yes the order of the commands is the order of execution.  If you think an explicit order attribute is better, we can add that.
> 
> I'm not sure I follow the first part, though.  Are you saying that the way we obtain version information could vary depending on the version itself, so that a single tokenization may not work?  In that is the case, then what we really need is for the command sequence to be generalized so that we can express both <and> and <or>; and startup would then try command A, and if that fails, command B, etc; each of those having the appropriate parser to find the version information from the command output.
> 
> Once the version information is set (giving a value to the ${version} property), then subsequent command definitions can then proceed to do as I have currently provided for:
> 
> <command>
>   <arg>
>   ...
>   <stream-parser stdout="true">${foo-parser-v_${version}}</stream-parser>
> </command>
> 
> assuming that the configuration file has furnished a definition of that parser.
> 
> Al
> 
> 
> ----- Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
>> Al,
>> 
>> I assume the "on-start-up" command is there (for example) to enable obtaining the version of the installed system. While this seems good, there also needs to be some way to select the parser based on this version. In other words, there needs to be a regex for each parser that is matched against the output of the "on-start-up" command that selects which parser is used for output from subsequent commands.
>> 
>> Also, for commands that have minOcurrs="0", this implies that there can be multiple commands of this type, right? If so, I think there needs to be some ordering of the command execution (or do you assume it's the order the commands appear in the configuration file?)
>> 
>> Greg
>> 
>> On Jan 16, 2011, at 6:09 PM, Albert L. Rossi wrote:
>> 
>>> Greg, Randy, Dave,
>>> 
>>> I have posted a draft of the (control part) of the ResourceManager.xsd (http://wiki.eclipse.org/PTP/designs/resource_manager_xsd); please take a look when you get a chance.
>>> 
>>> This is a valid XSD which will generate the necessary Java Classes using the JAXB compiler.  I have not yet decided whether it will be simpler to use JAXB runtime to build the actual instance objects from valid instances of the XML, or whether we just might want to parse it in using a DOM parser and then pull from it as necessary.  
>>> 
>>> Let me know about the holes here, or what you don't think is going to work.  Undoubtedly we will need to iterate a few times.
>>> 
>>> Thanks, Al
>>> 
>>> _______________________________________________
>>> ptp-dev mailing list
>>> ptp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>> 
>> _______________________________________________
>> ptp-dev mailing list
>> ptp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>> 
> 
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev