[JBoss JIRA] (RF-12486) Metamer: rich:calendar: Attribute change leads to disappear attributes area [myfaces]
by Ján Jamrich (JIRA)
[ https://issues.jboss.org/browse/RF-12486?page=com.atlassian.jira.plugin.s... ]
Ján Jamrich reassigned RF-12486:
--------------------------------
Assignee: (was: Ján Jamrich)
> Metamer: rich:calendar: Attribute change leads to disappear attributes area [myfaces]
> -------------------------------------------------------------------------------------
>
> Key: RF-12486
> URL: https://issues.jboss.org/browse/RF-12486
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.Milestone1
> Environment: RichFaces 4.3.0.20120802-M1
> Metamer 4.3.0.20120802-M1
> Apache MyFaces JSF-2.1 Core Impl 2.1.8
> Apache Tomcat 7.0.29
> OpenJDK Runtime Environment 1.7.0_05-icedtea-mockbuild_2012_07_09_19_42-b00 @ Linux
> Chrome 20.0.1132.47 @ Linux i686
> Reporter: Ján Jamrich
> Labels: myfaces
>
> When select date from popup, and then change an attribute value, after automatic page reload whole area with attributes disappears and no longer possible change calendar value until page reload (just F5 doesn't work, as well as Rerender and Reload Metamer's buttons )
> This seems to be the same problem as with Mojarra but with slightly different behavior with MyFaces. See related issues for more info for Mojarra.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (RF-12486) Metamer: rich:calendar: Attribute change leads to disappear attributes area [myfaces]
by Ján Jamrich (JIRA)
[ https://issues.jboss.org/browse/RF-12486?page=com.atlassian.jira.plugin.s... ]
Ján Jamrich moved RFPL-2334 to RF-12486:
----------------------------------------
Project: RichFaces (was: RichFaces Planning)
Key: RF-12486 (was: RFPL-2334)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 4.3.0.Milestone1
(was: 4.3.0.Milestone1)
> Metamer: rich:calendar: Attribute change leads to disappear attributes area [myfaces]
> -------------------------------------------------------------------------------------
>
> Key: RF-12486
> URL: https://issues.jboss.org/browse/RF-12486
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.Milestone1
> Environment: RichFaces 4.3.0.20120802-M1
> Metamer 4.3.0.20120802-M1
> Apache MyFaces JSF-2.1 Core Impl 2.1.8
> Apache Tomcat 7.0.29
> OpenJDK Runtime Environment 1.7.0_05-icedtea-mockbuild_2012_07_09_19_42-b00 @ Linux
> Chrome 20.0.1132.47 @ Linux i686
> Reporter: Ján Jamrich
> Assignee: Ján Jamrich
> Labels: myfaces
>
> When select date from popup, and then change an attribute value, after automatic page reload whole area with attributes disappears and no longer possible change calendar value until page reload (just F5 doesn't work, as well as Rerender and Reload Metamer's buttons )
> This seems to be the same problem as with Mojarra but with slightly different behavior with MyFaces. See related issues for more info for Mojarra.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (RF-12459) Validate required fields on blur
by Bernard Labno (JIRA)
Bernard Labno created RF-12459:
----------------------------------
Summary: Validate required fields on blur
Key: RF-12459
URL: https://issues.jboss.org/browse/RF-12459
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: component-validators
Affects Versions: 4.2.2.Final
Reporter: Bernard Labno
Priority: Minor
It's generally good to validate input onchange event, but there is one exception. It's validateRequired. This validator, if present should be also added to onblur event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (RF-12273) rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL
by Neil Griffin (JIRA)
Neil Griffin created RF-12273:
---------------------------------
Summary: rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL
Key: RF-12273
URL: https://issues.jboss.org/browse/RF-12273
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component, portal
Affects Versions: 4.2.0.Final
Reporter: Neil Griffin
The fileupload.js JavaScript resource has a bug such that it uses the form's "action" attribute as the XmlHttpRequest URL, rather than the "javax.faces.encodedURL" hidden field value.
I think this is where the problem exists:
{code} __submit: function() {
var originalAction = this.form.attr("action");
var originalEncoding = this.form.attr("encoding");
var originalEnctype = this.form.attr("enctype");
try {
var delimiter = originalAction.indexOf("?") == -1 ? "?" : "&";
this.form.attr("action", originalAction + delimiter + UID + "=" + this.loadableItem.uid);
this.form.attr("encoding", "multipart/form-data");
this.form.attr("enctype", "multipart/form-data");
richfaces.submitForm(this.form, {"org.richfaces.ajax.component": this.id}, this.id);
richfaces.Event.fire(this.element, "onfilesubmit", this.loadableItem.model);
} finally {
this.form.attr("action", originalAction);
this.form.attr("encoding", originalEncoding);
this.form.attr("enctype", originalEnctype);
this.loadableItem.input.removeAttr("name");
}
},{code}
Until this is fixed, the component will not function in a portlet environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (RF-11952) Showcase: Glassfish -specific profile
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-11952:
-------------------------------
Summary: Showcase: Glassfish -specific profile
Key: RF-11952
URL: https://issues.jboss.org/browse/RF-11952
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: showcase
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Since Showcase uses JPA/JMS, {{jee6}} profile can't be deployed onto Glassfish.
It would be necessary to provide custom profile for Glassfish with custom {{persistence.xml}} setup.
{code}
javax.naming.NameNotFoundException: No object bound to name java:/DefaultDS
{code}
{code}
Caused by: javax.naming.NamingException: Lookup failed for '/ConnectionFactory' ...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months