On 6/1/06, Rashmi Hunt <[EMAIL PROTECTED]> wrote:
Thanks for the quick response.
1) My loaded did register qualified name for the binding with the Stax
loader registry.
2) And my loaded class is MODULE scoped
I figured out what the problem is, which is not related to
code/implementation. It's eclipse....
<snip/>
When I add my new binding project as a project dependcy to my test module
project,
I don't see this this error anymore when I create a new TuscanyRuntime. I
think when
the new binding project is in test project's classpath, Tuscany runtime is
able to find the
system.fragment file and load the new binding accordningly... that's my
theory :-)
Yep - that's exactly what's (not) working.
This highlights one of the problems with "auto-discovery" of stuff -
i.e. when it's not discovered for some reason then failures often
manifest in different areas.
With the "composite" revisions to the spec, this kind of partial
composition is going to be replaced with some form of include
mechanism where the parts are explicitly included. That way to include
your new binding you would modify/replace the default system SCDL with
one that included your new one.
The exact form of this has not yet been specified but as an interim I
plan to support this in core2 using something like:
<component name="XXXBinding">
<implementation.composite name="XXXBinding" bundle="binding-xxx.jar"/>
</component>
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
