Hi all I'm hitting an issue that is really, really starting to get my goat. The AssetService service appears to have the WebRequest object auto-wired into it via Hivemind. This is a little odd as all of the other dependencies are wired in normally via the Hivemind mapping. I'm sure its just an oversite by whoever wired up the AssetService in Tapestry but its now causing me problems.
Normally this wouldn't be a problem but I'm trying to get around my cookie writing problem (previously posted), the last bit of it is that WebRequest.forward doesn't flush the applications state when it sends a redirect to the client (possibly a bug?). To get around this I've written an Interceptor that intercepts calls to the WebRequest.forward method and uses the ApplicationStateManger.flush to write out the application state. All fine so far. Unfortnately this somehow stops the auto-wiring from wiring the WebRequest into the AssetService so I now get lots of NullPointerExceptions in AssetService. I'm thinking that the auto-wiring of WebRequest into AssetService shouldn't be happening (so another bug?) but is there a way around it for the moment? I could write another interceptor for the AsserService to inject the WebRequest into it but then I could hit the problem in another location for another service and end up having interceptors all over the place. Is there a better solution? Thanks, Rob Cole --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
