David, *; first off, thanks a bunch for your explanations on that, they surely made a few things clearer to me. :)
Am Wed, 26 Mar 2008 15:04:42 -0700 schrieb David Jencks <[EMAIL PROTECTED]>: > [2] ought to be able to deploy to remote servers with no problem.. > That said I haven't tried it. If it doesn't work it's probably a > very simple fix. Basically you just need to specify where the > remote server is. Hmmm, I will have a closer look at it then and see how far this will take me. :) [...] > With this point of view you would either assemble an app server > containing your application(s) or construct assembly instructions and > ship these to the remote servers and then start the preconfigured > servers with your application already installed. This is an interesting idea. Actually, I can't say I do or don't like it as I simply have to get acquainted to it after all, given that indeed it seems to introduce a whole new philosophy in developing and deploying Java EE applications, more than just slightly differing from what one is used to by now. :) > I'm curious about what kind of remote management you expect to have > for the remote servers. To be a little more verbose on that: So far, we are using a bunch of applications distributed around in our network running in several tomcat containers, and I found this solution to be quite difficult to deal with if a bigger bunch of people (also including some who are less experienced and/or less interested) is supposed to take care of that structure. Most notably, it is difficult to explain - how to get some options of applications deployed to these containers configured at runtime, - how to use server logs to tell what is goin' on inside these containers at the moment, - how to deal with reloading / stopping apps if desired. So far, the same time we look at geronimo, we are into playing around with glassfish which seems to do better about these things for a simple reason: It provides a fairly sophisticated management interface to deal with all these issues in an easy way. Given that, and assuming to replace an existing, distributed environment by one "huge" (indeed monolithic it seems) Java EE container, there seems to be quite a benefit compared to our given situation, plus the chance to throw in things like EJB, JMS, ... easily to our Spring based applications. But the idea of the Java EE server being a standalone, well-administered runtime to just dump applications to and be reasonably sure they will start out is a tempting thing. From that point of view, I have indeed get acquainted to the idea of, say, building "my own app server distribution" by assembling an application server containing just my application. But maybe indeed it's just about getting used to it. At least, is there a way of running geronimo 2.x as a "traditional" application server (standalone installation on some dedicated host ready to recieve apps) as well? Anyway, thanks again for your input on that, best regards. Kristian -- Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/ jab: [EMAIL PROTECTED] * icq: 48874445 * fon: ++49 176 2447 2771 "One dreaming alone, it will be only a dream; many dreaming together is the beginning of a new reality." (Hundertwasser)
