> I don't know if I can take much more of Avalon. I've lost so much > interest in working on James because of the problems that arise from > using Avalon, and am nearing my last straw this afternoon. > > The latest problem with our use of Avalon is that if you have any open > connections when you try to stop the JVM, it hangs and has to be > forcibly stopped.
That has been the case for a while > I thought the whole reason behind migrating to Avalon > was so that we didn't have to deal with underlying threading, > configuration, object pooling, database sources, connection handling, > logging, and other server related issues. Unfortunately, none of the > features are implemented that wonderfully, the platform continually > moves from one pre-alpha release to another, there are regular huge > arguments on the dev mailing list about what latest pre-pre-alpha > component should be added next to the already uncertain platform, and > meanwhile the James project is stuck working again and again on stuff > that was already working before we ported to Avalon years ago. > > Sorry, I'm just really really tired of this stuff. Since there aren't > any real official releases of Avalon, should we just do another > snapshot? Or maybe just branch the code, import it into James so we can > gain control over our project again? How much code would we have to import, a lot right..? I share your concerns, but I wonder if there's another way. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
