[
https://issues.apache.org/jira/browse/STANBOL-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197840#comment-13197840
]
Ali Anil Sinaci commented on STANBOL-476:
-----------------------------------------
As far as I see, ContentItemResource is not a real web resource in enhancer, it
is used as a data model. And Enhancer produces its HTML by using this model
with a different ftl than the one we use within Contenthub. Enhancer does not
draw the download links, so they are only used within Contenthub currently. I
think in older versions, these download links were also used within the
Enhancer webUI. Anyway, I added a new parameter to remove the word "contenthub"
from ContentItemResource.
Maybe a refactoring is needed for ContentItemResource, however I dont think
that this is a good time to move whole ContenItem related staff from the
enhancer. STANBOL-471 may introduce new models for the management of content
items within Contenthub.
> Wrong URIs in ContentHub HTML metadata and content download links
> -----------------------------------------------------------------
>
> Key: STANBOL-476
> URL: https://issues.apache.org/jira/browse/STANBOL-476
> Project: Stanbol
> Issue Type: Bug
> Components: Content Hub
> Reporter: Alessandro Adamou
> Labels: REST
>
> Upon creating a new content item using the [stanbol-host]/contenthub/store
> HTML interface, a new ContentItemResource is created, e.g.
> http://localhost:8080/contenthub/store/page/urn:content-item-sha1-c08cb1a33e7343bd1c9b85f98800ac1bac157c76
> The Web template for that resource has content item and enhancement download
> links, but their URIs miss the "contenthub" endpoint:
> http://localhost:8080/store/raw/urn:content-item-sha1-c08cb1a33e7343bd1c9b85f98800ac1bac157c76
> http://localhost:8080/store/metadata/urn:content-item-sha1-c08cb1a33e7343bd1c9b85f98800ac1bac157c76
> where they should be http://localhost:8080/contenthub/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
