Hey,
I suppose it is grizzly-http-server 2.3.8. I use maven and using the jersey
bom v2.9. The dependency graph in my IDE shows 2.3.8 as the version.
Regards
Sathya
On Sun, Jun 1, 2014 at 9:50 AM, Oleksiy Stashok <oleksiy.stashok_at_oracle.com>
wrote:
> Hi guys,
>
> which Grizzly version are you using?
>
> Thanks.
>
> WBR,
> Alexey.
>
> On 31.05.14 08:27, Paul O'Fallon wrote:
>
> After your e-mail I tried the same thing in my code and you're right -- it
> always answers at the first level (/foo) and not at the defined point
> (/foo/bar). In fact it seems to ignore everything after the first path
> (/foo/bar/baz still answers at /foo). Unfortunately I don't know how to
> fix it, but I can confirm the same results...
>
> - Paul
>
>
> On Sat, May 31, 2014 at 8:24 AM, Sathyakumar <sathyakumar.s_at_gmail.com>
> wrote:
>
>> Am trying hard to do an SE deployment of a Jersey app on Grizzly http
>> server.
>> My RESTful services are available on a non-default context. Below is the
>> code I used
>>
>> URI uri = UriBuilder.fromUri("http://localhost/Services/webresources/
>> ").port(8080).build();
>> HttpServer server = GrizzlyHttpServerFactory.createHttpServer(uri, new
>> MyConfig());
>>
>> However non of the resources are accessible under context
>> "/Services/webservices" and are instead available under context
>> "/Services". I debugged the code a bit and the context path of the request
>> is always returned as "/Services" instead of "/Services/webresources". I
>> dont know what I'm doing wrong. Any pointer that will help me get going in
>> the right direction will help
>>
>
>
>