Slashdot Mirror


Tomcat Install On OpenBSD

Dan writes "Adam Getchell has published instructions on installing Tomcat on OpenBSD in the form of install logs. The config is setup as non-root so that anyone can start/stop Tomcat. He has not tried loading any EJB's and is playing with Cocoon to make the setup work with XML publishing framework. Adam is looking for feedback relating to his setup."

4 of 11 comments (clear)

  1. EJB? by digerata · · Score: 2, Informative
    ...He has not tried loading any EJB's...

    Hope he is not dissapointed with failure. As far as I know, Tomcat is not an EJB container.

    --

    1;
    1. Re:EJB? by JediTrainer · · Score: 2, Informative

      You're absolutely correct. Tomcat is not (and will likely never be) an EJB container. It's a very nice Servlet container, though...

      However, once Tomcat's installed, it wouldn't be a big leap to then install JBoss to work in tandem with Tomcat, providing those missing EJB container services. It seems like a very nice package.

      --

      You can accomplish anything you set your mind to. The impossible just takes a little longer.
  2. Unix and the standard install by Anonymous Coward · · Score: 3, Insightful

    For all the talk of Unix being a developer's dreamland, it sure seems like getting applications deployed onto systems is a pain in the ass. It's just poke and test, poke and test, poke and test. If there was a standard installation method (none of this configure && make crap) that allowed users the ability of putting files exactly where they wanted them, you wouldn't see such problems where the install script magically chooses to shit all over the disk for you.

    It would also help alleviate the problem of incompatible code because everything would be separated nicely into packages instead of a gigantic tarball of who-knows-what cruft.

    There's a lot of good things about Unix. Portability and installation ain't it.

    1. Re:Unix and the standard install by Elwood+P+Dowd · · Score: 4, Interesting

      Boy, could I not disagree more.

      With something that does use the standard GNU build system, I can set it to install into ~/bin and ~/lib instead of /usr/bin and /usr/lib, or /usr/local/bin and /usr/local/lib.

      In fact, I can make ~groupname/bin and ~groupname/lib directories, so that everyone in a certain project will get access to the results.

      Sure, porting tomcat might have been a pain... and that pain might hilight weaknesses in the Unix design philosophy, but portability and installation are not those weaknesses. For many system administrators, portability and installation ease/flexibility are wonderful features of Unix that do not exist on Windows.

      --

      There are no trails. There are no trees out here.