DJ Gregor wrote: > >> Now since we have Jetty built-in and enabled by default, should we stop >> distributing the non-Jetty webapp in $OPENNMS_HOME/webapps/opennms as a >> part of >> the base distribution? If people want to install it, let them download a >> separate package. This could also let us remove the (now confusing) >> support >> for installing the webapp into Tocmat from the installer. > > I notice this every now and then, so I thought I'd open it up as a bug > and bring it up here for discussion. What do people think about no > longer distributing the non-Jetty webapp with the base OpenNMS > distribution? >
I try to stay as close as possible to the stock rpm-packaged setup so if I needed tomcat on the same box I'd probably just run a separate instance on a different port anyway. However, I did run into this error: http://confluence.atlassian.com/display/DOC/Known+Issues+for+Jetty in the admin/manage-unmanage interfaces form and haven't found the right place to change the limit. -- Les Mikesell [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
