On Oct 3, 2008, at 10:13 AM, Jeroen Hoffman wrote:
Hi Mansour,
Well, Jetspeed's table called 'mimetype' holds the know mimetype, of
which the entry with id 1 stands for application/xhtml+xml and 2 for
text/html.
In the table called 'client', various browsers for different
platforms can be identified. Each entry has a value
preferred_mimetype_id that sets the default mimetype to be set as
content type of the response.
So to change it you need to update your client table.
Using SQL this would be:
> update client set preferred_mimetype_id=1 where
preferred_mimetype_id=2;
Im not sure if I understand the problem, but I thought I would give a
little history that might help
Device configuration is imported with Jetspeed XML. We have the
following mime types:
<MimeTypes>
<MimeType>application/xhtml+xml</MimeType>
<MimeType>text/html</MimeType>
<MimeType>text/vnd.wap.wml</MimeType>
<MimeType>text/vxml</MimeType>
<MimeType>text/xhtml</MimeType>
<MimeType>text/xml</MimeType>
</MimeTypes>
You can add an additional mime type, for ex:
<MimeType>image/svg+xml</MimeType>
Whereas your browser's headers provide mime types, Jetspeed maps them
to a more generic media type. You can create your own media type:
<MediaTypes>
<MediaType name="svg">
<charcterSet value="UTF-8"/>
<title value="SVG"/>
<description value="SVG Media Type"/>
<capabilities></capabilities>
<mimeTypes>image/svg+xml</mimeTypes>
</MediaType>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
