You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2008/08/21 00:12:44 UTC
[jira] Commented: (TOMAHAWK-1059) Tomahawk dependencies into
commons-el
[ https://issues.apache.org/jira/browse/TOMAHAWK-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624161#action_12624161 ]
Leonardo Uribe commented on TOMAHAWK-1059:
------------------------------------------
After thinking a lot about this topic (long time ago, but I forget to comment it), the solution proposed for this issue was create a core12 branch for tomahawk, so its shared dependency was 3.0.x (instead jsf 1.1 compatible 2.0.x which has the commons-el dependency) so if you use tomahawk12, this dependency is not present and the problem is fixed.
> Tomahawk dependencies into commons-el
> -------------------------------------
>
> Key: TOMAHAWK-1059
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1059
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Environment: All versions
> Reporter: Werner Punz
>
> Tomahawk has dependencies into commons-el which cause an error if you add plain tomahawk into a jsf 1.2 environement. The dependency is introduced by the shared code between tomahawk and the core.
> So far one codepart which has one is a dependency into commons-el.Logger
> the dependency is caused by the class
> org.apache.myfaces.shared.util.ClassUtils
> and it is in the method
> public static Object convertToType(Object value, Class desiredClass)
> {
> if (value == null) return null;
> try
> {
> // Use coersion implemented by JSP EL for consistency with EL
> // expressions. Additionally, it caches some of the coersions.
> return Coercions.coerce(value, desiredClass, COERCION_LOGGER);
> }
> catch (ELException e)
> {
> String message = "Cannot coerce " + value.getClass().getName()
> + " to " + desiredClass.getName();
> log.error(message, e);
> throw new FacesException(message, e);
> }
> }
> You can bypass the shutting down in a jsf 1.2 environment if you add commons-el but then you introduce a clash in el implementations which might cause sideffects in various components.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.