We are close to finishing of testing of next patch for the NetBeans 6.1. It seems that the patch doesn't cause any regressions and fixes the bugs that it promised. Unfortunately, some of the bugs are almost unverifiable because they appear only in some unknown conditions. Anyway, we haven't found any regression during the testing that could be caused by the fixes.
The patch should be released on August 27 if there won't be any other issues reported by other teams. If you are not patient then you can try the patch now. On your own risk, of course. Add new update center and set up the URL field to this link. The updates will appear in the Plugin manager or in bubble.
Please, be aware of this bug when you are installing a patch - Bubble can install different set of update than via Plugins.
The patch should be released on August 27 if there won't be any other issues reported by other teams. If you are not patient then you can try the patch now. On your own risk, of course. Add new update center and set up the URL field to this link. The updates will appear in the Plugin manager or in bubble.
Please, be aware of this bug when you are installing a patch - Bubble can install different set of update than via Plugins.
I just tried to install these. It shows a bunch of new updates, I click install, it lists them again and I press Next. Then it tells me "Networking problem in: http://bits.netbeans.org/6.1/fixes/2008-08-12_03-59-31/uc/java2/org-netbeans-modules-java-kit.nbm" and wants me to check my proxy settings. I can download that file using Firefox so I'm not sure what's wrong. I'll just have to wait for the official release.
Posted by Ryan de Laplante on August 25, 2008 at 09:49 PM CEST #
When I tried to install other plugins such as Maven2 support I got the same error. I restarted the IDE then was able to install Maven2. Now patch 3 installed successfully. Now lets see if I can finally upgrade from 6.0.1 to 6.1 :) I've been waiting for an number of showstopper (to me) bug fixes that were sprinkled in patch 1, patch 2 and patch 3.
Posted by Ryan de Laplante on August 25, 2008 at 10:00 PM CEST #
Ok it's better (probably usable) now, but there's still something wrong. I have a J2EE 1.4 web project that has a servlet. The servlet uses a JAX-RPC web service client. I see the web service client generated classes are in /build/generated/ but the IDE shows red marks beside every line in my servlet that uses one of the generated files. It builds successfully, and clean/builds successfully. I can't use code completion in the servlet for the generated objects since it doesn't know where they are.
I've been waiting for 3 patch releases because of bugs in the JAX-RPC support that uses to work great in NB 6.0.
Posted by Ryan de Laplante on August 25, 2008 at 10:11 PM CEST #
The lack of code completion because of this regression really should be a P1 showstopper for patch 3. It was identified in March, I don't know why it still isn't fixed yet. http://www.netbeans.org/issues/show_bug.cgi?id=129645
Posted by Ryan de Laplante on August 26, 2008 at 02:53 PM CEST #
It is up to appropriate QA team to nominate bug to be fixed in a patch. That is pity that this issue didn't make into the patch3. The patch is almost ready for distribution therefore we won't add any new fixes into it. I'm sorry.
AFAIK, there is no plan for patch4 because the NB 6.5 should be released instead of it. We will continue to provide patches for the 6.5 , of course.
Ryan, make more noise next time about fixes that should go into a patch. Feel free to add me on CC of an issue when you need a help to get an issue into a patch. I expect that you know my issuezilla username (lhasik)
Posted by Lukas on August 26, 2008 at 04:56 PM CEST #
Thanks. I made a bunch of noise about my JAX-RPC issues before NB 6.1 was released, then after patch 1, after patch 2, and now just before patch 3. There were many issues that got fixed. I wasn't able to get this far without trying the new patch 3 fixes. Before it wouldn't even build the project. I figured when they fixed that they would have also tested that they don't get 500 errors in the editor and that code completion works.
Can you please make sure this is fixed in 6.5? I am not happy on 6.0, mainly because it is very slow compared to newer releases. If it is not fixed in 6.5 release I'm probably going to have to drop NetBeans and go with IntelliJ IDEA in the future.
I just found and reported some new [to me coming from 6.0.1] bugs:
http://www.netbeans.org/issues/show_bug.cgi?id=145166
I was excited to be able to have JAX-WS and JAX-RPC service clients in the same EJB 3.0 project. I can add the JAX-RPC client, but can't drag/drop the operation into my code window so it is useless!
http://www.netbeans.org/issues/show_bug.cgi?id=145155
HTTP monitor makes a lot of noise every time I access a page, and can't be turned off.
I was also excited about being able to expose some EJBs as JAX-WS web service endpoints, and others as JAX-RPC web service endpoints. When I tried to do this I found that I could only create JAX-WS endpoints. I don't know if this is a bug in NetBeans or a flaw in Java EE 5.
Posted by Ryan de Laplante on August 26, 2008 at 05:27 PM CEST #
I'm not a J2EE/JAX-RPC expert. I've forwarded your comment to the right people (i hope). They will hopefully comment on.
Posted by Lukas on August 26, 2008 at 05:42 PM CEST #
Hi,
some answers to raised questions:
re. IZ #145166 - d'n'd for JAX-RPC has never been implemented AFAIK, you can use call ws op action in the editor instead
re. JAX-RPC web services in EJB module - this was considered to be implemented but was dropped and only support for JAX-RPC ws clients has been added (mainly because of a lot of rpc/enc services around and limited support for them in JAX-WS and no time to work on web services part then)
re. networking problems: checking Plugins -> Settings -> Force install into shared directories usually gets me around it but really don't know why
regards,
--lj
Posted by Lukas Jungmann on August 26, 2008 at 11:22 PM CEST #
I had the same problem installing updates as Ryan (post august 25th). Few directories from http://updates.netbeans.org/netbeans/updates/6.1/uc/final/stable/modules/patch3 were empty. Then after a few refresh of the page they suddenly show some content. It works now.
Posted by Louis on September 04, 2008 at 04:47 PM CEST #
after I installed version 6.1 I can't opne it ( it shows a white screen after it loads). Any thoughts?
Posted by Harvey on September 05, 2008 at 05:36 AM CEST #
@Harvey: It happened when you started fresh NB 6.1 or after you applied a patch? Did you imported a old settings? What OS, JDK, etc. Is the main window started (or it hangs during startup?) ? Could you try to take thread dump - http://wiki.netbeans.org/GenerateThreadDump ? Please, create new bug in issuezila with all the info and add lhasik on CC. (O you can r send it to me if you don't want to bother with filling bug).
Posted by Lukas on September 05, 2008 at 11:39 AM CEST #
Saw the news about patch3 on the Start Page today and installed the upgrade immediately. Little I knew that all my webapps inside of the enterprise are all broken in the editor, and all the references to EJBs are no longer valid. I removed and added the dependency many times without any resolution. Like Ryan de Laplante, my application builds and runs fine. I don't know how this slipped through the QA crack, but I am reverting back to 6.1 fresh. I personally would not touch patch3 with a 10 foot pole.
Posted by Raymond Chen on September 05, 2008 at 05:47 PM CEST #
Raymond: regarding the broken editor, is this JAX-RPC related or something else? I haven't seen references to EJBs being broken. Make sure to file bug tickets with enough detail so they can fix the problem. Obviously they have not seen that behavior before.
Posted by Ryan de Laplante on September 05, 2008 at 05:51 PM CEST #
@Raymond: I forwarded you complains to responsible team. As it is Friday afternoon in Prague, please be patient with an answer :(
Could you be more specific? Screenshots, exceptions, more details?
ASFAIK, there were only folowing bugs fixed in J2EE area
137071 User library definitions are removed from nbproject/private/private.properties on startup
132513 Cant' add valid J2EE modules as Library in Enterprise app
134632 Can't change "path in WAR" for additional WAR content specified on Build/Packaging
134640 When adding shared libraries folder to existing Visual Web app, it causes unresolved dependencies
134633 Regression: Packaged archive is broken/unusable in NB 6.1
134900 ClassCastException when making project sharable
134452 libs.*.classpath.libfile properties appear in project.properties instead of build.properties
Full list at http://wiki.netbeans.org/NetBeans6.1PatchesInfo
None of the fixes seems to be related to the area where your problem appeared. Please, fill new issue about it with as much details as possible before you reinstall it - http://www.netbeans.org/issues/enter_bug.cgi?component=j2ee
Posted by Lukas on September 05, 2008 at 06:02 PM CEST #
Thanks for for all the suggestions. I am going to try to reproduce the problem on a simple project, as my EAR is quite large and complicated. It originated back to NB 6.0 and survived many patches. I just tried a HelloWorld enterprise app, and it seems to be okay on a Visual JSF page calling EJB. Let me throw other stuff at it until I can reproduce the problem and make a meaningful bug report.
Ryan, my problem could be JAX-RPC related, as I do expose an EJB as a web service. It seems odd, as the problem only happens after patch3. The best description is that all my code-behinds for VJSF can longer reference anything in the EJB jar while in the editor. Again, it builds and runs great.
Posted by Raymond Chen on September 05, 2008 at 06:52 PM CEST #
Raymond: I wasn't able to reproduce your problem regarding EJBs. Please file a new issue with more details. You can use URL mentioned above. Thanks.
Posted by Honza on September 09, 2008 at 09:45 AM CEST #
I'm seeing the same thing - the libraries/dependencies in my project (Java Library) don't seem to be recognized by the editor and the code is littered with "package does not exist" errors. The project builds fine however.
Posted by Steve Shaw on September 10, 2008 at 04:52 PM CEST #
@Steve: Unfortunately, it is know bug. Rebuild your project should help. If not then only restart can save you. :(
Posted by Lukas Hasik on September 11, 2008 at 10:03 AM CEST #
@Lukas: Thanks, unfortunately restarts are no good - it's broken. Do you know which plugins are at fault so I can roll them back? Also, are there plans for a quick fix?
Posted by Steve Shaw on September 11, 2008 at 02:42 PM CEST #
Well, I can't reproduce the problem from the ground up, but it seems to be related to that particular EJB jar. That jar just couldn't be used in patch3, and no new project can recognize any import from it. Dependency injection does not work either on that jar but do throw the exception below:
SEVERE [global]
java.lang.NullPointerException
at org.netbeans.modules.java.source.builder.TreeFactory.QualIdent(TreeFactory.java:546)
at org.netbeans.api.java.source.TreeMaker.QualIdent(TreeMaker.java:757)
at org.netbeans.modules.j2ee.ejbcore._RetoucheUtil$3.run(_RetoucheUtil.java:194)
at org.netbeans.modules.j2ee.ejbcore._RetoucheUtil$3.run(_RetoucheUtil.java:171)
at org.netbeans.api.java.source.JavaSource.runModificationTask(JavaSource.java:915)
at org.netbeans.modules.j2ee.ejbcore._RetoucheUtil.generateAnnotatedField(_RetoucheUtil.java:170)
at org.netbeans.modules.j2ee.ejbcore.action.CallEjbGenerator.generateInjection(CallEjbGenerator.java:307)
at org.netbeans.modules.j2ee.ejbcore.action.CallEjbGenerator.generateReferenceCode(CallEjbGenerator.java:234)
at org.netbeans.modules.j2ee.ejbcore.action.CallEjbGenerator.addReference(CallEjbGenerator.java:149)
at org.netbeans.modules.j2ee.ejbcore.ui.logicalview.entres.CallEjbDialog.open(CallEjbDialog.java:147)
at org.netbeans.modules.j2ee.ejbcore.ui.logicalview.entres.CallEjbAction.performAction(CallEjbAction.java:75)
at org.openide.util.actions.NodeAction.performAction(NodeAction.java:289)
at org.openide.util.actions.CallableSystemAction$1.run(CallableSystemAction.java:118)
at org.netbeans.modules.openide.util.ActionsBridge.doPerformAction(ActionsBridge.java:77)
at org.openide.util.actions.CallableSystemAction.actionPerformed(CallableSystemAction.java:114)
at org.openide.util.actions.NodeAction.actionPerformed(NodeAction.java:277)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1220)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1261)
at java.awt.Component.processMouseEvent(Component.java:6041)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
at java.awt.Component.processEvent(Component.java:5806)
at java.awt.Container.processEvent(Container.java:2058)
at java.awt.Component.dispatchEventImpl(Component.java:4413)
at java.awt.Container.dispatchEventImpl(Container.java:2116)
at java.awt.Component.dispatchEvent(Component.java:4243)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
at java.awt.Container.dispatchEventImpl(Container.java:2102)
at java.awt.Window.dispatchEventImpl(Window.java:2440)
at java.awt.Component.dispatchEvent(Component.java:4243)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
[catch] at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Posted by Raymond Chen on September 11, 2008 at 06:33 PM CEST #
Raymond: May I kindly ask you to file a bug in issuezilla? If you can reproduce this exception please use the Exception Reporter dialog. Thanks
Posted by Honza on September 11, 2008 at 06:45 PM CEST #