Hey thanks, Stefano. My code was a few weeks behind the "current". I'm happy to see the use of javamail 1.4.
For the last few weeks I have been using some of my time to replace the Avalon IOC with the Spring framework, hoping that some of my team developers who used to feel alienated by Avalon will feel right at home and start to develop on top of James. It has not been as smooth as I'd hoped, because the code also uses quite bit of cornerstone packages, which also depend on Avalon IOC and the XML configuration format. Right now I'm not ready to remove the dependency on cornerstone yet, due to time constraint. IMHO, the sooner we remove Avalon from James, the sooner we'll see more people start developing with James. Ciao, Bing On 5/14/06, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
What do you intend with "current James code" ? Our trunk has been refactored to use the javax.mail.util.SharedByteArrayInputStream and now we depend on Javamail 1.4. Stefano Bing Ran wrote: > I recently have noticed that current James code uses the above Sun > internal class in a few places, such as MimeMessageWrapper, > AbstractFileRepository. This makes James tightly bound with javamail > 1.3.3. Javamail 1.4 removes this this class thus breaks the build. > > Is ther a special reason that James needs to use this class? > > Thanks for any insight. > > Bing --------------------------------------------------------------------- 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]
