Checking it in sounds good, when ever you're ready, and I can do what you suggest and for now locally change things so that its used. But right the databinding code in the core/spi doesn't work anyway does it? Maybe the post processors are still running but they're not doing anything, so we could just take that out of the system scdl for now and then we should be able to remove all the old code.
...ant On 3/20/07, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi, Ant. I'm doing the databinding integration locally. To avoid destablization of the current core and achieve better modularity, I created a module "tuscany-core-databinding" to hold all the integration code which hooks the databinding framework to the wiring fabric. Then I could remove all the databinding-related stuff from the current "spi" and "core". I'm not sure what's the best way to share the work with you. I can check in the "tuscany-core-databinding" module but you'll have to remove the databinding packages from "core" and "spi" (maybe a patch will help). Any better and simpler way? Thanks, Raymond ----- Original Message ----- From: "ant elder" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, March 20, 2007 6:27 AM Subject: databinding in trunk > Trying to get the Axis2 and e4x databindings working again in trunk but > building the databinding framework module I get some test failures due to > missing methods when running with mvn but they all work in eclipse. It > looks > like there's a conflict due to some of the classes being duplicated in the > SPI databinding package and in the databinding-framework module which also > includes that package. Should this be working right now? Could I remove > the > classes from the SPI module? > > ...ant > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
