How to get RequestContext object in Filters??

Hello All,

I am using TS 6.7.2 with Livesite 3.0 on Linux.

My requirement is to access the error page set under default.site from a servlet filter.

One way which I could think of is to call livesite runtime API and get RequestContext object using :

RequestUtils.getRequestContext(request)

Because I am using the filter so I am getting request object which I can pass to the method getRequestContext.

But even after doing that I am getting context object as NULL.

Could someone please provide any pointers or solution to access the error page inside the filter without parsing default.site.

The requirement is quite urgent, any help would be appreciated.

Thanks in advance

Find more posts tagged with

Comments

Rick Poulin

You cannot obtain the request context in your filter because that object hasn't been created yet. You'll have to find another way to get the information you need. If you only have one site and all you need is the name of the error page, then you can go read the default.site file directly with an XML parser.

SE123

You cannot obtain the request context in your filter because that object hasn't been created yet. You'll have to find another way to get the information you need. If you only have one site and all you need is the name of the error page, then you can go read the default.site file directly with an XML parser.

Hi rpoulin,

Thanks for your reply, I have managed to get the RequestContext object in my filter. I just changed the normal filter to Spring Filter by chaging the filter-class to DelegatingFilterProxy and defined the mapping in application context.

Now the problem is that when I access any .page I get the context object and also get the error page of site.
But if I have any form and I submit that form to a servlet say
/servlet/SubmitLogin
My filter in this case gets invoked but I get null context object with same code.

Dont know what is wrong.

Rick Poulin

My filter in this case gets invoked but I get null context object with same code.

Dont know what is wrong.

Well I just said you can't get the RequestContext in your filter. I guess I should have specified "in a supported manner". In this case, I don't know what wizardry you used to instantiate the RequestContext, but it seems you missed at least one use case. Either way, I don't know what your custom code looks like and I can't really help you go further down that unsupported rabbit hole, as you're likely in uncharted territory.