Bug 724392 (BRMS-338) - When adding rules in Guided Editor with the date-effective attribute set, entering a wrong date format does not show warning.
Summary: When adding rules in Guided Editor with the date-effective attribute set, ent...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-338
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: unspecified
Version: 5.0.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.1.0.ER4
Assignee: Tihomir Surdilovic
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks: BRMS-339
TreeView+ depends on / blocked
 
Reported: 2010-06-25 04:29 UTC by Tihomir Surdilovic
Modified: 2010-11-23 13:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-23 13:02:31 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-338 0 Major Closed When adding rules in Guided Editor with the date-effective attribute set, entering a wrong date format does not show war... 2014-02-10 09:38:36 UTC

Description Tihomir Surdilovic 2010-06-25 04:29:07 UTC
Help Desk Ticket Reference: https://access.redhat.com/issue-tracker/?module=issues&action=view&tid=1062023&gid=1354
securitylevel_name: Public

When creating a rule in guided editor and adding the date-effective attribute users can enter an invalid date format and no error or warning are shown. This is bad because after saving the rule and trying to build the package package building fails simply with: 
"	
Sorry, a technical error occurred. Please contact a system administrator."

and in the logs the exception thrown is:

[Mon Aug  2 00:00:00 2010] it should follow: [dd-MMM-yyyy]
2010-06-25 00:23:47,020 ERROR [STDERR] 	at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:360)
2010-06-25 00:23:47,020 ERROR [STDERR] 	at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:546)
2010-06-25 00:23:47,021 ERROR [STDERR] 	at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:164)
2010-06-25 00:23:47,021 ERROR [STDERR] 	at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceServlet.java:86)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at org.jboss.seam.web.ContextFilter$1.process(ContextFilter.java:42)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
2010-06-25 00:23:47,022 ERROR [STDERR] 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
2010-06-25 00:23:47,023 ERROR [STDERR] 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
2010-06-25 00:23:47,024 ERROR [STDERR] 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
2010-06-25 00:23:47,024 ERROR [STDERR] 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
2010-06-25 00:23:47,024 ERROR [STDERR] 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
2010-06-25 00:23:47,024 ERROR [STDERR] 	at java.lang.Thread.run(Thread.java:637)
2010-06-25 00:23:47,024 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException: Invalid date input format: [Mon Aug  2 00:00:00 2010] it should follow: [dd-MMM-yyyy]

We should put date format restrictions here or best thing is just to use a calendar widget IMO which would eliminate cut/paste or user typos.

Comment 1 Tihomir Surdilovic 2010-09-08 18:53:43 UTC
Link: Added: This issue is duplicated by BRMS-340


Comment 2 Tihomir Surdilovic 2010-09-08 20:49:22 UTC
Link: Added: This issue depends GUVNOR-626


Comment 3 Tihomir Surdilovic 2010-09-10 18:19:44 UTC
Link: Added: This issue is a dependency of BRMS-339


Comment 4 Tihomir Surdilovic 2010-11-04 18:44:18 UTC
Done

Comment 5 Lukáš Petrovický 2010-11-23 13:02:31 UTC
Verified fixed in BRMS 5.1.0 ER4


Note You need to log in before you can comment on or make changes to this bug.