[
http://jira.magnolia.info/browse/MAGNOLIA-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bracher resolved MAGNOLIA-2361.
---------------------------------------
Resolution: Won't Fix
So resolve the issue (reopen it in case you don't agree)
> Content2bean: fallback to default implementation when class property is empty
> or wrongly set ?
> ----------------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2361
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2361
> Project: Magnolia
> Issue Type: Bug
> Components: core
> Reporter: Gregory Joseph
> Assignee: Philipp Bracher
> Fix For: 3.6.x
>
>
> To be discussed: as per MAGNOLIA-1688, it might be useful to fallback to the
> default implementation class when a {{class}} property is set to an
> unexisting class or is empty. I am not entirely convinced, because this is
> typically a configuration mistake and it should not be ignored. Maybe a
> precise warning/error log before falling back would be good. (depending on
> what component is being configured, this could otherwise block the system -
> i.e for filters for instance)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
