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.
Create Web Project for Weblogic and select JSF Framework with default server library (2.0). Expand Weblogic node under Libraries once the project is created and you will find there between other jars: javax.jsf_1.0.0.0_1-2 (at the top) javax.jsf_1.0.0.0_2-0 (at the end) Similarly for Weblogic JSF version 1.2 the same jar is on classpath twice.
The reason is that jars (at the top) are referenced by manifest in api.jar (as well as many other apis). I can manually filter them, but we should file an issue for the WL I guess. Does anybody has access to their IZ?
Does WL documents/suggests somewhere to use api.jar? We do not have to use it, do we? Are you also saying that api.jar should not include any of the WL server libraries? I would agree with that. And perhaps I even have access to their bugzilla though have not tried it yet and I'm not that keen on trying to find it. :-)
(In reply to comment #2) > Does WL documents/suggests somewhere to use api.jar? Not sure about that. The weblogic.jar was used in order to develop apps (it contained the api such as servelet API etc). In Weblogic 10 it was modularized. Now it is api.jar referencing the spec jars from manifest. > We do not have to use it, > do we? No but I think the whole purpose of api.jar is to provide the Java EE 5 to the developer. > Are you also saying that api.jar should not include any of the WL server > libraries? I would agree with that. It shouldn't and it doesn't. The jsf jars referenced from api.jar are not part of any library. > And perhaps I even have access to their > bugzilla though have not tried it yet and I'm not that keen on trying to find > it. :-) Would be great if you could report it. In worst case it will be closed as invalid ;) There is one more issue I had with api.jar which I had to solve manually. It does not contain reference to javax.persistence libs. BTW it is not just javax.jsf, glassfish.jstl is duplicated as well.
But if api.jar is representation of EE 5 APIs then it is correct to contain JSF1.2, no? It is only problem when user decides to use JSF2 for example - in such case jsf2 should be on classpath before jsf12. So what exactly is bug on WL side I should file? Renaming api.jar to JavaEE5APIs.jar would be good idea.
This is still valid issue which might have negative side effects. Would be worth to fix for M1 maybe?
I originally thought the jsf should be filtered out, but it would not be correct for jstl. So I'm just adding all libraries in front of the standard server apis which is imo correct in general. web-main 51808a257818.
BTW Now I think the api.jar should reference all standard apis in Java EE, including jsf. In such case the bug on WebLogic side is that it does not reference javax.persistence and we have to work around it and search for it manually in serverplugin.
Integrated into 'main-golden', will be available in build *201008180001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/51808a257818 User: Petr Hejl <phejl@netbeans.org> Log: #188753 WL classpath node shows several JSF jar versions