myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Commented] (EXTSCRIPT-188) Extension don't works on Myfaces 2.2.3 / 2.2.11
Date Mon, 13 Feb 2017 08:53:41 GMT

    [ https://issues.apache.org/jira/browse/EXTSCRIPT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863343#comment-15863343
] 

Werner Punz commented on EXTSCRIPT-188:
---------------------------------------

Ok as promised, here an initial result from my findings. As it seems. The internal managed
beans from myfaces apis have changed. The problem simply is. JSF up until today has no official
api to plug in managed beans on the fly so I had to revert to platform specific apis for that.
And now that the jsf api has adopted cdi as official bean standard, it is highly unlikely
that this will change.

I will roll another version asap. But that means it will take a little bit. I probably will
be able to start to work on it on the second of March. Not before. (I am bound by job and
private life so I wont have time before that)

(Note: the startup error given is java.lang.ClassNotFoundException: org.apache.myfaces.config.impl.digester.elements.ManagedBean)

Also in the long run I have to look into the possibility to get the bean plugging mechanism
in a neutral way into CDI. For now I only have it working for OpenWebbeans, but not for the
RI (which at the time I wrote it did not have a well working api for that, that might has
changed) and decomission the managed beans support entirely. But that depends on having an
offical api on the cdi side to do this.



> Extension don't works on Myfaces 2.2.3 / 2.2.11
> -----------------------------------------------
>
>                 Key: EXTSCRIPT-188
>                 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-188
>             Project: MyFaces Extensions Scripting
>          Issue Type: Bug
>          Components: MyFaces 2.0 Extension
>    Affects Versions: 1.0.6-FINAL
>         Environment: Debian 8.2
> JDK 1.8
> Tomcat 7.0.42
>            Reporter: NCister
>            Assignee: Werner Punz
>
> Trying to follow example config (http://myfaces.apache.org/extensions/scripting/exampleconfig.html)
I've noticed that the web.xml settings are wrong so:
> <param-name>org.apache.myfaces.FACES_INIT_PLUGINS</param-name>
> <param-value>org.apache.myfaces.extensions.scripting.servlet.StartupServletContextPluginChainLoader</param-value>
> must be updated to:
> ...
> <param-value>org.apache.myfaces.extensions.scripting.jsf.startup.StartupServletContextPluginChainLoader</param-value>
> ...
> Again: The example war (https://repository.apache.org/content/repositories/releases/org/apache/myfaces/extensions/scripting/myfaces20-extscript-helloworld/1.0.5/myfaces20-extscript-helloworld-1.0.5.war)
deployed in a clean tomcat 7.0 instance) don't works (no errors, no results ...)
> Does Groovy integration works in MyFaces 2.2 ?
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message