Websphere 7 changes order of servlet filter-mapping on deployment

Hello Experts,

I'm new to websphere, but not to Application Servers. I've worked with a number of light weight and full fledged web/app servers and have never seen this kind of strange behavior. It appears that when I deploy my webapp to Websphere it creates a new web.xml and changes the order of my filter-mapping. This creates some strange behavior, as my filters are in a specific order to setup a hibernate session if it has not yet been done before it authenticates the user. I've combed through the files in the Websphere folders and found that the web_merged.xml file matches this new order. This must be an autogenerated file or something. I modified this file and still end up with the same 'wrong' order when I go into the WAS Admin console and look at the module deployment descriptor.

How can I force the correct order or force WAS to use my web.xml. rather than the generated one?

Thanks in advance.
intlgdAsked:
Who is Participating?
 
intlgdConnect With a Mentor Author Commented:
As it turns out I have added an id: id="my_web_app" and a meta data tag: metadata-complete="true" to get it to leave my web.xml as is. This seems to have solved my problem. Will post any additional changes I run into, should I find additional steps necessary.
0
 
HonorGodSoftware EngineerCommented:
I believe that is the appropriate resolution for a couple of reasons.

From my testing, it appears that the contents of the web_merged.xml file is dynamically generated using application annotations whenever the AppServer is started.

So, using this technique basically circumvents the use of the web_merged.xml file.
0
 
intlgdAuthor Commented:
The solution is correct.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.