I tried it out and would look like;
Caused by: org.apache.polygene.api.service.ServiceImporterException:
org.apache.polygene.api.constraint.ConstraintViolationException:
Constraint violation in
ds-derbysql.[DataSourceConfiguration,EntityComposite] for method
'driver' with constraint "not optional(driver)", for value 'null'
at method importService of
DBCPDataSourceServiceImporter:derbysql-datasource-service() in module
DerbySQLStorage Module' of layer 'Infrastructure Layer'.(:0)
at
org.apache.polygene.library.sql.datasource.AbstractDataSourceServiceImporterMixin.importService(AbstractDataSourceServiceImporterMixin.java:95)
at
org.apache.polygene.library.sql.datasource.AbstractDataSourceServiceImporterMixin.importService(AbstractDataSourceServiceImporterMixin.java:46)
The (:0) at end of line is remnants of line number in "normal" stack trace
elements.
Cheers
On Sun, May 28, 2017 at 12:34 PM, Niclas Hedhman <nic...@hedhman.org> wrote:
> Hi,
>
> I am thinking of adding a StackTraceElement in exceptions that indicate
> which module the problem is detected in.
>
> WDYT? implementation is not too hard, I think just few lines in
> CompositeMethodModel
>
>
> Cheers
> --
> Niclas Hedhman, Software Developer
> http://polygene.apache.org - New Energy for Java
>
--
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java
