Hi Robert, what you mean with ugly hack ? Could you eleborate what you think needs to get cleanup ? I'm currently trying to dig into the IMAP code but it seemed quite complex atm ;)
At the moment I'm even not 100% sure if we not should just use spring beans to configure the Torque and OpenJPA. Maybe we could just write an custom Property replacer BeanPostProcessor which will set the right values in spring-beans.xml depending on the values of james-config.xml. So the "end-user" will still only have one place to configure stuff... Thoughts ? Norman 2010/1/7 Robert Burrell Donkin <[email protected]>: > On Wed, Jan 6, 2010 at 10:09 PM, Norman Maurer <[email protected]> wrote: >> Hi all (Robert ;)), >> >> what is the status of JPAMailbox and JCRMailbox in IMAP-Trunk ? How >> stable is it ? what needs to get done to complete it ? > > depends :-) > > the functional tests suite is reasonably comprehensive so that's the > best way to find out how complete the each mailbox implementation is > > my installation uses torque and i don't have the time to create > conversion scripts so i don't know how a loaded instance will perform > >> I think with the spring deployment in james server trunk it would be really >> easy to use one of these too.. > > the interface that used avalon is in the wrong place: in james rather > than IMAP. the adaption code is a ugly hack. if james now runs on > spring then the right way to perform the integration would by cleaning > up the remaining code (so it relies only on an annotation enabled > mailet container) and moving it into IMAP as spring and sieve modules. > > - robert > > --------------------------------------------------------------------- > 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]
