Servlet Mapping Strategy w/ user-specific URLs

I would like to have a url structure of the form: myplace.com/user/xxx/resource/yyy where user and resource are handled by individual servlets. I would like users to have the ability to POST there username/password to /user and have it respond with their personal url, e.g.:

Re: Servlet Mapping Strategy w/ user-specific URLs

So you're talking about using the sorts of Filters available as of the Servlet 2.3 spec? That actually sounds promising, I'll take a look at it. One thing that bothers me about my current plan though is that I feel like I'm not making use of some of the functionality potentially provided by

Re: Servlet Mapping Strategy w/ user-specific URLs

At 01:48 PM 1/8/2003, you wrote: So you're talking about using the sorts of Filters available as of the Servlet 2.3 spec? That actually sounds promising, I'll take a look at it. Yep. Okay, one question about this: in the Filter, I'd parse the url and determine which servlet should be the

Re: Servlet Mapping Strategy w/ user-specific URLs

Depends upon your point of view. Mine is different from those I've seen in reply to your inquiry so far. If I can do something declaratively in Apache, I do it. If I am going to write code, I put do it in Tomcat. Apache is a world-class web server. Tomcat is an application (Servlet/JSP)

Authentication and Filters

I am using a Filter to do some URL rewriting. In the filter, I accept a url like: /user/x/resource/y [1] and convert it to /resource/y?user=x [2] In the Filter, I create a RequestDispatcher using the new url, and then call forward(). The servlet setup to handle /resource is

Re: Authentication and Filters

A key rule to remember is that security constraints are applied *only* on the original URL requested by the client -- not on RequestDispatcher calls. I would bet you probably have /resource/* protected, but you'll likely want to protect /user/* as well. Thanks, this is a great help. You're

Re: Authentication and Filters

A key rule to remember is that security constraints are applied *only* on the original URL requested by the client -- not on RequestDispatcher calls. On last thing, is this a part of the servlet spec, or is it left unstated and this is just Tomcat's particular implementation? Thanks -- To

Windows Service

Sorry about this question that has apparently been asked and answered innumerable times, but: I'd like to run Tomcat as a Windows 2000 service. Searching, I see there is a utility jk_nt_service.exe that is available, but I can't seem to locate the version that is appropriate for Tomcat 4.0.x.

Re: Windows Service

There is an option in the Tomcat installer to install Tomcat as a service on Windows. Jim Ah yes, thanks. I see now that the lastest 4.1 has it as part of the install. I'm just going to upgrade my installation. Sorry! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional

getCanonicalFile()

I just upgraded from Tomcat 4.0 to the latest Tomcat 4.1 and noticed something very strange that I was hoping someone could give me some insight on: Everyplace that I use to get a FileInputStream by simply saying: File file = new File(filename); InputStream istream = new

Re: getCanonicalFile()

If you need to reference files in some arbitrary directory someplace, you should pass the pathname of that directory to your servlet as an init parameter, and then use that path to construct an absolute path to the file you want. In my particular case the files I'm attempting to open are

[Fatal Error] :-1:-1: Premature end of file.

I am getting a Fatal Error when POSTing, but not PUTing, some XML data to my servlet. In the Command Window the following is shown: [Fatal Error] :-1:-1: Premature end of file. I also print out the Exception that I caught: Error: org.xml.sax.SAXParseException: Premature end of file.

Re: [Fatal Error] :-1:-1: Premature end of file.

Yikes, Almost the exact second I hit send on my last message, I realized that the issue is probably the Content-Type, and in fact, changing the request header to Content-Type:text/xml caused the issue with POST to go away completely and my app functions fine. My only remaining question is:

Admin Mbeans from Application in Tomcat 4.1.31?

Is it possible to access the management MBeans from a standard deployed application in Tomcat 4.1.31? I can't figure out if it is possible to reference the MBeanServer from an application. Any pointers or code examples would be greatly apprectiated. I would like to be able to show the state