Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
JTree - Saving Changes
- Thread starter chris921
- Start date
There is quite a lot of scope to that question. It depends on the application. If the JTree is displaying information from some database, then changes in the tree structure should naturally be persisted back to the database. Ditto for a file.
However, you may want to persist the tree model as a serialised object. You could persist a DefaultTreeModel as a serialised object (as a binary object file or XML file, check out java.beans.XMLEncoder and XMLDecoder). It depends on what you're trying to achieve.
Tim
---------------------------
"Your morbid fear of losing,
destroys the lives you're using." - Ozzy
However, you may want to persist the tree model as a serialised object. You could persist a DefaultTreeModel as a serialised object (as a binary object file or XML file, check out java.beans.XMLEncoder and XMLDecoder). It depends on what you're trying to achieve.
Tim
---------------------------
"Your morbid fear of losing,
destroys the lives you're using." - Ozzy
- Thread starter
- #3
stefanwagner
Programmer
Well - but your file isn't a tree.
It depends, how you create a tree from the file. Depending on that, you have to save the tree.
seeking a job as java-programmer in Berlin:
It depends, how you create a tree from the file. Depending on that, you have to save the tree.
seeking a job as java-programmer in Berlin:
Chris921, the tree is only a means of displaying/manipulating data. Your most recent post is merely stating the obvious. Deciding how to persist the information depends upon other things:-
1) How much data are we talking about?
2) Does the data need long-term storage or not?
3) Is there any other data (not part of the tree) which belongs in the problem space?
4) Is the application purely a 'stand-alone' app or one which many users on a network will use?
5) Will many users want to access the same data?
... and so on.
In other words, yes we could provide a concrete example of how you would persist the data in your tree, but without details from you it may not be an appropriate approach.
Tim
---------------------------
"Your morbid fear of losing,
destroys the lives you're using." - Ozzy
1) How much data are we talking about?
2) Does the data need long-term storage or not?
3) Is there any other data (not part of the tree) which belongs in the problem space?
4) Is the application purely a 'stand-alone' app or one which many users on a network will use?
5) Will many users want to access the same data?
... and so on.
In other words, yes we could provide a concrete example of how you would persist the data in your tree, but without details from you it may not be an appropriate approach.
Tim
---------------------------
"Your morbid fear of losing,
destroys the lives you're using." - Ozzy
- Status