Closed mmoayyed closed 11 years ago
I also have the following SSO report context file with the following:
<context:component-scan base-package="net.unicon.cas.addons.info"/>
<context:component-scan base-package="net.unicon.cas.addons.ticket"/>
<context:annotation-config/>
Looks like the dependency list needs to be augmented to restore the missing javax-ws
entry?
Yes, the SSO report is implemented as a Jersey (Jax-RS) REST resource, so these deps:
<exclusion>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-client</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-core</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-server</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-servlet</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jersey.contribs</groupId>
<artifactId>jersey-spring</artifactId>
</exclusion>
<exclusion>
<groupId>javax.ws.rs</groupId>
<artifactId>jsr311-api</artifactId>
</exclusion>
must not be excluded in order to use it.
I'll look into this more closely. I believe I had taken out the SSO report context file from the config and expected the setup to work after that, but something else was still dependent on the ws-rs stuff. I put the deps back in for the time being.
Turns out the issue is unrelated to cas-addons actually. Closing.
The cas-addons dependency is added into the file with the full list of exclusions: