#15 ComponentID param in ConfigurationException

[Dennis Veltrop]

I think it would be a good idea to provide the componentid in a ConfigurationException. For example; the debug info below is quite undescriptive when having several DBContainsDataRules configured:

2006-11-27 16:30:59,379 ERROR [com.logicacmg.eplatform.core.servlet.PageServlet] Error while doing work.==>com.logicacmg.eplatform.core.exception.ConfigurationException: java.sql.SQLException: Invalid column name 'ikpnummer'.=(Message)=>java.sql.SQLException: Invalid column name 'ikpnummer'.=(Stack)=>
2006-11-27 16:30:59,379 INFO [STDOUT] com.logicacmg.eplatform.core.exception.ConfigurationException: java.sql.SQLException: Invalid column name 'ikpnummer'.
2006-11-27 16:30:59,379 INFO [STDOUT] at com.logicacmg.eplatform.rule.domain.DBContainsDataRule.apply(DBContainsDataRule.java:92)
2006-11-27 16:30:59,379 INFO [STDOUT] at com.logicacmg.eplatform.core.authorisation.RuleConstraint.apply(RuleConstraint.java:145)
2006-11-27 16:30:59,379 INFO [STDOUT] at com.logicacmg.eplatform.configuration.epom.EpomObject.hasAuthorizationAttribute(EpomObject.java:181)

This way, it would be easier to find the

/ ApplicationRuntimeEx