[
https://issues.jboss.org/browse/FORGE-587?page=com.atlassian.jira.plugin....
]
Ryan Bradley commented on FORGE-587:
------------------------------------
I've been meaning to take a look into this, but it should be possible to disable
validation of search criteria in the Forge configuration.
The JSF views for Forge are generated using Metawidget. To disable validation, one should
be able to use a different Metawidget configuration which ignores any validation
constraints.
However, I am unfamiliar with how JSF enforces validation constraints. I presume it's
done using the backing bean? If that's the case, we may be able to create a separate
backing bean to be used for the search page which does not contain any validation
criteria.
Forge Generated CRUD - Next Button Fail
---------------------------------------
Key: FORGE-587
URL:
https://issues.jboss.org/browse/FORGE-587
Project: Forge
Issue Type: Bug
Reporter: Burr Sutter
Priority: Critical
This likely a Forge specific bug
1) run admin_layer.fsh to generate CRUD screens for event, show, ticket, booking, etc
2) Go to Event at
http://localhost:8080/ticket-monster/faces/admin/event/search.xhtml
3) With the longer list of events (from the newer import.sql) - click on Next
This causes two errors:
"An event's name must contain between 5 and 50 characters"
"An event's name must contain between 20 and 1000 characters"
--
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