I figured this out. I was getting an odd error on a service init which wasn't showing in the stacktrace. I fixed that and the webservice loads up correctly right after deploy now.
Sorry for the thread traffic today on a non-issue.
- Damian
-----Original Message-----
From: Sobieralski, Damian Michael
Sent: Tuesday, August 05, 2014 3:51 PM
To: users_at_jersey.java.net
Subject: [Jersey] Re: javax.servlet.ServletException: A MultiException has 2 exceptions. They are:
Nevermind my never mind. This is still an issue.
I created a binder, extended resourceConfig and binded. After webapp deploy on first hit to a webservice I get those errors. On 2+ hits all works fine.
-----Original Message-----
From: Sobieralski, Damian Michael
Sent: Tuesday, August 05, 2014 3:10 PM
To: users_at_jersey.java.net
Subject: [Jersey] Re: javax.servlet.ServletException: A MultiException has 2 exceptions. They are:
Nevermind.
It seems a variation of this fixed my issue:
http://stackoverflow.com/questions/16216759/dependency-injection-with-jersey-2-0
-----Original Message-----
From: Sobieralski, Damian Michael
Sent: Tuesday, August 05, 2014 2:49 PM
To: users_at_jersey.java.net
Subject: [Jersey] Re: javax.servlet.ServletException: A MultiException has 2 exceptions. They are:
> But if I use a jersey client
Correction: Doesn't need to be a jersey client. ANY REST client. On first hit after deploy I get that error. On 2nd hit (and beyond) all works fine.
-----Original Message-----
From: Sobieralski, Damian Michael
Sent: Tuesday, August 05, 2014 2:47 PM
To: users_at_jersey.java.net
Subject: javax.servlet.ServletException: A MultiException has 2 exceptions. They are:
I am having an odd problem.
So here's the odd error. This is on the server end (Jersey 2.11). On webapp deploy and startup when I hit a webservice w/ a client I get this (in the server logs):
javax.servlet.ServletException: A MultiException has 2 exceptions. They are:
1. java.lang.StringIndexOutOfBoundsException: String index out of range: 0 2. java.lang.IllegalStateException: Unable to perform operation: create on org.mypackage.ws.jersey.myJerseyRestWebservice
But if I use a jersey client and if I hit the exact same service again all works fine (no new deploy just hit the same endpoint again). And it works fine until next new deploy.
Any ideas?
I'm still new to jersey so perhaps I am missing something I need to configure.
- Damian