�I can't do anything with request contexts in the image. �
self session
self requestContext
etc
won't work in the debugger as they are dynamic variables which use the exception mechanism to retrieve their value (search for references to�WACurrentRequestContext)
If you are in the debugger and you need the session or the request context you can either follow the stack trace until you find a variable holding the session or request context or just add the following code to the method you are debugging and resume the debugger:
| theSession theRequestContext |
.
.
.
theSession := self session.
theRequestContext := self requestContext.
self halt.
---
Hope this helps
Nick
�
----------------
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> 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