> -----Original Message----- > From: Johan [mailto:[EMAIL PROTECTED] > > If you want keep things simple and clean I wouldn't go implementing > lifecyclesupport in the actions. Better is putting the businesslogic > inside Avalon and use the actions as a client of Avalon.
Hmm. Perhaps it would be enough just to get the ServiceManager reference in the ServletContext. This shouldn't be too hard. > IMHO I think Struts and Avalon are a very nice combination for anyone > who wants a good designed webapplication, but no J2EE app. It could be very nice. I agree. > But the servlet integration or PlugIn facility of struts isn't maybe the > best way to get a hold on your Container. You can also choose to make > your Avalon Container available thru JNDI. Struts can then get a handle > to the Container thru JNDI, but a Swing frontend can as well use the > businesslogic the same way as the Struts frontend. I guess you have a > lot of freedom in how to incorporate the two. The JNDI option is the one which is currently being explored, and obviously the one which provides the most flexibility. I was just curious how difficult it would be to integrate it more directly into struts and to see how much interest there might be in that approach. jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
