Yes it is, the reason are :
1. simplicity
2. people can change it by changing the interceptor anyway
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3915726#3915726
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3915726
Could someone please explain how the ContentTypeInterceptor, ModesInterceptor
and the supports section of the portlet.xml file work to set the content type
of the response. Looking at the ContentTypeInterceptor it appears that the
response is always going to be text/html no matter what is put
the content type interceptor determines the content type that the browser
requested / can handle. The portal takes this content type as the allowed
content type for the current request. Portlets that want to set a particular
content type need to first check if the current request supports that
mholzner wrote :
| the content type interceptor determines the content type that the browser
requested / can handle
|
I guess I'm just not seeing how the ContentTypeInterceptor actually does what
you said.
| ...
| try
| {
| // Set UTF-8 for parameter decoding
|
ahem, I guess in theory it should ;)
You are right. It is hard coded for now. I wasn't aware of that.
Time for some community contributions :)
Since we're on this topic, does anyone have experince with CC/PP?
How would that fit into this discussion.
My current thinking is that this , or a
Did you try:
| supports
| mime-typebla/mime-type
| mime-typebla/mime-type
| mime-typebla/mime-type
| mime-typebla/mime-type
| /support
|
Wild guess.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3914079#3914079
Reply to the post :
Actually I did try that initially but it yelled at me when I started the portal
saying something about too many elements...so I figured that wasn't allowed...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3914082#3914082
Reply to the post :
