[jira] Work started: (WW-1839) Websphere 6.1: Ajax samples in struts2-showcase-2.0.6.war doesn't work

["Tapio Holopainen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/struts/browse/WW-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on WW-1839 started by Tapio Holopainen.

> Websphere 6.1: Ajax samples in struts2-showcase-2.0.6.war doesn't work
> ----------------------------------------------------------------------
>
>                 Key: WW-1839
>                 URL: https://issues.apache.org/struts/browse/WW-1839
>             Project: Struts 2
>          Issue Type: Bug
>          Components: API, Examples, Views
>    Affects Versions: 2.0.6
>         Environment: Websphere 6.1
>            Reporter: Tapio Holopainen
>         Assigned To: Tapio Holopainen
>            Priority: Critical
>
> I deployed struts2-showcase-2.0.6.war to Tomcat 5.5. AJAX samples worked just fine. Then I deployed the same .war to Websphere 6.1. None of the AJAX samples worked. Other samples seems to work normally. Could it be that Websphere doesn't handle baseRelativePath in djConfig the same way than Tomcat does? There is no exceptions in Websphere log.
>  
> <script language="JavaScript" type="text/javascript">
>     // Dojo configuration
>     djConfig = {
>         baseRelativePath: "/S2Show/struts/dojo",
>         isDebug: false,
>         bindEncoding: "UTF-8",
>         debugAtAllCosts: true // not needed, but allows the Venkman debugger to work with the includes
>     };
> </script>
> <script language="JavaScript" type="text/javascript"
>         src="/S2Show/struts/dojo/dojo.js"></script>
> <script language="JavaScript" type="text/javascript"
>         src="/S2Show/struts/simple/dojoRequire.js"></script>
> <script language="JavaScript" type="text/javascript"
>         src="/S2Show/struts/ajax/dojoRequire.js"></script>
> <script language="JavaScript" type="text/javascript"
>         src="/S2Show/struts/CommonFunctions.js"></script>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.