Thanks Jeremy, Basically, what I need is something like WSDL4J , maybe a "SCDL4J", which contains the WSDL object model and a reader/writer. Tuscany already has the SCDL object model, also the loaders, I was able to manually register loaders (subclass of StAXElementLoader or AbstractLoader , itself a subclass of StAXElementLoader ) to StAXLoaderRegistry, and StAXLoaderRegistry can load SCDL and all the information loadable from the loaders.
Now I need to find a way NOT to do the registration manually. The reason we need this feature is: before a sca pacakge is installed into Tuscany, I may want to expose some of the SCDL for user to do last minute updates, or some definition may trigger some other processing, e.g. some binding extensions need J2EE side of code gen.. This "SCDL4J" feature can enable us do it. So my question to your suggestion to start a runtime is: 1. is the runtime a runtimeContext? 2. how I can get the registry from the runtime? is the registry StAXLoaderRegistry? I tried to see from the class reference of StAXLoaderRegistry and StAXLoaderRegistryImpl to find clue on how to get it, was not able too.. All the current test cases on loader are registering loader manually. Appreciate your help. Yang On 8/4/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On Aug 4, 2006, at 10:33 AM, Yang Lei wrote: > Hello, > > With M1 Driver, I can load a sca.module by creating a > StAXLoaderRegistry and > registering loaders into it. I wonder if Tuscany has a better way > for me to > get a StAXLoaderRegistry (or some other instance) fully loaded > with all the > loaders (Tuscany basics or other extensions ) so I can load any > SCDL w/o > worrying of what are the current supported loaders... > > The purpose of loading the SCDL is to read the defintion to start some > processing w/o creating the moduleContext and start it. Yang, could you give a little more information on what you are trying to do? The loader infrastructure is designed to support deployment scenarios where we need to create the runtime artifacts needed to host the user's application. This needs a lot of additional infrastructure to capture information not contained in the SCDL (for example, introspecting Java classes, loading external files, ...). To do all that you really need the runtime running (as it has the mechanisms for loading extensions, introspection, resolving external artifacts and so on). From the running runtime you can access the registry as a service. On the other hand, if you are in a tooling environment and are just editing the SCDL, you may not need all that. If you're looking to slurp in XML, edit it and write it out again, some form of XML editor (e.g. vi) or modeler (e.g. EMF) may be more appropriate. -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
