[
https://issues.apache.org/jira/browse/STANBOL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved STANBOL-142.
-----------------------------------------
Resolution: Fixed
Works for me and Jenkins build passes, looks good.
> Error 404 on / in enhancer/launchers/full
> -----------------------------------------
>
> Key: STANBOL-142
> URL: https://issues.apache.org/jira/browse/STANBOL-142
> Project: Stanbol
> Issue Type: Bug
> Components: Enhancer
> Reporter: Bertrand Delacretaz
> Assignee: Olivier Grisel
>
> Since the STANBOL-120 changes I have problems with startup of the
> enhancers/launchers/full launcher.
> Looks like a startup timing/problem with org.apache.stanbol.commons.web.base,
> steps to reproduce:
> cd enhancer/launchers/full
> rm -rf sling
> java -Xmx1024M -jar
> target/org.apache.stanbol.enhancer.launchers.full-0.9-SNAPSHOT.jar
> http://localhost:8080/engines -> 404
> Stop and restart the org.apache.stanbol.commons.web.base
> Console says "INFO: Initiating Jersey application, version 'Jersey: 1.2
> 05/07/2010 02:04 PM'
> http://localhost:8080/engines -> 200OK
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
