Skip to main content

Web.xml 301

I am a J2EE consultant by profession. Like in every other profession, You learn new things every day. The project I consult for, is architected viewing far ahead technologically. Although Many in my own project disagree that the project is in pristine shape (code wise). But to me, All it needs is a little tidying up (complement that superior design). However, at the core, This one is a masterpiece. And being an aspiring architect, I have had yet another those "Best so Far" projects. Here are somethings I haven't done in the past but did in this project.

Filters:
Recently I have had close encounters with Filters. the Advanced version of them. We have Sitemesh, OpenSessionInView, Acegi all filtering the requests. Acegi Filter itself calls its own (Configurable) Filter Chain.

The most commonly use of a filter is on a url-pattern
<url-pattern>PATTERN_HERE</url-pattern>
- However, It can also be used on servlets using <servlet-name>directgroup</servlet-name> You can also combine them to get both url mapping and also servlet.
There is also a dispatcher (<dispatcher>VAL_HERE</dispatcher>) which can further filter based if it was REQUEST, FORWARD etc - More Doc here

Scriptlets:
I have not seen this before - but apparently, You can disable Scriplets on certain pages completely. <% %> doesn't work in those pages
You can achieve that like this
<jsp-property-group>
<url-pattern>/WEB-INF/*</url-pattern>
<scripting-invalid>true</scripting-invalid>
</jsp-property-group>


there will more coming in this series. I have to write a lot about Acegi. with time.. ;) check back later.

Leave comments in Guestbook
Labels:

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.
Read More >>

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.
Read More >>

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>
Read More >>