[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26165#action_26165
]
Hudson CI server commented on MAGNOLIA-3019:
--------------------------------------------
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#1263|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1263/]
MAGNOLIA-3019 use Throwable.toString() in log message, so we see the
exception class as well, and not "null" if the exception has no message
> CNFE hidden by Content2BeanException
> ------------------------------------
>
> Key: MAGNOLIA-3019
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3019
> Project: Magnolia
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.2.3
> Reporter: Federico Grilli
> Assignee: Federico Grilli
> Fix For: 4.3
>
>
> I've noticed several times while debugging that the real cause of failure for
> {code}
> info.magnolia.content2bean.impl.Content2BeanTransformerImpl.setProperty(..)
> {code}
> is a ClassNotFoundException. However, this cause doesn't show up in logs as
> it is caught and shown like this
> {code}log.error("can't set property [" + propertyName + "] to value [" +
> value + "] in bean [" + bean.getClass().getName() + "]");{code}. It would
> definitely save time and headaches to some people to add the exception cause
> to this message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
