anonymous wrote : 1. What content-type is your user agent expecting? text/wml,
or something to that effect?
The content type for the WML is "text/vnd.wap.wml".
anonymous wrote : 2. The cms portlet should be able to serve non text/html,
text, but doesn't presently. Note, it does not serve binaries. Those have to be
served from the servlet level.
I think the portlet must be invisible if it doesn't support the current MIME
type.
anonymous wrote : 3. To serve wap content, we'd probably have to take the user
agent in to account. I've never worked with wap/wml serving, so any input would
be appreciated, Arturas.
I'm glad to help the team. I'm coding the new content type interceptor and I'm
going to provide you guys with that. My idea is:
1. Only the portal can set the MIME type.
2. Other parts of portal (pages, portlets) uses portal's MIME type.
3. Pages and portlets declares MIME types it can handle. Pages and portlets are
not displayed if the current MIME type is not supported.
For that reason we need to remove all setContentType('text/html').
Regards,
Arturas
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864833#3864833
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864833
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
