polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <nic...@hedhman.org>
Subject Re: Adding stack trace element ??
Date Sun, 28 May 2017 07:05:46 GMT
I tried it out and would look like;

Caused by: org.apache.polygene.api.service.ServiceImporterException:
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


On Sun, May 28, 2017 at 12:34 PM, Niclas Hedhman <niclas@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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message