On Jan 29, 2007, at 9:37 AM, Jeremy Boynes wrote:
Re autowiring, I ran into a issue here trying to separate the Java
Class out of ServiceContract. There are still few places where we
assume that a ServiceContract has a corresponding Java interface -
I can deal with most of those but there are a lot of assumption in
the autowire implementation that this is there.
For now I plan to leave it there and just add the general
properties for class name and contribution to JavaServiceContract.
Will this refactor include changing autowire so that it is able to
work on the general ServiceContract rather than the Java-specific
interface type? If it does, then hopefully we can remove the Java-
specific bits from ServiceContract after.
Yes
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
