From: Tomas G. <to...@pr...> - 2007-02-09 13:48:38
|
Hi Thomas, Actually we have begun to think about this, as in considering what the future would look like. I was also angry about how hard it is to make ejb work in a nice way when working with serveral different app-servers. I hope that spring is easier for that? We don't have experience with spring ourselves yet, have only read about it a lot but not done any practical work. I think that the session beans is not so hard to get rid of, it's not such a huge service interface. The entity beans, converting them into hibernate/jdo, I see as the more difficult part, with mappings for different databases etc. I don't think the project is too complex, especially if you concentrate on the EJBs, but then again I may not be the right person to ask, I'm a bit home-blind if I can call it that :-) EJBCA have a pretty good amount of JUnit tests that test the services. These should be adapted to a spring implementation and should make things easier to work with and verify the functionality. The conslusion is that we are very positive. I would like to hear a little bit about if you think my expectations would be met. Especially regarding multiple application servers (jboss, weblogic, glassfish etc) and various databases (mysql, postgres, oracle, ...). Cheers, Tomas thomas moerman skrev: > I would like to have your opinion on this. For a developer not familiar with > EJBCA, but experienced in Spring development, how much effort would it take > to re-implement the EJBCA core module? (Just getting rid of EJB, but keeping > all functionality, and keeping it open source of course) Would this be > feasible in any way or is the project too complex to understand in a > (relatively) short period of time? I understand that Spring support is not > (yet) a part of the EJBCA roadmap. Any thoughts, comments, remarks? Are > there other people/developers that would be interested in such a project? |