Saminda, Comments in line.....
On 2/26/07, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
Hi, > Basically, this means that there is *always* a registry from where items > > are looked up. There could be a remote registry, and you could define > some items on your local view of it - effectively overriding any > resources from it. It is also possible that you may not use a remote > registry - and thus define any resources locally. > > When a remote registry is defined, you *do not* have to define the > registry keys to Synapse again as before (using dynamic properties), > since Synapse would see all keys available in your remote registry by > default. Say your registry contains a key "reg_key_xslt1" which maps to > a XSLT, and you want to use this resource from a XSLT mediator. You just > have to state > > <xslt key="reg_key_xslt1"/> > > If a XSD you require is not available on your remote registry, you may > define it locally as follows, and use it: > > <definitions> > <registry-entry > key="local_key_xsd1" src="file:xsds/my_schema1.xsd"/> > </definitions> > > <validate> > <schema key="local_key_xsd1"/> > </validate> If the registry contains keys, then user dose not need to address them explicitly in the synapse.xml. They all be available automatically through registry definition right. Now if a given key is not available in you have to define them as <registry-entry/> @key and @src. Does registry-entry means, does this update the registry with the given source information apart from locally available.
No. These registry entries which are outside of the declaration of the remote registry are locall to the synapse enviorenment that is defined by the particular configuration. So if another instance or more pointing to this registry can use them.
Then U have to declare them in the remote registry. Shouldn't we be able to do the same for other Synapse entities like
<sequence/> as well. If a registry contains some default sequences such as default RM configuration sequence etc, would be able to get them directly from registry with a give key.
Yes. we are going to do that. In synapse.xml for configuring proxies or others , for elements, if the name
contains virtually multiple words, it has been written as <foo-bar/>. When it comes to attributes it's written as carMar. IMHO, if it can be given as <foo-bar car-mar="something"/> wouldn't this be easy to user to remember, Or <fooBar carMar="something"/>, rather mixing the way we write element and attribute names ?
+1 for this.... What is the standard way of doing things???? Thank you
Saminda > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org
Thanks, Ruwan. -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
