Bug #971
Error when saving a new notification
Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
11/26/2013
Due date:
% Done:
0%
Description
The following error has been reported from the production environment (www.etbmanagerdb.org) by e-mail:
org.jboss.seam.RequiredException @In attribute requires non-null value: caseBDHome.caseHome org.jboss.seam.RequiredException: @In attribute requires non-null value: caseBDHome.caseHome at org.jboss.seam.Component.getValueToInject(Component.java:2361) at org.jboss.seam.Component.injectAttributes(Component.java:1739) at org.jboss.seam.Component.inject(Component.java:1557) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:61) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:97) at org.jboss.seam.util.Work.workInTransaction(Work.java:61) at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:91)
This error is rose when a new notification is posted.
History
#1
Updated by Ricardo Memoria over 11 years ago
Fixed.
The error could be replicated like that:
1. Start a new notification;
2. Fill all required fields;
3. Double-click on the "Save" button (double-clicking will send two requests to the server);
4. The first request is executed, but the second raises an error;
Solution:
Implemented JS in the save button, so when clicking on it, it's disabled (using the save approach as in use in the generic version)
#2
Updated by Ricardo Memoria over 11 years ago
- Status changed from New to Resolved
#3
Updated by Ricardo Memoria over 11 years ago
- Assignee changed from Ricardo Memoria to Luis Gustavo do Valle Bastos
#4
Updated by Luis Gustavo do Valle Bastos over 11 years ago
- Status changed from Resolved to Closed
Tested and adequate.