You are absolutely right Robin, it is really very simple when someone
is working only with Cocoon and Fins and the xml input data is not
coming from DB(which isn't the normal case). 
In my webapp scenario I have an existing webapp which is (as 90% of
webapps these days) based on Struts and charts is a very very tiny
part/enhancement of it. So i am using cocoon plugin to get it work with
struts. Now as you must have figured that part out we have only one
entry point to our webapp which is Struts servlet.

So considering your solution, which is very obvious and appropriate, my
dynamically generated html page will have a src with
"http://blah..getmeonlychart.do"; ..and this makes it two calls to
server for one user request. 

I hope i explained it to you.

-S

--- Robin Wyles <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I may be looking at this too simplistically, or missing part of your 
> problem, but it appears to me that you are trying to achieve all this
> 
> in one pipeline, when two would be easier.
> 
> 1st pipeline:
> 1. Generate the xml
> 2. Transform using xsl
> 3. Serialize into html, with the src of your image tag pointing to
> 2nd 
> matcher
> 
> 2nd pipeline:
> 1. Generate xml
> 2. Transform into image stream (I assume that you don't actually have
> 
> to save it to disk)
> 
> I'm going to be using Fins in a project very soon, and I sort of 
> imagined that this was the way I would approach it for charts that
> are 
> truly dynamic, so any feedback would be appreciated...
> 
> Robin
> 
> 
> On 2 Jul 2004, at 00:17, Java Developer wrote:
> 
> > Hi All,
> >
> > I am writing a webbapp which generates charts inside a dynamically
> > generated html page using cocoon and fins block.
> >
> > My problem is I m looking for a simpler way so that, in a pipeline,
> I
> > should be able to :
> >
> > 1. Generate the xml //Done ..not a problem
> > 2. Transform into image stream // partially done...that is THE
> PROBLEM
> > 3. Get the original xml back //Done..not a problem
> > 4. Transform using xsl//Done..not a problem
> > 5. Serialize into html //with image tag that points to step 2
> generated
> > image.
> >
> > Currently I m saving the image generated in step 2 and html is
> reading
> > it..which includes an IO operation(which i obiviously want to
> avoid).
> >
> > Other way could be storing the image stream into session by
> modifying
> > step 2 transformer, later rendering the image using servlet or
> > jsp.(which is again a server call..but should be faster than IO,
> love
> > to know any better way of doing it)
> >
> > My first question is how to access http request or session inside
> > cocoon transformer, and second is Am I trying to reinvent the wheel
> > again ? is anybody has a better way for displaying image in an html
> > page using cocoon in the current scenario ??
> >
> > Thanks much for your help and suggestions.
> >
> > I apologize being so fussy sounding too demanding.
> >
> >
> >
> > =====
> > - Java Developer
> >
> >
> >             
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail - 50x more storage than other providers!
> > http://promotions.yahoo.com/new_mail
> >
> >
> ---------------------------------------------------------------------
> > 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]
> 
> 


=====
- Java Developer


                
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to