jhomuth schrieb:
> Hi again,
>
> I fixed that problem after a 3 days searching the whole internet. I
> only wanna submit the solution if somebody has the same problem.
>
> I thought it was not the css and js stuff, because i copied it
> directly into my page, because it could not be found on the server,
> but I guess I did something wrong. Of course it was the css and js
> stuff. In MyFaces this stuff will be loaded through an Ressourceloader
> which is called through the Extensionfilter. But in Websphere (WAS
> 6.1) this filter is not invoked. To fix that you will have to set a
> property for your server.
>
> In the german version (which I use) you have to go to
>
> Server -> Anwendungsserver -> <yourServerName (eg. server1)> ->
> Webcontainer-Einstellungen -> Webcontainer -> Benutzerdefinierte
> Merkmale -> Neu and than set
> com.ibm.ws.webcontainer.invokefilterscompatibility to true.
> <http://localhost:9061/ibm/console/propertyCollection.do?EditAction=true&refId=Property_1225443461159&contextId=cells%3AavengerNode02Cell%3Anodes%3AavengerNode02%3Aservers%3Aserver1&resourceUri=server.xml&perspective=tab.configuration>
>
>
> in the english version it might be something like that
>
> Server -> Applicationserver -> <yourServerName (eg. server1)> ->
> Webcontainer-Preferences -> Webcontainer -> Userdefined Setting -> NEW
> and than set com.ibm.ws.webcontainer.invokefilterscompatibility to
> true.
> <http://localhost:9061/ibm/console/propertyCollection.do?EditAction=true&refId=Property_1225443461159&contextId=cells%3AavengerNode02Cell%3Anodes%3AavengerNode02%3Aservers%3Aserver1&resourceUri=server.xml&perspective=tab.configuration>
>
>
> After that please restart the server and then it will work. I mean it
> work in my case and I hope it will work for you in the same way.
> I found the solution here if you need some additional information
>
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg32571.html
I was curious about what this property did, and had a quick search. I
couldn't find any definite specification, but it looks to me like the
following occurs. I'm adding this info here just for future reference..
Most servlet containers do this:
* if request url matches a servlet
* compute filters, run filters, run servlet
* else
* set servlet to the "file-serving servlet"
* compute filters, run filters, run servlet
But websphere seems to do this by default:
* if request url matches a servlet
* compute filters, run filters, run servlet
* else if url points to file on disk
* compute filters, run filters, return file
* else send 404 immediately
Therefore applications that use filters to service a request (ie never
invoke the underlying servlet) don't work. And this is exactly what the
tomahawk ExtensionsFilter does; it checks the url and for certain urls
it serves the response itself. And the urls don't point to files on
disk; once "decoded" they do reference a file in a jarfile but websphere
can't know that.
And because ExtensionsFilter is not used to fetch *pages*, but instead
(optional) files like .css and .js, the user doesn't get an obvious 404
error on their screen; the .css or .js is just missing when the page is
rendered.
Setting the magic property appears to make websphere act like every
other servlet engine on the planet. Sigh.
Regards,
Simon
--
-- Emails in "mixed" posting style will be ignored
-- (http://en.wikipedia.org/wiki/Posting_style)
