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.
Can't deploy web project with jsf2.2. Create new web project with selected jsf framework with selected "registered library" - jsf 2.2. Try to deploy. fail with: <29.05.2013 14:06:19 MSK> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\Users\sp153251\AppData\Local\Temp\WebApplication34\build\web. Ensure that the annotations are valid. The error is null> <29.05.2013 14:06:19 MSK> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID "1369821978010" for task "17". Error is: "weblogic.application.ModuleException: java.lang.NullPointerException" weblogic.application.ModuleException: java.lang.NullPointerException at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
It seems to me that your WebLogic is not JSF2.2 ready yet. But it doesn't look to me like NB issue, sorry. Are you able to deploy it i.e. using admin console?
>It seems to me that your WebLogic is not JSF2.2 ready yet should it be suggested as valid selection in this case?
Also 2.1.20 seems to be included with webloic distribution but I got no options for this version, it may be something wrong with weblogic plugin if it do not discover 2.1.20 and report 2.2 as supported. Will reverify tomorrow.
(In reply to comment #2) > >It seems to me that your WebLogic is not JSF2.2 ready yet > should it be suggested as valid selection in this case? I think that the valid selection is offered by using "server libraries" as default. (In reply to comment #3) > Also 2.1.20 seems to be included with webloic distribution but I got no options > for this version, it may be something wrong with weblogic plugin if it do not > discover 2.1.20 and report 2.2 as supported. Will reverify tomorrow. If it's not offered there and should be, it can be issue in the WL or in the JSF support too. I'm going to investigate it more tomorrow and reassign it on appropriate component. Please, do you have WL12.1.2 you mentioned in the private email to me? (I would like to check exactly your use case) Thanks.
My resolution is following... it's WebLogic issue. WL we spoke about doesn't have the JSF 2.1 on the server classpath or better to say it has but with wrong path to the JAR. I was able to reproduce your NPE issue, it's some WL issue which we are not likely able to handle (would be better to report it to WL). About the problem of the JSF server libraries offer. The classpath is created besides other on base of the api.jar classpath. This .jar contains path to "wlserver/modules/javax.jsf_1.0.0.0_2-1.jar" which is completely wrong since the real JSF2.1 jar is at "wlserver/modules/glassfish.jsf_1.0.0.0_2-1-20.jar". I'm going to report it to WL bug tracking system and closing this issue as wontfix for now since the fix should happen on side of the WL server. In any case thanks a lot for pointing to such issue!
Entered WLS bug: https://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=16883058
> WL we spoke about doesn't have the JSF 2.1 on the server classpath Sorry Martin I don't understand, so is there issue with JSF 2.2 or 2.1? I understand that JSF 2.2 is probably not supported by WLS 12.1.2, so from this point of view I agree with the WONTFIX resolution. But is there an additional user-visible problem with JSF 2.1? When I am trying this out, I see that JSF 2.1 is the preselected default, and deployment of web project which uses JSF 2.1 (both Ant and Maven based) succeeds. But if there is a user-visible problem with JSF 2.1, then it should be filed as a separate bug.
(In reply to comment #7) > > WL we spoke about doesn't have the JSF 2.1 on the server classpath > > Sorry Martin I don't understand, so is there issue with JSF 2.2 or 2.1? I > understand that JSF 2.2 is probably not supported by WLS 12.1.2, so from this > point of view I agree with the WONTFIX resolution. Yeah, this reported problem is about JSF2.2 with WLS 12.1.2. > But is there an additional user-visible problem with JSF 2.1? When I am trying > this out, I see that JSF 2.1 is the preselected default, and deployment of web > project which uses JSF 2.1 (both Ant and Maven based) succeeds. But if there is > a user-visible problem with JSF 2.1, then it should be filed as a separate bug. The "user-visible" problem of the latest WLS build is that there is no JSF2.1 server library offered in JSF panel. The reason/evaluation I described in the comment #5 - the classpath defined in the WLS's api.jar is wrong (which is WebLogic issue). If you would like to have this reported as separated NB bug let me know and I can do that - I didn't do that for now since we will open issue with link to WLS one and then close once the WLS issue will be fixed again.
even it was reported as 2.2, I agree with won't fix as 2.1 should be provided instead by default and it's wl issue. But it may have sense to filter out unsupported libraries from registred libraries or if possible use these libraries with restrictions. for example it may be possible to select eclipsleink jpa 2.1 library but if server report jpa 2.0 as latest one persistence.xml will be created with version 2.0 (at least it's expected behavior). it may be filed as separate P3 issue/enhancement.
and thanks for evaluation and wl issue.
> here is no JSF2.1 server library offered in JSF panel. Ok, it turns out that this problem is only visible when using the universal installer. When using the zip build, JSF 2.1 server library *is* offered. Although this is clearly a WebLogic issue, I wonder if we could provide a workaround/hack on the NetBeans side, i.e. add JSF 2.1 server library as an option to the wizard, even if it is not detected correctly via the api.jar file. Martin/Petr, what do you think?
(In reply to comment #9) > But it may have sense to filter out unsupported libraries from registred > libraries or if possible use these libraries with restrictions. Sorry Sergey, but I'm afraid that it could more troubles bring than resolve. Let's suppose that it's only some WLS issue which will be fixed in WLS patch but NetBeans will still not offer the library. Also the default setup of the wizard will be correct (once WLS ClassPath issue will be fixed) so I'm not fan of this idea, sorry. (In reply to comment #11) > Although this is clearly a WebLogic issue, I wonder if we could provide a > workaround/hack on the NetBeans side, i.e. add JSF 2.1 server library as an > option to the wizard, even if it is not detected correctly via the api.jar > file. Martin/Petr, what do you think? It will require fixing/hacking of the WLS classpath. As we agreed on that offline, I'm entering issue for such scenario. If the WLS issue I entered today will be fixed in final build, we will close the issue. If not we should probably workaround that inside weblogic module: https://netbeans.org/bugzilla/show_bug.cgi?id=230522 Thanks guys for comments.