Some product I previously worked on has such registry, furthermore, it loads resources on demand instead of loading everything at beginning to improve performance, not every execution path needs *all* resources after all.
The way it works is 1. client queries the registry with some criterias such as Symbol Space (type vs. message vs. interface/portType ...), NameSpace and symbol name 2. the registry locates corresponding resources (resource indexing and caching are also done for future queries) 3. the registry loads the resources and returns the result(s) meeting the query (symbol indexing and caching are also done for future queries) 4. another query involves cached resource 5. the registry reloads *if* the resource has been updated In a word, the registry automatically locates, loads and refreshes resources on demand. It makes simplest client Programming Model and loosely couples query, locating, loading and refreshing. The refreshing helps a lot in authoring/debuging environments where resources may be updated from time to time. The locating, loading and update checking are all extensible. If any one is interested in such service, I sure can contribute. On 8/22/06, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi, I would suggest that we define a system service to provide the artifact resolving strategy. Then we can supply a default implementation, for example, resolve the wsdlLocation based on classpath. The embedded can choose to replace it with its own more sophisticated resolver (for exmaple, using META-INF/wsdl, scanning directory, or querying a WSDL repository). Thanks, Raymond ----- Original Message ----- From: "ant elder" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, August 22, 2006 7:34 AM Subject: Auto discovering WSDL > In a C++ thread [1] Jean-Sebastien talked about having WSDL files > automatically picked up by the C++ runtime instead of having to specify a > wsdlLocation attribute somewhere in the SCDL. I'd really like the Java SCA > runtime to also do this, do people agree or anyone have any concerns with > that? > > Something like having a specific folder like META-INF/wsdl and in there > any > resources ending with .wsdl get automatically loaded into the WSDL > registry. And I guess this could be implemented with a Builder that gets > run when a composite is loaded. > > Any comments or suggestions? > > ...ant > > [1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg06221.htm > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Yang ZHONG
