Comments (3)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 DougBreaux commented Permalink

<p>For whatever it's worth, it appears the described mechanism to use Spring to control and inject the Resource instances may have been a fluke.</p> <p>It is no longer working under WebSphere 8, reporting the following error:</p> <p>org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'winkInternalRegistryPostProcessor' defined in class path resource [META-INF/server/wink-core-context.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: org.apache.wink.server.internal.registry.ResourceRegistry</p> <p>This despite the fact that class does exist in one of the WebSphere-provided jar files, /usr/IBM/WebSphere/AppServer/plugins/</p> <p>I'm told that none of the jars in the plugins directories should be accessible directly to applications, and the fact that this works in WebSphere 6.1 is unintentional.</p> <p>So back to the drawing board for Spring DI with my Resources.</p>

2 Partyk1d24 commented Permalink

Do you have to use Wink for every Jax-RS implementation running on WebSphere?

3 Partyk1d24 commented Permalink

Actually I think I answered my own question with a yes... If you get some time can you try to help at the StackOverflow Post I made ...