For the service layer, just use plain Java interfaces/objects, you can expose these for your web services very easily using Glue or Axis (would highly recommend Glue). The Spring framework (www.springframework.org) has very nice Hibernate support for easily using sessions and transactions. It provides some other stuff, such as a web framework, but it's mostly a la carte, you can use the Hibernate support without using the rest of it.
Rob ---- On Tue, 29 Jul 2003, Butt, Dudley ([EMAIL PROTECTED]) wrote: > This sounds like just what i need, I was just thinking of putting in EJB because i thought it was the > right way to go, but i can see that EJB's are > fast becoming the dinosaurs of J2EE. > I have just a few questions relating not using EJB's as a service layer. Later on we will want to > implement Web Services, my design now has to cater > for that. Any suggestions? > Also, I've looked at the xPetstore using WW and Hibernate,and i see there is cool transaction > handling..as below.. > It just seems to me that there's a lot of duplicate code around starting Hibernate Sessions etc, I'm > just really wanting to know if the xpetstore is a > good place to base a project on, if its optimal enuf. i'd like to use it as the basic format of my > new project. > Also, usually session EJB would be used for all your business logic etc, where will that go now, > without an EJB session/service layer? > ========================================================= > ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
