[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wink-dev
Subject:    [jira] [Resolved] (WINK-375) wink-osgi reregistering previously unregistered service
From:       "Luciano Resende (JIRA)" <jira () apache ! org>
Date:       2012-12-11 7:13:21
Message-ID: JIRA.12622886.1354873328604.16485.1355210001356 () arcas
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WINK-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Luciano Resende resolved WINK-375.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3

Thanks for the patch.
                
> 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


[prev in list] [next in list] [prev in thread] [next in thread]