Generating artifacts for the file based registry

Hi Pete You might forget, we provide a FileBase registry called   ‘org.wso2.esb.registry.ESBRegistry’. This functions same as URLRegistry (in synapse) and only store Meta data in the database. This was the registry in the pervious ESB releases where there is no WSO2Regirty at that time. You can use that as follow by just editing only synapse.xml Example: <registry provider="org.wso2.esb.registry.ESBRegistry">       <parameter name="root">file:repository/conf/sample/resources/</parameter>       <parameter name="cachableDuration">15000</parameter>    </registry> With this registry, admin console can be used to manage resources. For your options 1 and 2, I will try that and will also try to provide a solution. st1\:*{behavior:url(#ieooui) } Thanks Indika      

Hi Pete, Let me try to explain the 3 approaches that you are trying; 1) Point esb to a remote registry, then export from the registry. When you create an artifact in the esb console, you must take an extra step to "export" it to the remote registry. The user experience needs improvement >> What sort of an improvement do you suggest for this? (understatement). When using the "export" button, you don't know if it has already been exported, plus you need to choose a location in the remote registry (like Endpoints) and then re-type in the name of the resource. >> well it is not really the name of the resource but the key by which you refer to this resource which is different from the name of the resource (both key and the name can be the same as well) If you forget to export, then the configuration is lost when the esb is restarted. >> not really, you can persist the configuration to the disk by clicking on the save icon on the configuration tab. -artifacts in the esb, don't necessarily exist in the remote registry >> yes they can be in the local configuration as local entries --if you delete an artifact in the remote registry, it still exists in the local esb (where?) >> ESB caches the resources from the registry and keeps a copy in the memory when it is using a particular resource. So may be it is using the cached copy, but you can configure the cache timeout in the ESB console or notify a particular resource to clear its cache. -artifacts in the remote registry, aren't necessarily known by the esb >> yes, it is not a must --if you delete an artifact in the local registry, it still exists in the remote registry >> local registry deletion has nothing to do with the remote registry and we do not recommend to have resources with the same key in local registry as well as on the remote registry, though you can do that. --I added a new endpoint via the remote registry console, and now the esb integrated registry gives me an error "Couldn't get child elements from registry :: Error when fetching resource with key /Endpoints " >> Integrated registry supports only XML entries and may be you mistyped the XML configuration of a particular endpoint. 2) Point the remote registry to the esb registry derby instance. This setup works, but when I run the export sample, it fails. See this posting for the exception: http://wso2.org/forum/thread/4156#comment-6866 >> will get back to you on that thread. 3) Crafting all synapse artifacts by hand. >> This option will be easy once you are used to the synapse configuration language syntax, but not for a person who is starting with it. Thanks, Ruwan Linton

Thanks to both of you for your follow up. Indika, the ESBRegistry is exactly what I was looking for. Thanks! I hope that version of the esb registry will be maintained going forward even though it is "older". Ruwan, Kevin is looking more closely at the remote registry and esb and will post his comments. Obviously we are new to this product, and still finding our way through it.