You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2013/11/24 23:14:35 UTC
[jira] [Updated] (TOMEE-836) ReportValidationResults should
log.info about the root cause
[ https://issues.apache.org/jira/browse/TOMEE-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins updated TOMEE-836:
--------------------------------
Fix Version/s: (was: 1.6.0)
1.6.1
> 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.beta1, 1.6.1
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)