[ 
https://issues.apache.org/jira/browse/CLEREZZA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004249#comment-13004249
 ] 

Reto Bachmann-Gmür commented on CLEREZZA-325:
---------------------------------------------

The reason is the messagebodywriter is chosen based on concreteness of the type 
of the writer: the platform GenericGraphNodeMBW produces */* while the 
GraphNodeWriter from org.apache.clerezza.jaxrs.rdf.providers produces some 
concrete rdf formats.

To change this behaviour we could change the Produces-Annotation of 
GenericGraphNodeMBW to @Produces({"application/xhtml+xml", "*/*"})

However for resources where the is no capable renderlet, this would lead to an 
xhtml page with much less content than the rdf.

e.g.:
curl -u admin:admin http://localhost:8080/test
<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
<html xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"; lang="en">
        <head>
                <link type="text/css" href="/style/style.css" rel="stylesheet" 
/>
                <title>Untitled Content</title>
        </head>
        <body>
                        http://localhost:8080/test
        </body>

Of course if the default renderlet could deliver an RDFA version of the 
resource context this would be the preferable version.

> Have server side media-type priority list to use when the cleint accept 
> header expresses equal preference for multiple available representations
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLEREZZA-325
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-325
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Reto Bachmann-Gmür
>            Assignee: Reto Bachmann-Gmür
>
> revert CLEREZZA-324 once this implemented

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to