On Sep 6, 2006, at 3:51 PM, Raymond Feng wrote:
Hi,
I think I'm going to leave databinding-framework as an extension
for now. It won't impact the integration effort this stage. When
the code becomes more mature (in terms of test coverage and
functions), I'll merge it into the core/spi and the work should be
very trivial.
O.K let me know if I can help with anything.
Jim
Thanks,
Raymond
----- Original Message ----- From: "Jim Marino"
<[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, September 06, 2006 10:22 AM
Subject: Re: Should we merge the databinding-framework into spi/core?
If there are no external dependencies on databinding, my
preference would be for the extension pieces to be merged with
SPI and the impl to be placed in core under /services. Before
that happens, though, I'd also like to see a lot more test
coverage in place, particularly unit testing. Integration testing
could be done whenever we get to an integration build.
Jim
On Sep 6, 2006, at 10:13 AM, Raymond Feng wrote:
Hi,
I'm in the middle of integrating databinding framework with core/
spi and it's time to make a decision on the packaging.
There are two options for the databinding-framework.
1) Merge with core/spi: Move the interfaces/base classes into
spi and implementation into core.
2) Keep databinding-framework as an extension.
Individual databinding technology modules will stay as extensions.
Please let me know your opions.
Thanks,
Raymond
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
