[
https://issues.apache.org/jira/browse/EXTSCRIPT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864044#comment-15864044
]
Leonardo Uribe commented on EXTSCRIPT-188:
------------------------------------------
Just to clarify, the change done in 2.2.3 to rename
org.apache.myfaces.config.impl.digester.elements.ManagedBean into
org.apache.myfaces.config.impl.digester.elements.ManagedBeanImpl was to make
the distinction with org.apache.myfaces.config.element.ManagedBean. There was
no structural changes in that part for 2.2.3. 2.1.x branch does not have the
change, so the latest 2.1.x version will work.
> 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)
