[
https://issues.apache.org/jira/browse/OLINGO-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015389#comment-14015389
]
Eugenio Lentini commented on OLINGO-298:
----------------------------------------
Hi Michael,
thanks really a lot for your investigation, basically the issue "the
Application is a class and not an interface." I have discovered was due to a
bug in apache Wink used by WebSphere, I have updated WAS to 8.5.5.2 and the
issue disappeared.
You are right, yesterday I have checked again the specification and there was
not the limitation on the Application, I was looking at the version 1.0 sorry
for my mistake.
I have put in place and already tested what have you suggested and it works
quite well except for a possible bug I have found in the servlet about the
redirect. For that I have open the issue OLINGO-307 where I describe the
problem and my temporary solution.
Thanks a lot for the attention and the time you have spent.
Eugenio
> Incompatibility with jsr311
> ---------------------------
>
> Key: OLINGO-298
> URL: https://issues.apache.org/jira/browse/OLINGO-298
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 1.2.0
> Reporter: Eugenio Lentini
> Assignee: Michael Bolz
> Priority: Blocker
> Fix For: V2 1.3.0
>
>
> Hi,
> I have tried to deploy a web application with an OData web service based on
> Olingo on IBM Websphere version 8.5.5 and I have got an exception due to an
> incompatible use of @Contex annotation with jsr311 specification
> org.apache.wink.server.internal.application.ApplicationProcessor
> processClasses Une exception s'est produite lors du traitement de la classe
> org.apache.olingo.odata2.core.rest.ODataExceptionMapperImpl. Classe ignorée.
> java.lang.IllegalArgumentException: javax.ws.rs.core.Application is not an
> interface
> Basically you are using in the class ODataExceptionMapperImpl.java the
> annotation in this way
> @Context
> Application app;
> but the javax.ws.rs.core.Application is not allowed as context type according
> to the specification jsr311 but it is allow in jsr339.
> Could you please have a look?
> Eugenio
--
This message was sent by Atlassian JIRA
(v6.2#6252)