arturas, you are right on all points and this is actually what the spec says.
1. yes the portal decides the mime type and this is what the content type interceptor does. 2. show only the portlet that can produce this mime type and declare it. it is done in portlet.xml in the support tag 3. today our portlet are not designed for that : the portlet should do a response.getContentType and according to that content type do q switch/case 4. we will go in that direction, BUT this is not the priority of the project today. So the migration is going to be done step by step. Today we have more important priorities. So keep cool we're doing it, but in a controlled manner 5. you forget something, the dispatching to the aggregqtor (theme) must also be based on the content type. Today it will do HTML View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864855#3864855 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864855 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
