On Aug 22, 2006, at 8:59 AM, Hawkins, Joel wrote:
Jim wrote:
In the case above, I thought ShipperReference was wiring out over the
binding and having the binding resolve the target through OSGi? If
that is the case, what may be happening is a bug I ran into last
night. Basically, the reference builder need to set a URI on the
Reference model object, otherwise the composite reference builder
assumes it is a composite reference. That should be fixed, or at
least an error thrown.
To see if this is your problem, can you attach the code you are using
to a JIRA and I'll take a look?
That's exactly the case. What code would you like? The entire OSGi
setup, the sample code minus the OSGi bits, or just the SCDL?
Just the SCDL will do. I can throw it into my test harness and see
what is happening.
I'm
assuming this would be repeatable using any binding for the
ShipperReference, since I really never even get to the OSGi binding
code
(if I remove the binding specification in the ShipperReference
entirely
I get the same error - BuilderConfigException("Target not found for
reference " + "shipper")).
Thanks,
Joel
The contents of this e-mail are intended for the named addressee
only. It contains information that may be confidential. Unless you
are the named addressee or an authorized designee, you may not copy
or use it, or disclose it to anyone else. If you received it in
error please notify us immediately and then destroy it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
