Re: SynapseObject - Reminder...

Tue, 28 Feb 2006 20:45:38 -0800

Hi...
 
1) If main processor comes across an xml fragment of type SynapseObject in synapse.xml it needs to call a processor          
    (SynapseObjectProcessor maybe) to convert the xml fragment into a SynapseObject instance.
 
2) But we need a place holder for this instance, now the question is where to put it for further reference.
From a scoping perspective, we can scope it at two levels
a) specific to a mediator
If it is specific to a mediator then we should extend the current mediator to have a member variable of type hashtable and appropriate getters and setters. We can  push the SynapseObject in the hashtable, this also allows the user to use any kind of object if in case they choose not to you SynapseObject.
b) global.
For global usages we can put synapseObject instances in the SynapseEnvironment which can be used by any part of synapse.   
 
The getters and setters might look up the hierarchy... Mediator's hashtable, then environment...
 
~Vikas.
----- Original Message -----
Sent: Tuesday, February 28, 2006 11:20 AM
Subject: Re: SynapseObject - Reminder...

Hi,

Please be kind enough clarify the following small questions.

1. As every element <foo/> in the synapse.xml maps to a FooMediator, how does <foo/> gets the info out of <synapseobject/>. ex: does it as follows?
<foo>
    <synapseobject name="xx">
            <synapseobject xx="xx"/> [1..n]
     </synapseobject>
</foo>

2. Does every mediator get a reference to <synapseobject/> or a selected few such as <servicemediator/> or <classmediator/> get the reference to <synapseobject/>.
3. Synapse now has a <define name="some_name"/> mediator and this mediator can reference this by <refdefine ref="some_name"/>
Is it possible to have a scenario as follows

<synapse xmlns="http://ws.apache.org/ns/synapse">

   <servicemediator service="service1">
        <refdefine ref="customer_properties"/>
   </service>

   <classmeditator class="com.service.Service2>
         <refdefine ref="customer_properties"/>
   </classmediator>

   <servicemediator service="service3">
        <synapseobject>
              <attribute name="url" type="STRING">http://%3c</attribute>
              <synapseobject name="consumern">
                  <attribute name="identifier" type="STRING">someID</attribute>
                  <attribute name="priority" type="INTEGER">2</attribute>
            </synapseobject>
        </synapseobject>
   </servicemediator>

    <define name="customer_properties">
         <!-- attribute to service 1-->
         <synapseobject name="service1">
              <attribute name="url" type="STRING">http://%3c</attribute>
              <synapseobject name="consumer0">
                  <attribute name="identifier" type="STRING">someID</attribute>
                  <attribute name="priority" type="INTEGER">2</attribute>
            </synapseobject>
           <synapseobject name="consumer1">
                <attribute name="identifier" type="STRING">someID</attribute>
                <attribute name="priority" type="INTEGER">6</attribute>
            </synapseobject>
       </synapseobject>
       <!-- attribute to service 2-->
      <synapseobject name="service2">
              <attribute name="url" type="STRING">http://%3c</attribute>
              <synapseobject name="consumer0">
                  <attribute name="identifier" type="STRING">someID</attribute>
                  <attribute name="priority" type="INTEGER">2</attribute>
            </synapseobject>
           <synapseobject name="consumer1">
                <attribute name="identifier" type="STRING">someID</attribute>
                <attribute name="priority" type="INTEGER">6</attribute>
            </synapseobject>
       </synapseobject>
    </define>
</synapse>

4. As we agreed on, <synapseobject/> will be an extension, and what would be the way of integrating this in to Synapse at run time.

Thank you

Saminda

On 3/27/06, Vikas <[EMAIL PROTECTED]> wrote:
Hi,
 
This is regarding the Synapse object proposed by me and Soumadeep...
 
For convenience I am putting below the links for reference:
and the source code has been available in the Scratch
 
I feel that it an effective utility and have made use of it in a all the mediators that I would like to commit . It sure has made handling mediator's config data easier..
Would be checking in the cleaned up code for SynapseObject as an extension...Which I guess is OK.
 
Please let me know if anyone has any concerns about it??
 
~Vikas

Reply via email to