Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 439 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Handling AttrValException and throwing proper error message in UI

Hi All,
I have a scenario where I need to validate each attribute of a row before I push it into the DB. Validation of the attribute is majorly checking if the value is null or not. If null I am raising a AttrValException. However because of the BundleException property, it doesn't throw the exception onto the UI directly/immediately but it gets bundled up into RowValException and then into a TxnValException. After inserting the row, I have other data which is processed and validated in similar fashion. I am using OperationBinding to invoke the method which inserts the rows. However, when I use OpeationBinding.getErrors() post execute, it doesn't pick up the TxnValException and proceeds further and tries to commit the data(I am using EL {binding.commit.execute} for commit action).
Here are my doubts relating to this
1) Why isn't OperationBinding.getErrors picking up the TxnValException?
2) If OperationBinding.getErrors doesn't work, what is an alternative to handle this case and check if the exception was thrown or not?
3).When commit runs and sees that the remaining data is exception free, then will it try to commit the valid data and ignore the invalid data or will it throw an exception as some data is corrupt?
4) In case there are multiple attributes which fail the validation, though there is only 1 TxnValException, after iterating through it recursively we can get all AttrValExceptions. How can I throw all the AttrValExceptions simultaneously? Or rather how can I get the error message to display all the AttrValExceptions raised?
Answers
-
Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,457 Red Diamond
And you use which jdev version?
Do you have a test case based on the HR schema?
Timo
-
Jdev - 11.1.1.7.0
Sorry I don't have a test case readily available.
Thanks
Prithvi
-
Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,457 Red Diamond
Can you build one? This would help to sort things out.
Timo