-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support @Repeatable in @PayloadRoot and @SoapAction [SWS-877] #952
Comments
Gyula Szalai commented Because of this mod, our Java6 based project won't run with spring-ws 2.2.1. Is it intentional? |
Arjen Poutsma commented Gyula Szalai no, it is not. What is the error/stacktrace you are getting? |
Gyula Szalai commented
|
Gyula Szalai commented It's a Spring Boot application, that runs on AIX 5.3 and IBM Java6. |
Arjen Poutsma commented I am not convinced that this is a Spring-WS bug, as our use of This should work under JDK 6 or 7, since annotations that cannot be found in the JDK should simply be ignored. It seems more likely that this is some sort of annotation-introspection bug that occurs in IBM JDKs. I will ask around and investigate further. |
Gyula Szalai commented OK, thank you in advance. |
Juergen Hoeller commented Indeed, Spring Web Services uses the same approach as some of the annotations in Spring Framework 4.x itself. Let's rather revisit Spring's core For better or for worse, IBM's JDK 6 is pretty special there, having peculiar rules with respect to nested type resolution within method bodies as well. Note that as of JDK 7, IBM's JDKs are derived from OpenJDK and therefore naturally more in line with Oracle's established JDK behavior. If you have any chance to do so, you could run this on IBM JDK 7, just to see whether the problem goes away... Actually, it might even help to upgrade to the latest IBM JDK 6 version, assuming you might be using an older variant there? Juergen |
Gyula Szalai commented Thanks Jürgen! Actually we used a very-very old IBM JDK6 version. Unfortunately this server is stuck Shall I file an SPR issue or it can be closed? |
Juergen Hoeller commented Alright, I'm glad to hear that it works for you now :-) No need to create an SPR issue for this one then. I'm nevertheless going to revisit our annotation introspection exception handling but will do so under a different umbrella. Juergen |
Arjen Poutsma opened SWS-877* and commented
Support the JDK 8
@Repeatable
annotation in the@SoapAction
and@PayloadRoot
annotations.Issue Links:
Referenced from: commits fe4747d
The text was updated successfully, but these errors were encountered: