Personally after being a windows developer for 7 some years I like the down and dirty approach. You get a good handle of what's going on behind the scenes since you are behind the scenes.
Nothing worse than clicking a button and trying to explain to someone what you did to get the error message - a picture is worth a thousand words...much easier to copy and paste a server.xml text file :) Actually intensified my efforts to get into programming and out of tech support when I saw windows, was extremely glad I had made that move once users had the power to customize their own toolbars!!! My 2 cents. Charles -----Original Message----- From: A mailing list for discussion about Sun Microsystem's Java Servlet API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Galbreath Sent: Wednesday, November 14, 2001 6:15 PM To: [EMAIL PROTECTED] Subject: Re: Disappointed You guys remember when you started down this trail? Maxim is simply expressing his frustration with the technology. It is complex and it remains in a defining phase. Soon (me hopes!) there will be GUI wizards to guide developers through the complex maze of configuring and setting up web applications. For now, it's like the early days of the Internet (1980s) when you had to know Telnet and Unix just to navigate. Today's developers never had that experience and are used to Mac and Windoze GUIs that will do everything at the press of a button. Hopefully, all the XML configs will be hidden soon so new developers will become productive a lot sooner. There is no doubt that being in the Java world today involves mastering many skills just to get an app deployed. The depth of knowledge required at present is daunting; it has become a barrier to new entries into the dev world. These guys come here in hopes of finding existing expertise that will give them some clue. Anybody remember the "elite" days of the underground BBS's in the '80's? You would ask a question about how to do something and get booted from the BBS because you were "not worthy." As for Maxim, have some patience and do some research. No one is slighting you here; if you did not get an answer it is most likely because no one had the time to respond (we have other responsibilities to home and work, you know). Cheers! Mark ----- Original Message ----- From: "Milt Epstein" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 14, 2001 10:18 AM Subject: Re: Disappointed > On Wed, 14 Nov 2001, Maxim Patramanskij wrote: > > > Hello anyone, > > who is taking part in this mailing list. > > > > What I'm really do not understand is why no one of my messages was no > > once replied by nobody! > > Was those questions posted in non-understandable nor correct manner? > > Or my postings was ignored because of other reason and if so, why > > nobody told me, what was wrong? > > If I've broke some rules, moderators should made me notes, don't you? > > If I was asking something obvious, why no one told me, where I can > > find an answers? > > Don't take it so personally. There are a lot of reasons your post > might not have gotten any response. You can post the same thing one > week and not get any response and the next week get a bunch of > responses. Of course, there are certain things you can do to increase > your chances of getting responses (e.g. be concise, be specific, be > on-topic, provide details, make it clear you've tried to figure out > the problem yourself, etc.). And as someone else suggested, you might > have better luck on the tomcat-users list, it's higher volume than > this one and focussed only on tomcat. > > In any case, in answer to your question: I believe that you can't > expect too much customization from the automatically generated > configuration file, the consensus recommendation is to take the file > that's generated, copy and modify it according to your specific needs, > and use that modified file. I don't think there's any way around this > currently. > > > > Anyway, I will post here AGAIN, some of them, that still aren't clear > > for me: > > > > > My questions concerns to Tomcat 3.2.x servlet container, especially to > > > its opportunity to create automatic configuration file for Apache, > > > named mod_jk.conf-auto. > > > As well as web application is known by Tomcat(either by putting it to > > > webapps folder or editing server.xml manually), it automatically > > > appends application's parameters(servlet and .jsp mounting rules, alias > > > and so on) to the mentioned file immedeately after restart. > > > Where can I customize Tomcat for creating: > > > > > > JkMount /context/* ajp12 > > > > > > instead of creating separate rules for .jsp's and servlet's: > > > > > > JkMount /context/servlet/* ajp12 > > > JkMount /context/*.jsp ajp12 > > > > Milt Epstein > Research Programmer > Software/Systems Development Group > Computing and Communications Services Office (CCSO) > University of Illinois at Urbana-Champaign (UIUC) > [EMAIL PROTECTED] > > ___________________________________________________________________________ > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff SERVLET-INTEREST". > > Archives: http://archives.java.sun.com/archives/servlet-interest.html > Resources: http://java.sun.com/products/servlet/external-resources.html > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html > > ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
