The multiple XML docs was my intention. In my application, the xml payloads are wrappered inside of <payload> tags (as per the ICE spec) I have xml controllers and controls that create the wrappers. It works great for me, but yes, I can see where there could be an agregrated XML format.
> Portlets would be nice if serving as Web services ;-) Any one tried? Oasis has a Web Services for Remote Portals committee defining standards in this area > -----Original Message----- > From: Ozgur Balsoy [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 15, 2002 2:00 PM > To: Jetspeed Users List > Subject: Re: XML media type testing > > > Both sound great. I have tested the agentxml/1.0. It works fine. > > I see that there are multiple XML docs in the output. It looks like we > need XML aggregation like HTML where the result is one big XML following > a schema with other XMLs inside (without prologs,of course). Some thing > like: > > <portal> > <portal-metadata/> > <session-metadata/> > <etc/> > <porlet id="xxx"> > <output here/> > </portlet> > <porlet id="xxx"> > <output here/> > </portlet> > </portal> > > Is this what you're trying to do? > > Portlets would be nice if serving as Web services ;-) Any one tried? > > Ozgur > > David Sean Taylor wrote: > > Ozgur, > > > > Im using Jetspeed as an XML portal, where Jetspeed checks the User-Agent > > header for the string "agentxml/1.0" - see the Capability Map. Perhaps a > > better way would be to check for "accept/xml" in the "Accept" > string, but I > > really haven't been able to relay on it. If you'd like I can > add the check > > for Accept "text/xml". Im working on this code today and tomorrow. > > > > Another approach that I am now trying out is to setup a separate > > layout/template URL that always returns a specific XML flavour (in my > > particular case - ICE). That way I don't have to depend on the agent > > providing the correct headers. > > > > David > > > > > >>-----Original Message----- > >>From: Ozgur Balsoy [mailto:[EMAIL PROTECTED]] > >>Sent: Thursday, August 15, 2002 12:18 PM > >>To: Jetspeed Users List > >>Subject: XML media type testing > >> > >> > >>Hi, > >> > >>Does any one know how to test Jetspeed with clients accepting text/xml > >>media type? Is there any client for this or do we need to make low level > >>HTTP connections? In this case, what would be valid HTTP headers? > >> > >>I have tried something like the following but could not get it working: > >> > >>GET /jetspeed/portal/ HTTP/1.1 > >>Connection: Keep-Alive > >>User-Agent: MyAgent/1.0 > >>Accept-Charset: iso-8859-1 > >>Accept: text/xml > >>Host: montblanc:1111 > >> > >> > >>ozgur > >> > >> > >>-- > >>To unsubscribe, e-mail: > >><mailto:[EMAIL PROTECTED]> > >>For additional commands, e-mail: > >><mailto:[EMAIL PROTECTED]> > >> > >> > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
