[
https://issues.apache.org/jira/browse/STANBOL-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-1022.
------------------------------------------
Resolution: Fixed
changed with http://svn.apache.org/r1466327
> Entityhub JAX-RS resource should check in its constructor if the entityhub
> service is available
> -----------------------------------------------------------------------------------------------
>
> Key: STANBOL-1022
> URL: https://issues.apache.org/jira/browse/STANBOL-1022
> Project: Stanbol
> Issue Type: Bug
> Components: Entityhub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
>
> With the changes of STANBOL-996 the timings of service registrations during
> startup have changed. Typically the startup of components is faster while
> actual services are registered later (relative to components.
> Because of this is is more likely that the WebFragment of the Entityub is
> already registered, wile the EntityhubService is not yet available. If this
> is the case, than calls to the RESTful services of the Entityhub do result in
> NPEs and 500 responses.
> Instead the JAX-RS resource for the Entityhub should check the availability
> of the Entityhub service and correctly answer with an 404 status code and a
> message explaining that the Entityhub is not available.
> This issues is also the cause for recent unstable Jenkins build (e.g. 1341
> [1]).
> [1] https://builds.apache.org/job/stanbol-trunk-1.6/1341
--
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
