This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 136225 [details] Glassfish log When working with GF 3.1.2.2 using JSF web app project, whenever I change faces-config.xml file, I get the attached stacktrace. In fact, I don't know if this is a issue in NetBeans or if this is a internal issue in Glassfish. Steps to reproduce: 1) Create new web app with JSF supporte 2) Use PrimeFaces 3.5 as component library 3) Create a faces-config file in project 4) Deploy the project 5) After project is deployed, notice line in glassfish log saying "INFO: Monitoring jndi:/server/Studi2/WEB-INF/faces-config.xml for modifications" 6) Make any relevant changes in faces-config, like adding a navigation rule like: <navigation-rule> <from-view-id>*</from-view-id> <navigation-case> <from-outcome>alunos</from-outcome> <to-view-id>/secure/alunos/index.xhtml</to-view-id> </navigation-case> </navigation-rule> 7) Check glassfish log, appears the following error: INFO: jndi:/server/Studi2/WEB-INF/faces-config.xml changed! INFO: Reloading JSF configuration for context /Studi2 INFO: Invalidating Session 656242834cbf2670a4e2a1004bcc SEVERE: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! java.util.concurrent.ExecutionException: java.lang.NullPointerException The complete log is attached to this issue ticket.
This issue would be related (or better, the root) of the problem: https://java.net/jira/browse/JAVASERVERFACES-2590
Targeting to 7.4.
Yes. this does not look like problem on NetBeans side. I'll keep this as P2 to check it more often for few weeks but I can't do much at this point.
Well, for me is enough if you can contact some Oracle folks to make some pressure to get this issue fixed... it is open for couple of months already, would be nice to get this fixed as soon as possible.
There seems to be some activity now.
Looks like this problem is not in GlassFish 4: INFO: Monitoring jndi:/server/WebJSF/WEB-INF/faces-config.xml for modifications INFO: Running on PrimeFaces 3.5 INFO: Loading application [WebJSF] at [/WebJSF] INFO: WebJSF was successfully deployed in 1,802 milliseconds. INFO: visiting unvisited references INFO: visiting unvisited references INFO: visiting unvisited references INFO: visiting unvisited references INFO: visiting unvisited references INFO: Initializing Mojarra 2.2.0 ( 20130502-2118 https://svn.java.net/svn/mojarra~svn/tags/2.2.0@11930) for context '/WebJSF' INFO: Monitoring jndi:/server/WebJSF/WEB-INF/faces-config.xml for modifications INFO: Running on PrimeFaces 3.5 INFO: Loading application [WebJSF] at [/WebJSF] INFO: WebJSF was successfully deployed in 1,567 milliseconds. Well, now I did the same on 3.1.2.2: INFO: Initializing Mojarra 2.1.6 (SNAPSHOT 20111206) for context '/WebJSF2' INFO: Running on PrimeFaces 3.5 INFO: Monitoring jndi:/server/WebJSF2/WEB-INF/faces-config.xml for modifications INFO: WEB0671: Loading application [WebJSF2] at [/WebJSF2] INFO: WebJSF2 was successfully deployed in 7,405 milliseconds. INFO: Initializing Mojarra 2.1.6 (SNAPSHOT 20111206) for context '/WebJSF2' INFO: Running on PrimeFaces 3.5 INFO: Monitoring jndi:/server/WebJSF2/WEB-INF/faces-config.xml for modifications INFO: WEB0671: Loading application [WebJSF2] at [/WebJSF2] INFO: WebJSF2 was successfully deployed in 1,483 milliseconds. And in both cases I did not see NPE in server logs.
Just to finally classify this on NetBeans side: 1) What happens after you do full deploy (right-click on project and select deploy)? 2) Is NetBeans deploy on save feature working correctly? We would like to know this to make sure there is no additional problem on NetBeans side.
After the error (I believe it is not either in NetBeans or Glassfish, but JSF Mojarra with CDI), I always get error 500 from server - even for deployments. So I have to stop glassfish and start it again. Regards, Edson
500 Internal Server Error A generic error message, given when no more specific message is suitable. This looks like something in server got broken and it's not able to process requests. But yes, this has nothing to do with NetBeans.
I am trying to validate that this does not happen with GF4 and NB 7.4. I could not reproduce it. Before I close this as a GF 3.1.2.2 bug, I wanted to make sure that I could produce the issue in a NB 7.4 deploying onto GF 3.1.2.2 environment. I could not. I doubt that something magical happened to fix this. I followed the steps and could not reproduce the issue. Is there something that you did not mention between step 2 and step 7? Can you attach a project that could be used to replicate the issue?
Some details about which values you selected for Libraries: * Server Library; version * registered libraries; version * a newly created library; details may be helpful, too.
(In reply to comment #10) > I am trying to validate that this does not happen with GF4 and NB 7.4. > > I could not reproduce it. > > Before I close this as a GF 3.1.2.2 bug, I wanted to make sure that I could > produce the issue in a NB 7.4 deploying onto GF 3.1.2.2 environment. > > I could not. > > I doubt that something magical happened to fix this. > > I followed the steps and could not reproduce the issue. Is there something > that you did not mention between step 2 and step 7? > > Can you attach a project that could be used to replicate the issue? I've a sample project, but it is 32Mb in size (already zipped), and cannot be attached here. How can I send it to you? Edson
(In reply to comment #11) > Some details about which values you selected for Libraries: > * Server Library; version > * registered libraries; version > * a newly created library; details > > may be helpful, too. I've tried default GF 3.1.1.2, and also with updated (latest stable) version of relevant libraries. Doesn't matter. Seems a GF problem with CDI. But I don't know how can I disable CDI in NetBeans project.
(In reply to comment #13) > (In reply to comment #11) > > Some details about which values you selected for Libraries: > > * Server Library; version > > * registered libraries; version > > * a newly created library; details > > > > may be helpful, too. > > I've tried default GF 3.1.1.2, and also with updated (latest stable) version of > relevant libraries. > > Doesn't matter. Seems a GF problem with CDI. But I don't know how can I disable > CDI in NetBeans project. Please, let me know how can I send the sample project to you. Regards, Edson
can you reproduce the issue with a smaller project... purpose built for demonstrating this issue? Have you removed any/all unnecessary bits (like classfiles, etc) from the project before you zipped it? Otherwise, can you post it someplace and send me a link to it?
Sure! Here http://www.knowledgespread.net.br/Studi2.zip
(In reply to comment #15) > can you reproduce the issue with a smaller project... purpose built for > demonstrating this issue? I think it is reproducible with any CDI enabled JSF project... but I'm not sure. This project is tiny (except for the PrimeFaces libs and themes). > > Have you removed any/all unnecessary bits (like classfiles, etc) from the > project before you zipped it? I've used NetBeans export to ZIP... I don't know what it exports or not... > > Otherwise, can you post it someplace and send me a link to it? The project is the same I've used to produce a video.
Here is the video with the issue in action: www.knowledgespread.net.br/Issue 2590.avi
OK. I used the attached project to replicate the error in a 7.4/3.1.2.2 dev/deploy environment. I could not reproduce the issue in a 7.4/4.0 dev/deploy environment. So, I am going to close this as FIXED.