Concerning TOMEE-130 - Would it make sense to decouple the UI from the remaining webapp logic? For example it could just emit JSON data accesible through a REST API. That way we could have a 2nd webapp that only does the UI or have an OpenSocial container such as Apache Shinding that would consume the JSON data from the 1t webapp and afterwards renders the UI using its own rendering engine. We could even have KDE or Win 7 widgets accesing the 1st webapp and thus TomEE instances could be managed from the desktop...
Cheers Daniel On Tue, Jan 31, 2012 at 1:41 AM, David Blevins <david.blev...@visi.com> wrote: > Thought these might be some good discussion points/improvements for TomEE. > > - TOMEE-130: Improve openejb webapp console to match current site look and > feel > - TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE > - TOMEE-132: Make it easier to use command line deployer in TomEE > - TOMEE-133: TomEE logs/openejb.log should be merged with the rest of Tomcat > logging > - TOMEE-134: Rename openejb.war to tomee.war > > General idea is to blend in a bit more and modernize the naming. > > Thoughts? > > > -David >
