Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / GUI / June 2007

Tip: Looking for answers? Try searching our database.

NetBeans - Refactor killed my custom components.

Thread view: 
ImLurkingHere@gmail.com - 29 Jun 2007 02:08 GMT
I'm working on a program in the NetBeans IDE. I have a few components
that I've created, and added to the design pallet.

Today, I decided to reorganize my code a bit, and renamed the default
package where most of my source is kept. After re-naming and
refactoring the code, I opened up one of my forms, to discover that
all of my compontents were "invalid". In some forms it gives me errors
about loading the properties of the various components. The components
were added from the project, not from a JAR, if that makes any
difference.

I tried "reload form" in the source browser, but it doesn't work :(.

Any suggestions? I really don't feel like starting over. I'm using
NetBeans 5.5.

Thanks.
Andrew Thompson - 29 Jun 2007 04:23 GMT
>I'm working on a program in the NetBeans IDE. I have a few components
>that I've created, and added to the design pallet.

Note this is an IDE/java problem (but mostly IDE).
It is not so much a 'GUI' question.

>Any suggestions? I really don't feel like starting over. I'm using
>NetBeans 5.5.

Stop using NetBeans until you can code both
basic Java, and are relatively proficient in writing
GUI code.

The basic problem here, I guess, is that the NetBeans
form definition is still expecting the old packge names
(or lack of them).  But that is between you, and your
IDE.

Signature

Andrew Thompson
http://www.athompson.info/andrew/

ImLurkingHere@gmail.com - 29 Jun 2007 04:53 GMT
> Note this is an IDE/java problem (but mostly IDE).
> It is not so much a 'GUI' question.

Sorry, I'll keep that in mind.

> The basic problem here, I guess, is that the NetBeans
> form definition is still expecting the old packge names
> (or lack of them)

Well, that prompted me to try and open up the .form file used by
NetBeans, and I'm in luck. It's an XML document, so I can change the
class references in the form to point to the new packages.

Thanks for the (slightly indirect) help!
Andrew Thompson - 29 Jun 2007 06:52 GMT
..
>> The basic problem here, I guess, is that the NetBeans
>> form definition is still expecting the old packge names
>> (or lack of them)
>
>Well, that prompted me to try and open up the .form file used ..

Aha!  Well, if you are going to add that level of common
sense to the use of the IDE while learning Java, it might
be possible to circumvent or work around the hazards I
expected would hinder the project!

>...by
>NetBeans, and I'm in luck. It's an XML document, ...

Yeah.  NB is relatively sensible that way.  The project
files are either ant based build.xml's, or NB's own (AFAIR)
internal project files are also XML based.

If something goes wrong with a build or run
(it will) those are the the most common files to
look into.

>..so I can change the
>class references in the form to point to the new packages.

Glad you sorted it.

>Thanks for the (slightly indirect) help!

Your ability to sort the problem from the hint,
and willingness to report back, was more than
enough thanks.

Signature

Andrew Thompson
http://www.athompson.info/andrew/



Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.