Jim Marino wrote:
Yes the commons option would have been ideal but unfortunately, It's
more than just reflection and utility classes. It's also injection
classes related to wiring and component-handling classes which depend
on SPI. Having gone over the options, merging the two seems to be the
lesser of two evils, the other approach being a lot of duplicate code.
Jim
Can you tell me which injection and wiring classes and help me
understand why they're creating such coupling? Maybe some of them could
be turned into useful SPIs and the others could go into common? Thanks.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
