Tomasz Szymanski wrote:
But then... I bet it'll throw another exception, related to the order in which you're finishing the transaction. If it does, you'll probably figure out why.
Automatically managed component initialization. <strong>WARNING:</strong>
* This method is automatically generated, so any user-specified code inserted
* here is subject to being replaced.
seb petterson wrote:In my web.xml file I have:
as well asBut still when I type in a url for a jsp file with the extension replaced for jsf the webserver returns "file not found".
I should mention that I have a boiled down version of my webapp working on a local tomcat instance. However, the target environment for the jsf enabled jsps is an existing webapplication in a WebSphere Application Server, and here it fails.
In the web.xml file there are also many elements declaring various filter-mappings and servlet-mappings, including for the url-pattern /*, can this be the cause of the mapping not working for *.jsf?
Thanks in advance,
[ July 27, 2005: Message edited by: seb petterson ]