[
https://issues.apache.org/jira/browse/WINK-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528769#comment-13528769
]
Hudson commented on WINK-375:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #492 (See
[https://builds.apache.org/job/Wink-Trunk-JDK1.5/492/])
WINK-375 - Applying patch from Reto Bachmann-Gmür to re-register previously
unregistered service in a OSGi environment (Revision 1420013)
Result = FAILURE
lresende :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1420013
Files :
*
/incubator/wink/trunk/wink-osgi/src/main/java/org/apache/wink/osgi/WinkRequestProcessor.java
> wink-osgi reregistering previously unregistered service
> -------------------------------------------------------
>
> Key: WINK-375
> URL: https://issues.apache.org/jira/browse/WINK-375
> Project: Wink
> Issue Type: Bug
> Reporter: Reto Bachmann-Gmür
> Fix For: 1.3
>
> Attachments: WINK-375.patch
>
>
> reregistering a service that was unregistered before may cause the following
> warning and fail:
> 2012-12-07 10:26:00,062 [FelixStartLevel] WARN [FelixStartLevel]
> (ApplicationValidator.java\:85) - The class XX was already added to the
> JAX-RS runtime. The runtime is ignoring this value. Check that this class
> was not returned in the javax.ws.rs.core.Application subclass getSingletons()
> and getClasses() methods.
> The reason for this is that on unregistetration a new RequestProcessor is not
> created right away but only scheduled for the next request. Adding a new
> resource should trigger creation of a new RequestProcessor if the request
> processor is outdated
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
