When this problem manifests, the plugin throws an exceptionally irrelevant exception that provides very little information. Below is what the exception looks like...
So from that you'd think it's a compiler issue, but the problem actually lies in your own code. Specifically it is the use of unchecked generics that causes it.
To demonstrate, lets assume I have a class called TestClass that has a method called testMethod(). This method expects a List<T> as the input parameter. There is no other code in the method because its not necessary to show this problem.
So far so good. There is nothing extraordinary in the code above (except that it doesn't do anything useful). Now lets say I wanted to make use of this class and its sole method somewhere in my web service code. Lets also say that I was lazy and didn't declare my List properly so my code ends up with an unchecked generic like this...
The above will cause JWSC to fail. For some reason because testMethod() expects a List<T> and it gets a List instead, JWSC goes whacko.
Now if I declare my list variable with a qualified generic type like below, everything works as expected, no complaints from JWSC!
The second version of the code is of course better in many ways, so I wouldn't necessarily call this a JWSC bug, however the exception that is being thrown could have been better or perhaps it should have been a warning saying that there is an unchecked type being used!