tags:

views:

22

answers:

1
Q: 

Jersey @Provider not recognized

We are using a Jersey JAXBContext resolver implementation using @Provider. It appears that Jersey is not recognizing the @Provider class - the code is never being executed. Is there a reason that Jersey/JBoss isn't properly identifying the class?

A: 

This answered the question. It was connected to Spring config - not related to JBoss.

Marcus  2010-09-24 17:00:05

related questions

How to get the status of a JBOSS server
JNDI without a J2EE Container (with JNP? Maybe some other provider?)
Consuming web services with jboss
JAVA Swing client, Data Access to Remote Database; Ibatis
Upgrade to Quartz 1.6 on JBoss 4.2.x
Problems with shutting down JBoss in Eclipse if I change JNDI port
.NET enterprise application platform (same as JBoss to Java)
What is the best way to configure iPlanet/Sun ONE be the HTTP/HTTPS front end to a JBoss/Tomcat application?
Problem using JConsole remotely with JBoss 4.2.2 with app that uses JWS
Is there any way to have the JBoss connection pool reconnect to Oracle when connections go bad?
Help configuring JNDI with embedded JBoss in Tomcat 5.5.x
Spring JTA TransactionManager config: Supporting both Tomcat and JBoss
How can I best connect Seam and GWT in a stateful web application?
Best practices for configuring Apache / Tomcat
What are the best books for JBoss?
JBoss 4.23 and EJB 2 support
How to rewrite an URL on a JBoss server?
Bypass GeneratedValue in Hibernate
Two Phase Commit/Shared Transaction
Faces Servlet threw exception java.lang.StackOverflowError
Modify an xml files in a jar file with Java
using DBMS_APPLICATION_INFO with Jboss
Reconnecting JMS listener to JBossMQ
Accessing Datasource from Outside A Web Container (through JNDI)
Resolving Session Fixation in JBoss