[
https://issues.apache.org/jira/browse/STANBOL-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Christ resolved STANBOL-363.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.9.0-incubating
Tested in a launcher environment of the IKS (http://www.iks-project.eu)
project. Seems to be fixed.
> Bad links running stanbol at subpath
> ------------------------------------
>
> Key: STANBOL-363
> URL: https://issues.apache.org/jira/browse/STANBOL-363
> Project: Stanbol
> Issue Type: Bug
> Reporter: Reto Bachmann-Gmür
> Assignee: Fabian Christ
> Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Whne configuring the JerseyEndpoint to be at /stanbol I encountered the
> following issues (summarizing them here into 1 jira issue as I think they are
> minor and can probably be fiexed together):
> - I'm getting a 404 at /stanbol, only /stanbol/ works, possibly this cannot
> be easily fixed, but then the link on the stanbol logo should point to
> /stanbol/ rather than /stanbol
> - The link to the system-console on the entry page point to
> /stanbol/system/console this is wrong as the system console is independent of
> the jersey endpoint (and inconsistent with the link on /stanbol/engines which
> points to /system/console/components)
> - on stanbol/cmsadapter/map the link is to stanbol/system/console/configMgr
> - on /stanbol/rules the final paragraphs provide to links to /rules
> - /stanbol/sparql has an invalid link to /store
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
