myfaces


Java EE 7 Application not deploying on Glassfish 4 Sever after switching from Mojarra to MyFaces

こ雲淡風輕ζ 提交于 2020-01-16 07:16:08
问题 Currently we have a problem when we try to deploy our Java EE 7 application to a glassfish 4.0 server. Before we changed the JSF implementation from JSF Mojarra 2.2.0 to MyFaces 2.2.2 it worked pretty well. Heres the error log: >2014-03-24T16:05:42.356+0100|Schwerwiegend: Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI? 2014-03-24T16:05:42.357+0100|Schwerwiegend: Die Anwendung wurde bei Systemstart nicht einwandfrei

Java EE 7 Application not deploying on Glassfish 4 Sever after switching from Mojarra to MyFaces

狂风中的少年 提交于 2020-01-16 07:16:05
问题 Currently we have a problem when we try to deploy our Java EE 7 application to a glassfish 4.0 server. Before we changed the JSF implementation from JSF Mojarra 2.2.0 to MyFaces 2.2.2 it worked pretty well. Heres the error log: >2014-03-24T16:05:42.356+0100|Schwerwiegend: Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI? 2014-03-24T16:05:42.357+0100|Schwerwiegend: Die Anwendung wurde bei Systemstart nicht einwandfrei

Custom renderer for PrimeFaces component works fine in Tomcat, but not in Websphere

爷,独闯天下 提交于 2020-01-14 09:28:28
问题 I'm using MyFaces 2.1.9 and PrimeFaces 3.5. I've implemented a custom renderer for <p:inputText> . This works fine at home with Tomcat. But this does not work at work with Websphere. I've placed breakpoints in the custom renderer class, but they are never hit. I see nothing in my logs as well. However, when I register the very same custom renderer on standard JSF <h:inputText> , then it works fine. I've registered it as follows in faces-config.xml : <render-kit> <renderer> <component-family

“could not initialize proxy - no session” with an open session available

孤人 提交于 2020-01-13 18:23:37
问题 I work with JSF 2 (MyFaces 2.1.7 and Primefaces 3.4.2), CDI (Weld-servlet 1.1.10), JPA 2 (Hibernate 4.1.7) and Lombok 0.11.2. All this runs on Tomcat 6 and 7. I use the OpenSessionInView pattern, implemented through a Filter . @Advanced @Data @Slf4j public class TransactionalFilter implements Filter, Serializable { private static final long serialVersionUID = 999173590695648899L; @Inject private EntityManager em; @Override public void doFilter(ServletRequest request, ServletResponse response,

Jsf pages shows blank when deployed on Tomcat 7

邮差的信 提交于 2020-01-06 08:47:13
问题 Application builds fine and deploys, the index.html pages shows up before redirecting to the login.xhtml page and there the problem begins, the login.xhtml page displays blank and the view source does same thing. Any help will be appreciated. Below is my web.xml file <?xml version="1.0" encoding="UTF-8" ?> <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi

Migrating to JSF 2.3, Problems with MyFaces Initialization

倾然丶 夕夏残阳落幕 提交于 2020-01-06 05:44:07
问题 I'm upgrading an application comprised of two projects, "common" and "myapp". I'm now upgrading it to JSF 2.3 (MyFaces) and Primefaces 7 , and I can't figure out how to get past a failure in initialization. I should note that there've been a lot of other changes as well. Both projects had been successfully upgraded to OpenJDK 11 , Tomcat 9 , and to using Maven . And with the change to JSF 2.3, managed beans are no longer supported in favor of JAVA's CDI API, which inconveniently is longer

Undefined component type javax.faces.ViewRoot in JSF 2.3 startup

流过昼夜 提交于 2020-01-06 05:37:07
问题 This is a new twist from my earlier issues found here. I'm upgrading from MyFaces 2.1 to 2.3.5, and from PrimeFaces 6.1 to 7. This has also included migrating from managed beans to CDI. At this point, the server starts up and it appears that MyFaces, PrimeFaces, and CDI are being initialized. However, when I attempt to load my first page I get " Undefined component type javax.faces.ViewRoot ". Note, this is a "component type" not a class. Tracing into the MyFaces code, I can see that the

How can I check if an object stored with @WindowScoped is stored correctly?

╄→尐↘猪︶ㄣ 提交于 2020-01-05 07:44:32
问题 Two days ago I wrote this question: How can I retrieve an object on @WindowScoped? and BalusC answered with some suggestions, now I have some problem to understand if my problem is that the object in WindowScoped is stored properly or my code to retrieve it is wrong! Well, as I said, I have an object that I stored in @WindowScoped annotation but I can retrive this object only the first time! Why? I just have a doubt: the CODI extension of MyFaces could be configured in some manner? Or I can

How can I check if an object stored with @WindowScoped is stored correctly?

跟風遠走 提交于 2020-01-05 07:44:08
问题 Two days ago I wrote this question: How can I retrieve an object on @WindowScoped? and BalusC answered with some suggestions, now I have some problem to understand if my problem is that the object in WindowScoped is stored properly or my code to retrieve it is wrong! Well, as I said, I have an object that I stored in @WindowScoped annotation but I can retrive this object only the first time! Why? I just have a doubt: the CODI extension of MyFaces could be configured in some manner? Or I can

PrimeFaces ViewExpiredException after page reload

我的未来我决定 提交于 2020-01-04 03:00:11
问题 I have wrapper PrimeFaces.ajax.AjaxResponse to handle ViewExpiredException (reloading the page): var handleViewExpired = function (viewId) { window.alert('${msg.ajax.viewExpired}'); window.location.reload(); }; However, sometimes I got that error over and over again after trying to click anything invoking AJAX requests on the site: javax.faces.application.ViewExpiredException: /tree.xhtmlNo saved view state could be found for the view identifier: /tree.xhtml at org.apache.myfaces.lifecycle

工具导航Map