Update: I looked for tests using a request context and found WAInteractionTest; all test pass, and I was able to set a breakpoint and inspect a nice working request context. So the it's not the downstream seaside image that is at fault.
Confused... I will admit to some creative use of rendering, but it's all done with "components" that have a #basicRenderContentOn:for: where the second argument is the component doing the rendering. The pieces are abstractions of bibtex (hence my interest in Citezen) entries that I didn't want to fully componentize because they can get very numerous with use. But I render (I *think*) by the rules and am asking what should be a valid canvas or component for the context. I'll keep looking. Bill ________________________________ From: [email protected] [[email protected]] on behalf of Schwab,Wilhelm K [[email protected]] Sent: Friday, March 16, 2012 11:37 AM To: [email protected] Subject: [Pharo-project] Seaside image Hello all, I have started to resurrect some of my Seaside code (originally written for 2.8) in the Seaside downstream image for Pharo 1.3 (Seaside 3, I think??). I can't do anything with request contexts in the image. I can try loading Seaside myself in a new image, but I was wondering if anyone has seen this. Bill ----------------- I don't understand what you have been doing wrong. "WACurrenrRequestContext value" will always be available if you are inside a callback or rendering - virtually anywhere in Seaside. Wherever you have a WAComponent you can also send #session to it. On 15 March 2012 18:34, Schwab,Wilhelm K <bschwab at anest.ufl.edu<http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>> wrote: > I am trying to create anchors that will "dynamically" serve pdf > documents. The archive in question is way too big for a FileLibrary and a > separate web server is probably overkill since I intend to do all of this > locally and would rather not have to run Apache on the machines in question > (security paranoia or laziness, take your pick<g>) . So, I was hoping to > create mime documents on the fly. > > I found suggestions such as: > > component session requestContext respond:[ :response | > response > document:self getPdfBytes > mimeType: 'application/pdf' > fileName: 'seaside-test.pdf'; > doNotCache > > I don't see #getPdfBytes, but suspect I can wing it given the file names > in anchors. > > The problem is that everything I ask for a requestContext feigns > ignorance. I can't even get #session because of the same error. I am > using Seaside 3 from the Pharo 1.3 image and Seaside downstream project. > > Any suggestions? > > Bill
