>
> it shouldn't be hard - you can give it one more try (try build/test that
> helloworld sample and see how are things done there).. or, if you want/may,
> you can post here some simplified project which represents issue you are
> facing and we should be able to find where the problem is..
>
I've played around a bit with the Helloworld sample, changed from JAR to WAR
but when I when I change jersey-grizzly to jersey-server (I want a REST
service hosted by an existing container, not an embedded Grizzly), the tests
fail... even if I add jersey-grizzly again under the test scope.
If I add jersey-test-framework-grizzly as test dependency to my own project,
I keep running into "Could not find artifact
org.glassfish:javax.servlet:jar:3.0-b66" (Also get it as a warning:
[WARNING] The POM for org.glassfish:javax.servlet:jar:3.0-b66 is missing, no
dependency information available). I've extracted the essential parts of my
POM and put it here:
http://xml.pastebin.com/AChR4ukv
> These errors were introduced recently, we changed this behavior; Jersey
> used to inject nulls, but it lead to even worse errors, so currently we emit
> a error like this, which forces developer to fix it early..
>
Fair enough, I've updated the source to reflect those changes and it seems
to work! :)
well, it is not that hard! Or it definitely shouldn't be. You might be
> encountering some problems when migrating from older versions, but we have
> plenty of updated samples, so you should be able to find example for almost
> everything you want to do. But nobody/nothing is perfect, so if you have
> some concrete ideas for improvements, post them here or file new RFE on
> JIRA.
>
Yeah but problem is, there aren't enough samples to show every possible
combination - my frustrations likely has more to do with Maven than Jersey,
as there are a lot of ways to cut a POM cake. Thanks for the support, I'm
looking forward to diving into actual development with Jersey again - I
remember falling in love with it last time.
Kind regards,
Casper