look into the TC7 code and see what I'm up against.
On Wed, Dec 15, 2010 at 11:58 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Gary,
>
> On 12/15/2010 11:40 AM, Gary Lawrence Murphy wrote:
>
Yeah, that's what I thought as well, moments after asking ;)
On Wed, Dec 15, 2010 at 12:03 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> most user agents aren't going to send the anchor to the server because
> it's not relevant.
>
>
--
*Have Blog, Will Travel: blog.teledyn.com
well, first I'll have to completely digest the spec before I could answer
this and ok, I guess we can throw MacOS in on the blame ;)
as a total aside that may work for me, in the URL spec cited above, they
used the notation of #extra-material -- what is the java method that returns
that extra mate
, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Gary,
>
> On 12/14/2010 5:56 PM, Gary Lawrence Murphy wrote:
> > oh, and I did try /test.jsp/* even though needing to explicitly match
> every
> > js
On Wed, Dec 15, 2010 at 11:29 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
>
> A high-volume real-time environment where on-the-fly JSP compilation is
> allowed and ad-hoc insertion of new dynamic content is allowed? Sounds
> like madness.
>
yes it is. such is the real world.
Thanks so much for that snippet; I notice in there no mention of filename
extensions but instead they talk of parsing the string form and give no
special meaning to the dot.
It is a difficult question hard to answer in an email without a great deal
of study, but to be naive and bold about it, what
built under the surface of the request, I think it should just be
/a/path/on/the/web and not a?subject=path&relation=on&article=the&object=web
:)
but yeah, I should take that up with them.
On Wed, Dec 15, 2010 at 9:33 AM, Mark Thomas wrote:
> On 15/12/2010 14:03, Gary Lawrence Murph
On Wed, Dec 15, 2010 at 4:54 AM, Mark Thomas wrote:
> Go read the spec. The JSP Servlet is mapped *based on file extension* not
> path.
heh, how very quaint. Where did they get this idea? from MSDOS? Oh never
mind. I don't think I want to know, and I suppose I just should be happy
the names
e)
On Tue, Dec 14, 2010 at 7:30 PM, Mark Thomas wrote:
> On 15/12/2010 00:00, Mark Thomas wrote:
>
>> On 14/12/2010 22:54, Gary Lawrence Murphy wrote:
>>
>>> On Tue, Dec 14, 2010 at 4:35 PM, Christopher Schultz<
>>> ch...@christopherschultz.net> wrote:
>
On Tue, Dec 14, 2010 at 7:00 PM, Mark Thomas wrote:
>
>
>>> Actually, this makes sense to me: the default mapping for the JSP
>>> servlet is "*.jsp". Your path doesn't end in .jsp, and therefore does
>>> not match the url-pattern.
>>>
>>> this is the crux of the problem, and the showstopper preven
oh, and I did try /test.jsp/* even though needing to explicitly match every
jsp in the project would be prohibitively inflexible, but there again, it
produced a parsing error and the webapp would not load.
On Tue, Dec 14, 2010 at 4:35 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
>
> > however when called with http://localhost:8080/test.jsp/this it fails as
> a
> > 404 not found
>
> Actually, this makes sense to me: the default mapping for the JSP
> servlet is "*.jsp". Your path doe
I am using Tomcat 6.0.20-2ubuntu2.2 on an AWS-hosted 64-bit Ubuntu 9.10
running on Java SE Runtime Environment (build 1.6.0_15-b03) and I am having
difficulty emulating getPathInfo() behaviour that works in other servlet
containers (jetty and resin)
I have a JSP file under ROOT:
<%...@page langua
13 matches
Mail list logo
