The point is not for you to use struts. The point is that struts employs a lot of things you say you want to learn about. Look at struts and you will see employed what you are tyring to understand, viz. how to initialize a servlet with web.xml at startup. If you think you can write a whole MVC as "no big stumbling block," and yet don't know how to initialize a servlet on the startup of the server with web.xml, I am confused. So, please accept my apologies once again.
At 08:10 AM 9/4/2002 -0700, you wrote: >Micael, > >You've mentioned Struts a couple of times and I admit I am curious. > >I did look into Struts but to be honost I wasn't all that impressed by what >(I think) I saw. It seemed like it was just offering a lot of lightweight >wrappers around the API. Case in point, the Cookie utility class didn't >appear to offer any additional functionality over the http.cookie class in >the JDK. It's connection pooling was even pretty rudamentary so I went >around that. I presume that its XML/XSL, and other such things would also >be rundamentary probably too. And actually, did I say a lot? I looked at >the API and I didnt think there was a lot there... > >All those things I'm saying wouldn't be bad per se, except that I don't want >to learn a whole new API to do basically what Java already does with it's >own standard API (again back to the wrapper thing). > >Granted the MVC pattern implementation is apparentlly very good but I'm not >seeing that as a huge stumbling block to write on my own. They also appear >to provide custom tags wrappers around their API so that you can keep your >code totally declarative (code based) at the JSP level. Ok, that would be >cool ... but again I just don't want to be realying on a non-standard API >still for standard functionality. I'll end up forgetting the JDK API in >lieu of Struts API. :( > >SOOOO, this is my initial impression of Struts. I dont know ... what do you >think? Am I totally off base with my concerns and/or assessment of the >package? If so, please let me know. I am open to being proven wrong here. >I've heard Struts is a great package ... its just the cost-benefit (time to >learn vs. gain in productivity) analysis doesn't seem to be pointing me in >that direction right now. :) > >-----Original Message----- >From: micael [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, September 03, 2002 12:36 PM >To: Tomcat Users List >Subject: RE: global.jsa > > >Why don't you look at a struts application? They exist, and all >applications with Tomcat do this. > >At 11:42 AM 9/3/2002 -0700, you wrote: > >Interesting. I was aware of the application scope option which is cool ... > >but not exactly what I was looking for. Running a servlet onStartup is an > >intriquing suggestion though. I didn't know you could do that....I think > >that's what I'm looking for! :) > > > >Cool...I'm going to read more about it. Do you know the syntax of the top > >of your head for specifying an onStartup servlet in the web.xml file? > > > >Thanks for your help. > > > >Neal > > > > > >-----Original Message----- > >From: Barney Hamish [mailto:[EMAIL PROTECTED]] > >Sent: Tuesday, September 03, 2002 2:14 AM > >To: 'Tomcat Users List' > >Subject: RE: global.jsa > > > > > >Why don't you just declare the object you want to use as having application > >scope? That way the first time you use it it will be initialized? > > > >Alternatively you can specify servlets that should be run on start-up in >the > >web.xml if you want some kind of java daemon running. > > > >Hamish > > > > > -----Original Message----- > > > From: neal [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, September 03, 2002 10:56 AM > > > To: Tomcat Users List > > > Subject: RE: global.jsa > > > > > > > > > Thanks. > > > > > > No global.jsa, eeh? > > > > > > The web.xml is a good way to go if you have flat variables > > > that you want > > > placed into the application object ... but can you instantiate objects > > > there? Can you specify scope of those objects or will it presume > > > application scope? > > > > > > THanks. > > > Neal > > > > > > > > > -----Original Message----- > > > From: Barney Hamish [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, September 03, 2002 1:30 AM > > > To: 'Tomcat Users List' > > > Subject: RE: global.jsa > > > > > > > > > You can use the WEB-INF/web.xml to similar effect or you can > > > also declare > > > objects to have application scope, then you have a global > > > object that you > > > can access anywhere. > > > Hamish > > > > > > > -----Original Message----- > > > > From: neal [mailto:[EMAIL PROTECTED]] > > > > Sent: Tuesday, September 03, 2002 10:15 AM > > > > To: Tomcat Users List > > > > Subject: global.jsa > > > > > > > > > > > > Is there such a thing as a global.jsa file in Tomcat? > > > > > > > > I first saw this concept (an idea taken from ASP's > > > > global.asa) implemented > > > > in JRUN. > > > > > > > > If there is a global.jsa, does anyone know of any docs on > > > > this? If not, is > > > > there an alternative? The reason I would want to use this is > > > > to instantiate, > > > > populate, and cache a few objects upon startup of the > > > application. If > > > > Tomcat does not provide a global.jsa...does anyone know how > > > > otherwise to > > > > achieve the goal? > > > > > > > > Thanks. > > > > Neal > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > > > <mailto:[EMAIL PROTECTED]> > > > > For additional commands, e-mail: > > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > > > >-- > >To unsubscribe, e-mail: > ><mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: > ><mailto:[EMAIL PROTECTED]> > > > > > >-- > >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
