Ok, so to try to answer my own question, it looks like the implementation loader can use a ComponentTypeDocumentProcessor (passing itself in the constructor) and then calling read with the URL of the component type side file. Does this sound ok?
On 4/10/07, Ignacio Silva-Lepe <[EMAIL PROTECTED]> wrote:
How is this supposed to work now? Previously, an implementation loader had the option of asking the loader registry to load a component type from a side file, and then it was able to downcast the returned component type to an extension-specific component type. Since a component type's file is a separate stream, how does an implementation loader (as a StAXArtifactProcessor that it is) kick off a separate stream read? Is there a pattern for this, and is there an exisiting component type reader that can be invoked? Or is this all left as an exercise to the developer? Or perhaps this is coming but not complete yet? Thanks
