[Vcb-framework] RE: configuration files

[Hovhannes A. <ha...@br...>]

1. re name and method name - we may want to show pin with name different
than method name. It is not only for overloading but mostly for better
naming on the diagram (e.g. we can select shorter name for pin).

2. you misunderstood me. Here is the example for inout pin (I make it
sample):

<inoutpin id="1" name="setup" out_id="51" out_name="responce">
   <parameter name="url" type="java.lang.String" />
   <parameter name="param2" type="java.lang.String" />
</inoutpin>

because it doesnt have many parameters and we can get the type by analyzing
the method we just need to assing second id and name for the same method

3. firing will be used in device config and not in part config. We will
discuss that later.

Hovhannes

-----Original Message-----
From: arto [mailto:art...@ed...]
Sent: Saturday, September 20, 2003 1:44 PM
To: Hov...@ly...
Cc: Vcb...@li...
Subject: Re: configuration files


Here is my ideas



<part>

    to have attributes name and classname is right and even essential

    although it could have 'description' atribut or tag

<inpin>

    "id" and "name" are essential and is used now in configuration

    I gess "methodname" can be used in case of
    overloaded methods for mapping if so then could be if not then don't
know why we need it
        we may also need "fire" atribute which will tell VCB framework to
fire this inpin at load time,
        because for now this desision is made analysing "parameter"'s
atributes


<inout
    you didn't show how we use it in the part configuration. let me gess
possible variants

<inoutpin id="1" name="setup" >
    <parameter name="url" type="java.lang.String" />
    <parameter name="url" type="java.lang.String" />

    <outpin id="51" name="response" >
        <parameter type="java.lang.String" />
    </outpin>
</inoutpin>
here we have inoutpin like inpin which has outpin inside and id of inoutpin
is the id of inpin
OR we may develop inpin tag so that it may have one outpin inside like:

<inpin id="1" name="setup" >
    <parameter name="url" type="java.lang.String" />
    <parameter name="url" type="java.lang.String" />

    <outpin id="51" name="response" >
        <parameter type="java.lang.String" />
    </outpin>
</inpin>
Here inpin sereves as inoutpin
OR

<inoutpin>
    <inpin id="1" name="setup" >
        <parameter name="url" type="java.lang.String" />

  <parameter name="url" type="java.lang.String" />

</inpin>

    <outpin id="51" name="response" >
        <parameter type="java.lang.String" />
    </outpin>
</inoutpin>
here we have inoutpin tag but as far we don't need
inoutpin id and it is used for visually combining particular in and out pins
as related ones
OR just
<inpin id="1" name="setup" >
    <parameter name="url" type="java.lang.String" />
    <parameter name="url" type="java.lang.String" />
</inpin>
<outpin id="51" name="response" >
    <parameter type="java.lang.String" />
</outpin>
having instead of inout pin separate in and out pins

why we need "out_id" & "out_name" as "inoutpin" attributes and how they will
be used is unclear to me

<outpin structure is the same as for <inpin


<parameter
    type - parameter type required and (used now)
    name - (optional) name of parameter explaining its meaning (used now)

       there is also "default_value" - which could be renamed as just
"value" and is used as initializing value for firing pin at load time.




Artavazd.





----- Original Message -----
From: Hov...@ly...
To: art...@ed...
Sent: Wednesday, August 20, 2003 12:24 PM
Subject: FW: configuration files



-----Original Message-----
From: Avoyan, Hovhannes, Lycos Armenia
Sent: Wednesday, August 20, 2003 11:12 AM
To: 'Vcb...@li...'
Subject: configuration files


Lets discuss configuration files in more details. It will be VCB language so
lets polish it.

So far we have part and device configuration files. For now lets focus on
parts. We have something like this|:



<part name="Database" classname="org.vcb.parts.database">

<terminals>

   <inpin id="1" name="start" >

   </inpin>

   <inpin id="2" name="stop" >

   </inpin>

   <inpin id="1" name="setup" >

      <parameter name="url" type="java.lang.String" />

      <parameter name="url" type="java.lang.String" />

   </inpin>

   <inpin id="3" name="request" >

       <parameter type="java.lang.String" />

   </inpin>

   <outpin id="51" name="response" >

       <parameter type="java.lang.String" />

  </outpin>



</terminals>

</part>

lets discuss attributes:

<part

    name - is short name to be shown on the diagram, could be optional
    sourcename - path to the implementation class


<inpin

    id - unique id for this part
    name - name of the pin to be shown on the diagram
    methodname - name of the method in the class (optional - if skipped then
name used)

<inout

   in addtion to inpin attributes
        out_id - id for outpin
        out_name - name of outpin

<parameter
    type - parameter type
    name - (optional) name of parameter explaining its meaning


Comments?
Hovhannes