Dear Pals, In my office, we have just finished a project with Java, Oracle, XML, XSLT, XSL-FO and some other technologies. We felt lack of a container in our project and in our next java project, we have decided to use an open source framework other EJB (the learning curve of EJB is not affordable by my company duirng projects). After having some searched on the web, we found Avalon a very good potential solution for us and today we found another one JGrinder. I am still downloading that. But now, need your advice. As a framework, Avalon has the better chance to be reacher --- as far my knowledge goes. But JGrinder may be slightly easier to adopt quickly, is it? Tell me the advantages and disadvantages of the both and if you have another one (other than EJB), be great to name it here. I am still new bie in making this decision, so...
I'm not familier with JGrinder, but it seems to be an Object persistance tool. Avalon the framework solves the problem of making your code modular (and some other stuff like configuration and logging and whatnot). There are, though, some pre-made components (or Blocks if you like) living in the sub-projects' CVS that solve many common problems (persistance being one of them). On the down side, most of the pre-made Blocks are not documented. I've been polluting the Avalon mailing lists recently (mostly the Phoenix subproject) and using it, so I can say first-hand that the Avalon developers know what they're doing. If you look up Pheonix in the apache bugzilla, you'll find nothing but a ton of enhancement requests submitted by the developers. Anyway, JGrinder and Avalon are made to solve different problems. So...you can use both of them together. You might want to do something like integrate a JDO implementation with Avalon so you aren't tied to a single persistance product.
We must storm this mad man's lab and destroy his villanous bomb! Are you with me tiny ad?
Free, earth friendly heat - from the CodeRanch trailboss