Quarkus JVM mode with JSF
I have an existing thorntail 2.4 based web application built using JSF and JEE (CDI/EJB).
For my technology stack above, if I am only using the JVM mode and not the native mode, is it possible to package my application using runtime?
I understand that EJB spec is not implemented with quarkus and I am OK with rewriting EJBs as CDI+JTA services but want to know if it's possible to use JSF with quarkus.
There is an extension for it available: https://github.com/tandraschko/quarkus-myfaces
UPDATE: I moved my 'personal' extension to MyFaces Core and we already have an 2.3-next-M1 release ready.
The showcase is available here and already uses the released version: https://github.com/apache/myfaces/tree/master/extensions/quarkus/showcase
UPDATE: We even released M2 today which supports native images!
Quarkus doesn't provide a JSF extension.
But it should be possible for your application to directly include a JSF implementation as a dependency and have it work
Related
Is jsf 2.2 not supported on glassfish 3.1.2?
My viewActions are not being invoked and some simple things do not behave same way as supposed with 2.1.23. So i am not sure about filing issues for 2.2
You can manually update the .jar file located at the Glassfish's /modules directory.
More information: How do I upgrade the JSF API in GlassFish?
By updating jar file some feature is supported. But, some of the feature. e.g. JSON processing is not supported. Use Glassfish 4.0 for best support.
I understand that the Trinidad framework is an extension of MyFaces project (who is the JSF implementation). But, I have JSF project that has only the trinidad dependencies. So, I ask:
How works this project without the JSF implementation´s dependencies?
Thank you
Apparently the project which you've in hands is been targeted for deployment on a real Java EE application server.
Normally, JSF is already provided as part of the Java EE API by a decent Java EE application server such as Glassfish, JBoss AS, WebSphere, WebLogic, etc. The web application project does not need to include the JSF libraries at all (like as it does not ever need to include the JSP/Servlet/EJB/JPA/etc libraries when deployed to such a server).
However, in case of barebones JSP/Servlet containers like Tomcat and Jetty, JSF is not provided by the server itself. JSF has either to be manually installed in those containers or to be provided by the web application project itself.
JSF component libraries like Trinidad, PrimeFaces, RichFaces, etc are not part of the Java EE API and thus surely need to be supplied by the web application project itself.
I am migrating a JSF application from WebSphere(WAS) 6.1 to WAS 7.0 and I am experiencing html deprecation issues now that I am using the JSP 2.1 API provided with WAS 7.0 as opposed to the JSP 2.0 API provided with WAS 6.1. Weblogic provides the ability to enable backward compatibility (http://docs.oracle.com/cd/E21764_01/web.1111/e13754/compat.htm#i1111538) in the weblogic app deployment descriptor. Is there a similar solution available in WAS 7.0? Is there a way to enable backwards compatibility in a deployment descriptor so the application can use JSF 2.0 API and not face the deprecated html issues?
There is nothing conclusive about this in the WebSphere Application Server 7.0 documentation, therefore I am led to believe that the typical IBM strategy is used here: The JSP engine you're getting with WAS 7.0 is JSP 2.1 compatible, period. You can't replace it and can't instruct WAS to use an older specification level.
Can someone please help me out with the Oracle ADF faces application which I'm trying to deploy on Websphere 7.0? Do I need to apply any fixpacks on WAS? I'm trying to migrate this project from Websphere 6.1 to Websphere 7.0.
In Websphere 6.1, after removing jsf implementation jar files and providing them as part of WEB-INF\lib and changing the classloader to PARENT_LAST, the application was working fine.
For websphere 7.0, I can't seem to get the application working. It always picks up the Sun's JSF implementation. I've also tried the shared library concept but to no success.
Regards,
Zahir
The Oracle documentation lists a certification for WAS 7.0.0.13 ND. So you need FixPack 13 or later.
As the WebSphere Application Server 7 is a full blown JEE5 server it requires/has JSF 1.2 support. You can switch between the built in Sun and MyFaces implementation if required.
You should probably make sure that the ADF version you are using is certified for WAS 7. The ADF release notes tell that ADF supports JSF 2.0. The WAS 7 only comes with JSF 1.2. Exchanging the JSF version with placing the JSF 2 libs into WEB-INF/lib works well for our projects in conjunction with the 'PARENT_LAST' classloading policy. Make sure that you set the policy either for the whole application or for both the application and the web module.
ADF Faces is a Java based framework and it will run on WebSphere but, you have to add the required libraries first. The easiest way to prepare WebSphere to run ADF Faces application is through JDeveloper. Alternatively, you can google Oracle JRF (Java Runtime Framework) and install that on your WebSphere, before running the ADF Faces application.
What is the configuration one has to do for deploying EJB 2.1 in Jboss AS 6.0?
Kindly refer to links, if there are any.
There should not be any explicit configuration needed. JBoss AS 6 officially only supports the Java EE web profile (which doesn't include EJB 2.1 at all), but in practice they have implemented the full stack and EJB 2.1 beans should just work.
That said, if at any way possible, try to avoid EJB 2.1. It's a bloated, nasty and heavy-weight technology that's literally from another era. For any new development EJB 3.1 or even 3.0 is highly recommended.