[
https://issues.apache.org/jira/browse/OLINGO-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896995#comment-13896995
]
Eugenio Lentini edited comment on OLINGO-153 at 2/10/14 8:59 PM:
-----------------------------------------------------------------
Hi Michael,
unfortunately because of a multi-module project and copyright issues I cannot
attach my pom but according to what I have seen in your pom is the same as mine
except for some proprietary artifacts which do not include any transitive
dependency on any version of {{javax.ws.rs}} (I have checked with {{mvn
dependency:tree}}).
Basically I have excluded the dependency, as you have done, from apache cxf and
olingo-core. One more thing, but I guess not important, I have even excluded
the dependency from {{org.apache.rampart:rampart-core:jar:1.6.1}} of
{{javax.ws.rs:jsr311-api:1.0}}.
Then I have just added the dependency on {{javax.ws.rs:jsr311-api:1.1.1}}. The
goal is to change Apache CXF with Jersey and {{javax.ws.rs:jsr311-api:1.1.1}}
for the time being, in the future we will update to
{{javax.ws.rs:javax.ws.rs-api:2.0}}.
As Sergey has said it seems a CXF bug, but quite strange beacuse I have already
tested a month ago against {{javax.ws.rs:jsr311-api:1.1.1}} and it was working
fine.
Thanks a lot for your help and attention.
Eugenio
was (Author: black@t):
Hi Michael,
unfortunately because of a multi-module project and copyright issues I cannot
attach my pom but according to what I have seen in your pom is the same as mine
except for some proprietary artifacts which do not include any transitive
dependency on any version of {{javax.ws.rs}} (I have checked with {{mvn
dependency:tree}}).
Basically I have excluded the dependency, as you have done, from apache cxf and
olingo-core. One more thing, but I guess not important, I have even excluded
the dependency from {{org.apache.rampart:rampart-core:jar:1.6.1}} of
{{javax.ws.rs:jsr311-api:1.0}}.
Then I have just added the dependency on {{javax.ws.rs:jsr311-api:1.1.1}}. The
goal is to change Apache CXF with Jersey and {{javax.ws.rs:jsr311-api:1.1.1}}
for the time being, in the future we will update to
{{javax.ws.rs:javax.ws.rs-api:2.0}}.
As Sergey has said it seems a CXF bug, but quite strange beacuse I have already
tested a month ago against {{javax.ws.rs:jsr311-api:1.1.1}} and it was working
fine.
> Dependency on javax.ws.rs 2.0 is back
> -------------------------------------
>
> Key: OLINGO-153
> URL: https://issues.apache.org/jira/browse/OLINGO-153
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Reporter: Eugenio Lentini
> Assignee: Michael Bolz
> Priority: Critical
> Attachments: mibo_fail_pom.xml
>
>
> Hi,
> I have set in the past the dependency on jsr311 version 1.0 but running jetty
> server I get a class not found exception due to
> java.lang.ClassNotFoundException: javax.ws.rs.InternalServerErrorException
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at
> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:421)
> at
> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:383)
> at
> org.apache.cxf.jaxrs.utils.ResourceUtils.createApplication(ResourceUtils.java:730)
> at
> org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createServerFromApplication(CXFNonSpringJaxrsServlet.java:435)
> at
> org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.init(CXFNonSpringJaxrsServlet.java:93)
> The issue is in a CXF class and according to the spec
> https://jax-rs-spec.java.net/nonav/2.0-SNAPSHOT/apidocs/javax/ws/rs/InternalServerErrorException.html
> that class has been added since version 2.0 of jax rs.
> Should I report the issue even on CXF bug track?
> Thanks a lot for the attention.
> Eugenio
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
