Fri, 22 Jun 2007 17:35:16 +0000#107754 Fixing possible NPE because of null listener. release60-m10_base update_of_anna_on_20070710_root
pzavadsky@netbeans.org [Fri, 22 Jun 2007 17:35:16 +0000] rev 979
#107754 Fixing possible NPE because of null listener.

Fri, 22 Jun 2007 17:27:52 +0000- added error code
am111535@netbeans.org [Fri, 22 Jun 2007 17:27:52 +0000] rev 978
- added error code

Fri, 22 Jun 2007 15:58:07 +0000- added line to stop the "visualweb" domain before removing glassfish
am111535@netbeans.org [Fri, 22 Jun 2007 15:58:07 +0000] rev 977
- added line to stop the "visualweb" domain before removing glassfish

Fri, 22 Jun 2007 15:48:07 +0000Bug Fix# 107717 IllegalStateException after refactor; ide hang
sandipchitale@netbeans.org [Fri, 22 Jun 2007 15:48:07 +0000] rev 976
Bug Fix# 107717 IllegalStateException after refactor; ide hang

IllegalStateException was happening only for page fragments. It was because during sync(),
the MarkupUnit.ensureAttributeValue() is called to ensure the value of id attribute
of the subview element is the name (sans extension) of the File. This happens
in the sync()->bind() sequence that results due to the fileRenamed() event
that is fired by Rename refactroing. The refactoring should take care of renaming the
sub view id for page fragments.

Another issue that has been fixed is that the SourceUnit was unable to remove the
PropertyChangeListener on the EditorCookie in the destroy() method after a move refactoring.
This meant that it kept on reacting to the document opened/closed property change events long
after it was logically destroyed. This was happening because it was using the old FileObject
to lookup a DataObject to in turn get the EditorCookie to remove the listener. However a null
DataObject was returned for the old FileObject. Fixed this by caching the EditorCookie in a
member field and using it to remove PropertyChangeListener. This probably started happening
after we switched to OperationListener (DataObject level) from the FileChangeListener based
management of FacesModels. This may fix some other wierd NPEs on editor close.

Added some code to protect against NPEs.

Removed code to refactor the managed-bean-class tag as the web/jsf refactoring takes care of it now.

Some preparatory code to handle web/**folder level move and rename refactoring.

Fri, 22 Jun 2007 14:53:38 +0000Removing unneeded dependency
abadea@netbeans.org [Fri, 22 Jun 2007 14:53:38 +0000] rev 975
Removing unneeded dependency

Fri, 22 Jun 2007 01:03:18 +0000#107558 Datasources not imported when Creator Settings are migrated on first IDE Run
jbaker@netbeans.org [Fri, 22 Jun 2007 01:03:18 +0000] rev 974
#107558 Datasources not imported when Creator Settings are migrated on first IDE Run

fix an NPE introduced in the previous integration

Fri, 22 Jun 2007 00:42:06 +0000107000 unwanted "lib" folder created for every opened/created project
edwingo@netbeans.org [Fri, 22 Jun 2007 00:42:06 +0000] rev 973
107000 unwanted "lib" folder created for every opened/created project

Fri, 22 Jun 2007 00:17:04 +0000#107558 Datasources not imported when Creator Settings are migrated on first IDE Run
jbaker@netbeans.org [Fri, 22 Jun 2007 00:17:04 +0000] rev 972
#107558 Datasources not imported when Creator Settings are migrated on first IDE Run

for Creator 2, no drivers had been registered even though JDBCDriver manager
fired a JDBCDrivers change event.

Fri, 22 Jun 2007 00:06:56 +0000Partial fix for: 107000 unwanted "lib" folder created for every opened/created project
edwingo@netbeans.org [Fri, 22 Jun 2007 00:06:56 +0000] rev 971
Partial fix for: 107000 unwanted "lib" folder created for every opened/created project
Two other visualweb modules may need to be fixed also.

Thu, 21 Jun 2007 22:42:14 +0000Added javax.xml.soap.MessageFactory system property to jax-rpc web service client, fixing runtime exceptions when deploying to a server running on JDK 6
quynguyen@netbeans.org [Thu, 21 Jun 2007 22:42:14 +0000] rev 970
Added javax.xml.soap.MessageFactory system property to jax-rpc web service client, fixing runtime exceptions when deploying to a server running on JDK 6