[
https://issues.apache.org/jira/browse/MYFACES-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859346#action_12859346
]
Werner Punz edited comment on MYFACES-2666 at 4/21/10 9:41 AM:
---------------------------------------------------------------
Ok a manual include of my javascripts showed the same problem with the switched
attributes which causes
firebug not to load the scripts after the first loaded script.
as mentioned above as it seems the error was carried over from the latest trunk
codebase.
however writing it as <script type="text/javascript"
src="/trinidad-demo/resources/js/myfaces/_impl/_util/_LangUtils.js"><!--
--></script>
fixes the issue.
That is the reason why Trinidad did not include jsf.js
Anyway MyFaces also has a problem I was able to submit a valid ppr request over
our manually included scripts on both the ri and myfaces
Tr-PPR-Message true
_noJavaScript false
event autosub
itxt Change this text
j_id_id119
javax.faces.ViewState !rti5p6zcy
javax.faces.partial.ajax true
javax.faces.partial.event click
javax.faces.partial.execu... rb3
javax.faces.source rb3
org.apache.myfaces.trinid... j_id_id18
partial true
selOne 0
source
source rb3
theGroup rb3
While the RI properly issued an xhr response
Myfaces seems to have introduced problems with handling of jspxes lately in the
ppr cycle, the response on the myfaces side was
Das Laden des Quelltexts ist fehlgeschlagen::
http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx
Which means loading of the source has failed...
so we have two problems here, one on the Trinidad side, not being able to load
jsf.js (still wonder why myfaces also fails on the ppr part while the ri does
not in that case)
and the other one on the myfaces side with not being able to deliver a proper
ppr response to a valid ppr request!
was (Author: werpu):
Ok a manual include of my javascripts showed the same problem with the
switched attributes which causes
firebug not to load the scripts after the first loaded script.
as mentioned above as it seems the error was carried over from the latest trunk
codebase.
however writing it as <script type="text/javascript"
src="/trinidad-demo/resources/js/myfaces/_impl/_util/_LangUtils.js"><!--
--></script>
fixes the issue.
> Getting a full-page-refresh when running JSF's Ajax on the Trinidad 2 (trunk)
> -----------------------------------------------------------------------------
>
> Key: MYFACES-2666
> URL: https://issues.apache.org/jira/browse/MYFACES-2666
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0
> Reporter: Matthias Weßendorf
>
> Running "pprDemos.jspx" page and triggering any ajax action, we see a
> full-page-refresh
> (tested with TRUNK of MyFaces2)
> Check out Trinidad trunk and change the pom.xml to take myfaces =>
> 2.0.1-SNAPSHOT instead of the beta-3
> go to trinidad-examples/trinidad-demo and trigger "mvn clean jetty:run
> -PjettyConfig"
> Now point a browser to this URL:
> http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
