> On Sep 23, 2007, at 11:29 PM, Dario Laverde wrote: > >> Dain, >> >> It's not clear how to invoke/test beans from the web admin the way >> I recall doing so >> in 0.9.2 unless I'm missing something obvious - otherwise, great >> job in bringing >> back that feature! > > I never used it in 0.9.2, so I have no basis for comparison. Can you > describe what you find strange?
Well I'm getting NULL when I click on the beans listed in the JNDI browser (e.g. for the beans from the servlet-samples.war) and from the invoke menu you can only go back to the JNDI browser, and from EJB viewer there's not a way to specify one. Unless I'm wrong to assume that the web admin works with the Tomcat plugin... >> So what's left, besides a how to on avoiding the OpenEJBListener >> for per-webapp >> embedding? ;-) > > The basics are all working good and I think it is ready for 3.0- > beta-1. As for 3.0 final Tomcat integration, I'd like to: > > o integrate security > o replace OpenEJB jndi impl with Tomcat impl > o change naming code to not replace the Tomcat enc builder but to > supplement it > o add ear support > > The first two are easy, but the last two will be challenging. I'd recommend adding to the top of the list the ability to bundle Open-EJB with your webapp (similar to Gernonimo's embeddable container). Is it just a classloader/path issue to move the listener to the web app's WEB-INF/web.xml as well as the loader and all the dependencies to the web app's WEB-INF/lib folder or is it much more than that? thanks Dain for your hard work, let me know where I can help, -Dario > -dain > >
