I was just reading this thread from August. Unfortunately, I *think* I
need a custom stream handler factory as I want to be able to hack about
with some of the URLs before they get a chance to open. Here's the
scenario:
- I have a directory containing a resource - call it X.xml - and a JSP -
call it displayX.jsp.
- I want to read X.xml from code within the JSP. What are the ways,
accoring to the JSP and servlet specs, that I can do this?
I need to intercept all of those ways, because that file X.xml might be
somewhere else completely and only need to appear to the webapp to be in
that directory. For bonus points, the JSP itself might be in a
different place from its requested URL (I have a filter that remaps
paths on requests, as suggested by Steve Kirk in response to an earlier
plea for help on this list).
Can anyone think of a way I can get by without a custom stream handler,
yet still allow an unmodified webapp to access this 'virtual file
system' functionality?
- Peter
--
Peter Crowther, Director, Melandra Limited
John Dalton House, 121 Deansgate, Manchester M3 2AB
t: +44 (0)161 828 8736 f: +44 (0)161 832 5683
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
