Hi
Could you may be post your web.xml here because 404 means that
servelet mappings might be incorrect. Otherwise it's very strange.
Renat
On 23/07/07, yosemite <[EMAIL PROTECTED]> wrote:
Hello,
thanks. Security on WebSphere is turned off. I also tried to modify to
was.policy with no success:
grant codeBase "file:${application}" {
permission java.security.AllPermission;
};
Funny thing is that a default welcome jsp gets displayed OK and Tapestry
filter seems to get invoked OK because
http://localhost:9080/TestWeb/index.jsp displays:
[WebContainer : 2] DEBUG
org.apache.tapestry.ioc.services.TapestryIOCModule.ThreadLocale - Invoking
constructor org.apache.tapestry.ioc.internal.services.ThreadLocaleImpl() (at
ThreadLocaleImpl.java:26).
in the console; while anything like http://localhost:9080/TestWeb/start says
HTTP 404 - File not found.
Maybe deployment descriptor mapping
<context-param>
<!-- The only significant configuration for Tapestry 5, this informs
Tapestry of where to look for pages, components and mixins. -->
<param-name>tapestry.app-package</param-name>
<param-value>cz.test</param-value>
</context-param>
works different in WebSphere? I have packaged my Tapestry class and html
into
TestApp.ear\TestWeb.war\WEB-INF\classes\ and Tapestry cannot find it there?
Karel
Renat Zubairov wrote:
>
> Hi
>
> Is security on the WebSphere on?
>
> I had significant problems in WS 5 with Security ON because of
> Javassist bug with classloaders.
>
> Renat
>
> On 20/07/07, yosemite <[EMAIL PROTECTED]> wrote:
>>
>> Hello everybody,
>>
>> I tried to deploy a T5 application that works fine on Jetty and Tomcat
>> onto
>> WebSphere 6.1.0.3, and although the app deploys OK, TapestryFilter does
>> not
>> get invoked on url-patterrn /* so I get HTTP 404.
>>
>> SystemOut.log contains lines like
>> ... [WebContainer : 1] DEBUG
>> org.apache.tapestry.ioc.services.TapestryIOCModule.ClassFactory -
>> Creating
>> class from ClassFab[
>> public class $ServletApplicationInitializer_113e33644e7 extends
>> java.lang.Object
>> implements org.apache.tapestry.services.ServletApplicationInitializer
>> private final org.apache.tapestry.ioc.ObjectCreator _creator;
>> public
>>
$ServletApplicationInitializer_113e33644e7(org.apache.tapestry.ioc.ObjectCreator
>> $1)
>> _creator = $1;
>> ... so I guess WAS can load Tapestry OK. Is there something blocking
>> Tapestry5 on WebSphere 6.1?
>>
>> Any ideas, please
>> Thanks
>> Karel
>> --
>> View this message in context:
>> http://www.nabble.com/Tapestry5-and-WebSphere6.1-tf4116345.html#a11705964
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Best regards,
> Renat Zubairov
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Tapestry5-and-WebSphere6.1-tf4116345.html#a11742285
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Best regards,
Renat Zubairov
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
