alberto wrote:
> Thanks for your help.
>
> I am not trying with curl also because I don't know what it is ;), but
> the browser is performing a simple GET over the address, so why should
> work different with curl?
>
Not different, i recommend using it for debugging purposes as it can
print out all the HTTP headers etc i.e. you can know what is going on
directly without browser configurations like caching/redirection etc
getting in the way.
alberto also wrote:
> Sorry, it was my mistake with tomcat!
No problem!
> As you can see I am quite prone to
> write jsersey instead of jersey! ;)
>
Thats OK, i did not even notice :-)
> I have a quick question now. I see that if I map the servlet on "/*"
> jersey try to handle every resource also index.html causing a 404
> response. Is this ok? Shouldn't jersey leave other resources to original
> handlers (JSP servlet etc..)?
This is a good point. For a workaround try using "/" instead (that is
what i do for the Bookstore example, but it may not work for everything.
I have not fully resolved the rules for this. It may be that instead of
Jersey functionality being a servlet it should be a filter as i
understand it makes it easier to integrate with other resources.
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109