On Monday 07 May 2007 5:00:35 pm Jason Morris wrote:

>
> OK, hypothetically let's say that I have a web-app ...
> OK, let's say that during the initial request, I create
> Writers ... and I stick them in the session...
> ... then I let the session Rete instance know that it's supposed to use
> these routers...
> Q1.  Is this an incorrect approach?
>

No, that sounds fine to me!

> Now, I want to recover
> the output from the various printout statements and the WSTDOUT stream
> sitting the two StringWriters. Since the Writers are in session scope, the
> hack that I have been using is 
> to place <%=expression%> tags inside various HTML tags in the JSP views
> (i.e., <td><%=expression%></td>)  where the expression is extracting the
> StringWriters and dumping their buffers.  This seems terribly inelegant,
> but it works.

Hmmm. I don't know what's wrong with that. The servlet or Bean code is working 
with the Rete instances, which the JSPs know nothing about; they just know 
that there should be StringWriters containing useful data. Why is this 
inelegant? It seems like nice modularity to me. Am I missing something?

> Q2.  In such an asynchronous application, what is the cleanest way to fetch
> re-routed engine output and buffer it to JSP views?

As I said, I don't see any problems here.  On the other hand, I'm not a SCWCD, 
so maybe I simply don't perceive the yuckiness... :)

---------------------------------------------------------
Ernest Friedman-Hill
Advanced Software Research          Phone: (925) 294-2154
Sandia National Labs                FAX:   (925) 294-2234
PO Box 969, MS 9012                 [EMAIL PROTECTED]
Livermore, CA 94550                 http://www.jessrules.com

--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to