Content type is based on the client accessing the portal. If you are accessing via a browser, it will always be text/html. This is done by inspecting the "User-Agent" header in the request and then looking at jetspeed's capability map to figure out the preferred content type to use. You can alter the capability map by changing the database tables CLIENT and CLIENT_TO_MIME type to force jetspeed to use an alternate content type.
HTH, Scott > -----Original Message----- > From: Jacek Wiślicki [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 30, 2005 12:07 PM > To: Jetspeed Developers List > Subject: Re: content-type > > Wiadomosc od Thanos Fakiolas z 2005-08-30 18:01 brzmiala: > > > what do you mean? > I would like to see your code, check if it's correct and test it at my > installations. > > i think that the solution is at the configuration of jetspeed! do you > > know which file generates the portal page? > Wow, a good question ;) It's a quite complex process. > > P.S. I'm not sure if it would matter, but do you have separate > decorators for XML? > > -- > pozdrawiam, > Jacek Wislicki > > [EMAIL PROTECTED] > tel.: +48 502 408 444 > gg: 2540358 > skype: jacek_wislicki > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
