[JBoss JIRA] Created: (RF-1487) Framework. Client events handler doesn't work properly.
by Ilya Shaikovsky (JIRA)
Framework. Client events handler doesn't work properly.
-------------------------------------------------------
Key: RF-1487
URL: http://jira.jboss.com/jira/browse/RF-1487
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Ilya Shaikovsky
Assigned To: Nick Belaevski
Fix For: 3.2.0
<h:form id="form">
<h:inputText>
<a4j:support event="onkeyup" oncomplete="alert('support complete')" onsubmit="alert('support onsubmit')" onbeforedomupdate="alert('onbeforedomeupdate')"></a4j:support>
</h:inputText>
<a4j:jsFunction name="callfunction" data="#{bean.property1}" oncomplete="alert('1');"></a4j:jsFunction>
<a4j:commandButton value="press" oncomplete="alert('1');"></a4j:commandButton>
<h:graphicImage value="/pages/alabama.gif" onclick="callfunction();">
</h:graphicImage>
<a4j:log popup="false"></a4j:log>
</h:form>
NOTHING except onsubmit and onbeforedomeupdate handlers works on this snippet under 3.2.0 SNAPSHOT. JS fuinction, support and a4j:button isn't calls its oncomplete, .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (RF-1360) BaseFilter fails to recognize non-faces resource requests, invoking BaseXMLFilter.doXmlFilter()
by Stuart Robertson (JIRA)
BaseFilter fails to recognize non-faces resource requests, invoking BaseXMLFilter.doXmlFilter()
-----------------------------------------------------------------------------------------------
Key: RF-1360
URL: http://jira.jboss.com/jira/browse/RF-1360
Project: RichFaces
Issue Type: Bug
Environment: Richfaces 3.1.3 (cvs), Seam 2.0.1 (cvs), Jboss 4.2.2
Reporter: Stuart Robertson
Priority: Critical
Fix For: 3.1.3
When servicing a non-jsf request, in this case to stream a pdf down to the user, the BaseFilter is mangling the contentType by appending an incorrect char encoding onto the (correct) content type.
13:58:28,313 INFO [FileServlet] Streaming file About Stu.pdf, contentType application/pdf and size 94171 to browser...
13:58:28,371 ERROR [STDERR] java.lang.Exception: contentType set to application/pdf;charset=ISO-8859-1
13:58:28,371 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl$1.setContentType(SeamFilter.java:66)
13:58:28,371 ERROR [STDERR] at javax.servlet.ServletResponseWrapper.setContentType(ServletResponseWrapper.java:130)
13:58:28,371 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl$1.setContentType(SeamFilter.java:65)
13:58:28,371 ERROR [STDERR] at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:260)
13:58:28,371 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
13:58:28,371 ERROR [STDERR] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
And in BaseFilter, doXmlFilter is always invoked because the if condition is for "true". Here is the code from BaseFilter starting on line 271:
// check ajax request parameter
// TODO - check for JSF page.
if (true) {
if (log.isDebugEnabled()) {
log.debug(Messages
.getMessage(Messages.FILTER_XML_OUTPUT));
}
// Execute the rest of the filter chain, including the
// JSP
xmlFilter.doXmlFilter(chain, httpServletRequest,
httpServletResponse);
doXmlFilter() appends an incorrect charType to a resource mimetype (in this case "application/pdf"). The correct behavior, if I read the code correctly, would be to invoke chain.doFilter() for resource requests.
I think the key is in the TODO. The code needs to recognize when the request is outside of faces, and not interfere with the response headers at that point.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (RF-1340) datascroller: Id attribute generated wrong in tld
by Ilya Shaikovsky (JIRA)
datascroller: Id attribute generated wrong in tld
-------------------------------------------------
Key: RF-1340
URL: http://jira.jboss.com/jira/browse/RF-1340
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Ilya Shaikovsky
Assigned To: Maksim Kaszynski
Fix For: 3.2.0
check the forum description. and pay attention to
<name>id</name>
<deferred-value>
<type>java.lang.String</type>
</deferred-value>
</attribute>
<attribute>
<description>Attribute allows to ignore an Ajax Response produced by a request if the newest 'similar' request is
in a queue already. ignoreDupResponses="true" does not cancel the request while it is processed on the server,
but just allows to avoid unnecessary updates on the client side if the response isn't actual now</description>
in tld
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months