-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MyFaces exception using wildfly-myfaces-injection-1.0.0.Final.jar #7
Comments
If you could provide a small reproducer, that would be super handy. It might be a while before I have time to try to cobble together one myself. |
I apologize for not replying sooner. Since the problem occurred in our huge JSF application, it's not easily possible to create a reproducer from that by removing parts of the application. Creating a reproducer from scratch would probably also take quite a bit of time, which I sadly don't have and my employer sadly won't pay. Unless you know a Maven archetype or sample project which can be deployed on WildFly and includes JSF, MyFaces, PrimeFaces, etc.? |
My understanding is that you are describing primefaces-test project. |
AFAIK, the primefaces-test project uses jetty to deploy the JSF application. I don't understand how it could be used to test WildFly modules. |
Maybe I am wrong, but I thought you can anyway build a war from it. |
I'll have to check, thanks. |
I get a weird exception when using this feature pack on WildFly 30:
Maybe there would be other exceptions, but I didn't test our whole application.
When I change the
org.jboss.as.jsf-injection:myfaces
module to includewildfly-jsf-injection-30.0.0.Final.jar
andweld-jsf-5.1.2.Final.jar
instead ofwildfly-myfaces-injection-1.0.0.Final.jar
and remove theprovides
tag as I did with WildFly 27, the exception goes away.It's going to be difficult to reproduce but there's definitely something wrong. Maybe it's just an incompatibility with WildFly 30?
The text was updated successfully, but these errors were encountered: