[
https://issues.apache.org/jira/browse/GERONIMO-6137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906683#comment-14906683
]
Eduardo commented on GERONIMO-6137:
-----------------------------------
I've been using Apache Myfaces in Geronimo 3.0 and 3.0.1 as well. Last time I
tested using PrimeFaces looking for some specific behaviour. I didn't find any
problem implementing it. I installed PrimeFaces jars to the server repository,
and accessing it using a reference in META-INF/MANIFEST.MF (OSGI way - WAB).
I also have tested web applications with Tomahawk.
> Support to deploy web applications with other JSF vendors
> ---------------------------------------------------------
>
> Key: GERONIMO-6137
> URL: https://issues.apache.org/jira/browse/GERONIMO-6137
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: myfaces
> Affects Versions: 3.0-M1
> Reporter: Ivan
> Assignee: Ivan
> Fix For: 3.0.2
>
>
> Although Geronimo ships the MyFaces implementation, while still some users
> would like to use other JSF providers. In the past, users have to configure
> some classloading options and disable the myfaces deployer.
> The initial idea for it is to detect whether there is another jsf
> implementation in the web application by trying to load some vendor class,
> and once detect, skip the MyFaces builder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
