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.
As discussed in bug 225554 (comments 1,3,5,6), we may want to update Java EE jar included in module javaee.api to the EE 7 version. Let's move the discussion to this issue, as that's a separate problem from bug 225554 (EE 7 Javadoc).
Copying my opinion from the bug #225554: Optimal would be to include into the projects version of the EE API corresponding to the EJB/WEB EE platform level. If you would agreed on including EE7 library also into EE6 projects (to spare some place) it's OK then. But my vote is for bundling both of them.
Would not the easiest choice be to simply add a new javaee-web-api-7.0 library? And change the code to add correct library based on project's Java EE level?
(In reply to comment #2) > Would not the easiest choice be to simply add a new javaee-web-api-7.0 library? > And change the code to add correct library based on project's Java EE level? I think that we have agreement here. Sorry, if my comment #1 doesn't sound so. :)
I agree that would be easiest, the question is whether we still need EE 6 and how important it is. If you say that there are compelling reasons to include EE 6, then let's do it that way. Also, in the future Oracle Cloud may be updated to EE 6, and at that point the Cloud plugin will need a Java EE 6 API to compile against (in case you are not using a local WebLogic 12 server), correct?
You are correct Petr. In the past we gave user only the latest EE jar version, that is EE6 jar even for EE5 project. While we could do the same with EE7 I think it would be better to distinguish them. I'm not sure that's a compelling reason enough.
I've created javaee7.api in web-main 4ea065cba653. There are two minor problems. Davide, where are those endorsed jars coming from (where one can download them)? Are these still needed. For now the corresponding lib definition is commented out. Second thing is the api jars are not available in maven repo. Is this something Milos should do once java ee 7 is finished?
(In reply to comment #6) > > Second thing is the api jars are not available in maven repo. Is this something > Milos should do once java ee 7 is finished? Not me, that's something the glassfish/javaee team should do (as they have done before)
(In reply to comment #6) > Davide, where are those endorsed jars coming from (where one can download > them)? Are these still needed. For now the corresponding lib definition is > commented out. They are not needed. The EE6 spec updated two jars which are part of Java SE6 and so we had to bundle them separately and place them on endorsed classpath. So far this is not needed for EE7.
Ok, closing as fixed.
> Second thing is the api jars are not available in maven repo. Not sure I fully understand this comment, but milestone builds of both API jars and endorsed jars are published here: https://maven.java.net/content/groups/promoted/javax/ >> Davide, where are those endorsed jars coming from (where one can download them)? > They are not needed. I must say I am still confused by all the endorsed stuff. But the truth is that in GF 4 there is directory modules/endorsed, which contains 3 jars, so I guess there is a reason for that? We may not have come across a scenario when these would be used, but does it really mean there are never used? I can imagine that in some JAX-WS scenarios you may need them.
Arun, do you know if EE7 requires newer versions of some SE7 jars? Just like EE6 did? (In reply to comment #10) > I must say I am still confused by all the endorsed stuff. But the truth is that > in GF 4 there is directory modules/endorsed, which contains 3 jars, so I guess > there is a reason for that? We may not have come across a scenario when these > would be used, but does it really mean there are never used? I can imagine that > in some JAX-WS scenarios you may need them. The definitive answer is to look at table EE.6-1 in EE 7 spec and which versions of individual Java technologies are required and compared those to one available in Java SE 7 (which I cannot find anywhere in some simple comprehensible table!). Anything which is in SE and is needed in EE in higher version will have to be placed automatically on endorsed classpath of javac. For SE 6 it was JAXB, Common Annotations and Web Services. For SE7 I cannot find the list of versions so I cannot answer your question definitely. The jars in GF look like the same jars in GF3.