Phil, Thanks for the help. JAlbum as used by me is a Swing app - it produces static HTML i.e. I can just point a browser at the directory that is produced and it just works - no container required. It claims to be W3C compliant XHTML (although they are lying a bit about this on the skin I am using according to Xerces :-) ). It's just files served up by the HTMLGenerator - a pretty straightforward example to try out, or so I thought. They are on a remote network drive, but this does work in Cocoon outside the portal.
I am intrigued as to why the image pipeline needs to be in the main sitemap though. Is this just to make it work in the portal or generally? Thanks again, Matt PS. I would wholeheartedly recommend using JAlbum (http://jalbum.net) for all your photo-album-on-the-web needs - it's not open source, but it's free. Makes me wish I had a life ;-P Matt Innes, UTB Consulting matt.innes<at>utbconsulting.com -----Original Message----- From: pguillard [mailto:[EMAIL PROTECTED] Sent: 30 November 2004 02:42 To: [EMAIL PROTECTED] Subject: Re: Including External Apps in Cocoon Portal Hi Matt, I'm worried i can't help you much, since i checked JAlbum and discovered it uses JavaBeans. But just a suggestion : When i did reuse an external application (JSP Servlet) in portal, i had the same situation, testing first that my application was ok in cocoon but outside portal and didn't get it to work in portal : I found that the servlet request, response and session objects were not the classic ones ( http.HttpServletRequest), thus i had to transform Request / Response objects for the portal use : apache.cocoon.environment.Request, apache.cocoon.environment.Response etc. I suppose you'll have to get into JAlbum to make some adaptations too. PS:Another thing: the pipeline to show your images can't be in the coplet pipeline but in the main sitemap pipeline, otherwise you get no image rendered. Hope it helps, Phil Ralph Goers wrote: >Do you have anything in errors.log or on stdout? Also, in 2.1.6 stuff >also goes to portal.log. I seem to recall that that file wasn't >configured in 2.1.5. > >Ralph > > >Matt Innes said: > > >>Instance Data: >> >>... >> <coplet-instance-data id="Exhibit-1" name="standard"> >> <coplet-data>Exhibit</coplet-data> >> </coplet-instance-data> >>... >> >>Layout:: >> >><composite-layout name="tab" id="maintab"> >>... >> <named-item name="Exhibit"> >> <coplet-layout name="coplet"> >> <coplet-instance-data>Exhibit-1</coplet-instance-data> >> </coplet-layout> >> </named-item> >></composite-layout> >> >>Would have included these in the original mail, but I thought I'd >>checked them to within an inch of their lives :-) >> >>Matt Innes, UTB Consulting >>matt.innes<at>utbconsulting.com >> >>-----Original Message----- >>From: Ralph Goers [mailto:[EMAIL PROTECTED] >>Sent: 29 November 2004 16:41 >>To: [EMAIL PROTECTED] >>Subject: Re: Including External Apps in Cocoon Portal >> >>What do your coplet-instance-data and layout definitions look like? >> >>Ralph >> >> >> >> >>--------------------------------------------------------------------- >>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] > > > > > --------------------------------------------------------------------- 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]
