[JBoss JIRA] (RF-12160) rich:validator does not validate on the client side the @Pattern constraint
by Juraj Huska (JIRA)
Juraj Huska created RF-12160:
--------------------------------
Summary: rich:validator does not validate on the client side the @Pattern constraint
Key: RF-12160
URL: https://issues.jboss.org/browse/RF-12160
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-validators
Affects Versions: 4.2.1.Final
Environment: application: generated project from richfaces-kitchensink-archetype 4.2.1-SNAPSHOT
browser: Chrome, Firefox
Reporter: Juraj Huska
When trying to validate input which has annotation based constraint @Pattern, validation for this constraint is triggered only after the submitting of the form. The other constraints (@NotNull, @Size) are triggered as expected, after the BLUR event fired on that input.
The issue is noticeable on the project generated by the kitchensink archetype with RichFaces 4.2.1-SNAPSHOT libraries.
The facelet for the input validation with pattern annotation-based constraints looks like:
{code:xml}
<h:panelGrid columns="3" columnClasses="titleCell">
<h:outputLabel for="name" value="Name:"/>
<h:inputText id="name" value="#{cc.attrs.member.name}">
<rich:validator/>
</h:inputText>
<rich:message for="name" errorClass="invalid"/>
</h:panelGrid>
{code}
The model entity field which is validated in the above mentioned input:
{code}
@NotNull
@Size(min = 1, max = 25)
@Pattern(regexp = "[A-Za-z ]*", message = "must contain only letters and spaces")
private String name;
{code}
Note that I have tried to reproduce this issue on metamer and I was not successful.
--
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
[JBoss JIRA] (RF-12583) Typo in the makePatternAMatch CSV javascript function
by Brian Leathem (JIRA)
Brian Leathem created RF-12583:
----------------------------------
Summary: Typo in the makePatternAMatch CSV javascript function
Key: RF-12583
URL: https://issues.jboss.org/browse/RF-12583
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone4
Reporter: Brian Leathem
Fix For: 4.2.4, 4.3.0.M3
The _makePatternAMatch_ function was introduced in resolution to RF-11531. however that method has a typo in it. See the extra ";" in the second _pattern_ assignment.
{code}
var makePatternAMatch = function(pattern) {
if (! (pattern.slice(0, 1) === '^') ) {
pattern = '^' + pattern;
}
if (! (pattern.slice(-1) === '$') ) {
pattern = pattern; + '$';
}
return pattern;
}
{code}
--
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
[JBoss JIRA] (RF-12470) Extended DataTable Scrollbar Disappears When Resizing Columns
by Jeff Smith (JIRA)
Jeff Smith created RF-12470:
-------------------------------
Summary: Extended DataTable Scrollbar Disappears When Resizing Columns
Key: RF-12470
URL: https://issues.jboss.org/browse/RF-12470
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.2.2.Final
Reporter: Jeff Smith
Having issue with extended data table horizontal scroll bar disappearing when resizing columns. When researching the issue further in the extendedDataTable.js, I found that the scrollable element style display property was being set to NONE instead of BLOCK when a column was resized. My work around was to call the updateLayout function and set the scrollable element style display property to block. This has seemed to work thus far.
document.onmouseup = function(e) {
#{rich:component('EDT_NAME')}.updateLayout();
#{rich:component('EDT_NAME')}.scrollElement.style.display = "block";
}
--
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
[JBoss JIRA] (RF-12254) kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP Status 500
by Juraj Huska (JIRA)
Juraj Huska created RF-12254:
--------------------------------
Summary: kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP Status 500
Key: RF-12254
URL: https://issues.jboss.org/browse/RF-12254
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: archetype, mobile
Affects Versions: 4.2.2.Final
Environment: project generated from kitchensink archetype
Reporter: Juraj Huska
Priority: Minor
When accessing wrong facelet on mobile device and consequently the right application context, then the HTTP Status 500 is returned with error message, which can be viewed in the attached screenshot.
It is caused because the {{PageBean}} hold the wrong part of the URL in the session,
{code}
public void setLocation(String location) {
this.location = location;
this.page = String.format("/mobile/%s.xhtml", location);
}
{code}
Note that I have tried to change the scope of the PageBean to RequestScoped, but then the list with members what not updated with the new created ones.
--
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
[JBoss JIRA] (RF-12514) rich:message: unite styleClass name for message detail
by Jiří Štefek (JIRA)
Jiří Štefek created RF-12514:
--------------------------------
Summary: rich:message: unite styleClass name for message detail
Key: RF-12514
URL: https://issues.jboss.org/browse/RF-12514
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: RichFaces 4.3.0-SNAPSHOT
Reporter: Jiří Štefek
There are typos for rich:message's style of message detail. On first view of the message there is styleClass of 'rf-msg-det', then 'rf-msg-dtl'. Unite a style class name from 'rf-msg-det' to 'rf-msg-dtl'.
Found typos:
* components validator/ui/src/main/java/org/richfaces/renderkit/MessageRendererBase.java
* ./mobile-compatibility/rf-mobile-skin.css
* ./validator/ui/src/main/resources/META-INF/resources/org.richfaces/msg.ecss
--
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