We are evaluating James for use in a large enterprise app so that it may supply mailing services to it.
Some developer have raised the issue that James is based on End Of Line frameworks such as Avalon. Furthermore, the website for James says they will continue using it by forking it or something. The natural question to ask would be: Why do you want to fork and continue development on a framework that is dead and buried by the Apache Foundation and its own creators? We naturally have considered the fact that switching this on the implementation might be very complicated, but some reasons other than it being hard for keeping Avalon around would be great. Disclaimer: This is a honest attempt to get information, not a jab at anyone. Thanks in advance for your help. -- Juan Carlos Murillo <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
