You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/17 14:32:14 UTC

[jira] [Commented] (TAP5-2199) Web project is not able to run on Websphere 8.0.05

    [ https://issues.apache.org/jira/browse/TAP5-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000774#comment-14000774 ] 

Jochen Kemnade commented on TAP5-2199:
--------------------------------------

In your description, you say that the problem occurs with Tapestry 5.3.2, but you have set the issue's "Affects Version/s" field to 5.3.7, 5.4. Which one is correct?
I ask because I assume this is related to TAP5-1854 and might already be fixed.

> Web project is not able to run on Websphere 8.0.05
> --------------------------------------------------
>
>                 Key: TAP5-2199
>                 URL: https://issues.apache.org/jira/browse/TAP5-2199
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-func
>    Affects Versions: 5.3.7, 5.4
>            Reporter: raghavendra
>            Priority: Critical
>              Labels: -, Tapestry, WAS8
>
> We are unable to get our Enterprise tapestry application running on Websphere Application server.
> Software Details:
> WAS 8.0
> Tapestry 5.3.2
> JDK 1.6.0.33
> Ajax failure with tapestry 5.3.2 on Websphere (WAS) 8.0
> When Individual tapestry pages are called, they work fine. 
> But when I submit a form and form is returning a page, then it goes to pagloaded event of the next page . After that it does not move forward.
> After restart, first form submit takes us to pageloaded and not to setuprender but subsequent call don’t take us even to pageloaded
> It gives the following error: “Ajax failure: Status for : SyntaxError: Syntax error Communication with the server failed: SyntaxError: Syntax error”
> It seems like Tapestry in WAS is failing to communicate with browser when we submit a form.
> If I try accessing an standalone page, it is accessible. AJAX communication within pages seems to be a problem here.



--
This message was sent by Atlassian JIRA
(v6.2#6252)