This week's book giveaway is in the Open Source Projects forum.
We're giving away four copies of Eclipse Collections Categorically: Level up your programming game and have Donald Raab on-line!
See this thread for details.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Intercepting request parameters in JSP.

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

I need to modify/scan the request parameters and set them to different values. I've heard that it is possible through filters. Can it be achieved in iPlanet 6.5 application server and are there any known problems, say of performance in using the filter class?

Is there a simpler solution by which deployment can be avoided? Because for implementing filters the web.xml file will require changes and will call for redeployment.

Awaiting responses.

Cheers,
Amit.
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Amit Shanker:
I need to modify/scan the request parameters and set them to different values. I've heard that it is possible through filters. Can it be achieved in iPlanet 6.5 application server and are there any known problems, say of performance in using the filter class?


It can be achieved with iPlanet 6.5 if iPlanet 6.5 supports the Java Servlet 2.3 specification (filters were introduced in 2.3, if I remember correctly).
Regarding performance, it shouldn't be a problem if you're not doing anything "big" inside the filter. If you're worried about performance, you should test it yourself and see how it affects your particular architecture and application profile.

Originally posted by Amit Shanker:
Is there a simpler solution by which deployment can be avoided? Because for implementing filters the web.xml file will require changes and will call for redeployment.

If you want to avoid redeployment of the application, the only other option is to intercept the raw network packets between the client and the web server. It is waaaaay better to just redeploy the application.
 
Sheriff
Posts: 7023
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Moving this to the Servlets forum...
 
Don't sweat petty things, or pet sweaty things. But cuddle this tiny ad:
Clean our rivers and oceans from home
https://www.kickstarter.com/projects/paulwheaton/willow-feeders
reply
    Bookmark Topic Watch Topic
  • New Topic