[
https://issues.apache.org/jira/browse/TOMEE-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608788#comment-13608788
]
Romain Manni-Bucau commented on TOMEE-836:
------------------------------------------
Wich such an exception the error is logged upper in the logs. If not the log
setting is probably wrong (not the default one)
> ReportValidationResults should log.info about the root cause
> ------------------------------------------------------------
>
> Key: TOMEE-836
> URL: https://issues.apache.org/jira/browse/TOMEE-836
> Project: TomEE
> Issue Type: Bug
> Components: Compliance Checks
> Affects Versions: 1.5.1
> Reporter: Mark Struberg
> Fix For: 1.6.0
>
>
> I'm having an EJB which references a @PersistenceContext with a not yet
> defined DataSource.
> This leads to a Deployment error, but the real cause is well hidden
> internally and doesn't get logged properly.
> Same happens if the persistence unit itself is not configured.
> This currently doesn't even lead to a deployment Exception but OpenEJB just
> resumes to start.
> If I debug into ReportValidationResults#deploy line 66
> uberContext.addFailure(failure);
> then I see the issue. But it doesn't get logged it seems.
> This should at least be logged with INFO level imo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
