Skip to main content

ADF Servlet Filter

By
This blog is to guide you how you can filter the requests and add your custom checks in ADF application.

Follow below steps to create/configure a Servlet Filter in your ADF/Webcenter application.

1. From new wizard select Servlet and select Servlet Filter





2. Click on next


3. Enter the name of Servlet filter and package


4. Map to Servlet or JSP radio button should be selected and it is default selection.


5. Click on finish and you will get a servlet filter created.


This is the class generated after you click finish, it is having init, destroy and doFilter methods. 
We will write our logic in doFilter method. This will be called whenever a Servlet or jsp page request arrive to application.   


As we created servlet filter with ADF steps so it has added our filter entry in web.xml file which is a mandate to work our filter. 
We can create other filters also but we must register it in web.xml file.


We can mention servlet initialization parameter when we are configuring our ServletFilter or after configuring also and same parameters can  be used.
Main purpose of such servlet filters is to fix security issues, work on application navigation control, validation of XSS and much more.

I added some code in doFilter method. here we can check for session timeout, or any attacks from other domain etc.


Based on your validation/requirement, you can force it inside this method(doFilter) and navigate your application to desired page by setting response value. In example i have set value of initialization parameter to response variable which was added in web.xml while initializing the servlet Filter. 

Comments

Post a Comment

Popular posts from this blog

Passivation and Activation in ADF (Application Module )

By
1. For performance reasons, ADF keeps a pool of application modules in memory. It tries to give each session the same application module as the session used during the last request; however, this might not be possible during peak load of your application. 2. In this case, ADF saves the application modules state in a database table so the application module can be used by another session. This is called passivation . 3. When the first session needs the application module again, its state is retrieved from the database process known as activation . 4. If you have made an error in your code and depend on some variable that is not persisted correctly when your application module state is stored, you will experience mysterious errors under high load.   Enable/Disable Application Module Pooling : Right-click on your application module, choose Configurations.By default, each application module has two configurations. Ensure that the one ending in …Local is selected and then click
1 comment
Read more

Get modified rows from Entitiy Cache

By
To get the modified rows from entity cache we have getEntityState() method at EntityImpl class. Refer to my previous blog  Accessing EO impl methods from VO impl  where i am overriding the getEntityState() in EOimpl and calling it in VOImpl. We can use methods written or overridden in VOImpl class to AMImpl class. There are different states associated with an entity object. STATUS_UNMODIFIED STATUS_MODIFIED STATUS_NEW STATUS_DELETED STATUS_DEAD We have to check the state or row in our AmImpl class by using the VOImpl method and through this we can distinguish the rows present at vo. Add below code in AMImpl class along with my previous post. public void geCachedRowsCount(){         JobsVOImpl jobsVo = (JobsVOImpl)this.getJobsVO();         RowSetIterator iter = jobsVo.createRowSetIterator(null);             while(iter.hasNext()){             Row row = iter.next();             byte state = jobsVo.getEntityState(row);             System.out.println("Job_id -&
2 comments
Read more

The file store "WLS_DIAGNOSTICS" could not be opened

By
WLS_DIAGNOSTIC ERROR weblogic.store.PersistentStoreException: [Store:280073]The file store "WLS_DIAGNOSTICS" could not be opened because it contained a file with the invalid version 1. A file of version 2 was expected. When you get this error while running your application on internal weblogic server delete the following file WLS_DIAGNOSTICS000000.DAT search the file in following path C:\jdev_work\system11.1.1.5.37.60.13\DefaultDomain this file is in DefaultDomain folder of your jdev. and delete the WLS_DIAGNOSTICS000000.DAT file . and run your applicatuon
1 comment
Read more