Suppai
asked on
Does a Java Conversion method from ListModel (DefaultListModel) to Vector exist?
I was wondering if a methods as mentioned in subject exist in the Java API? It is not that I can't create a loop that does the trick pretty easily, but I like to use the Java API as much as possible.
no and even you can't convert them!
sorry that should be:
Vector v = new Vector(Arrays.asList(listm
Vector v = new Vector(Arrays.asList(listm
or if you just want a List
List list = Arrays.asList(listmodel.to
List list = Arrays.asList(listmodel.to
ASKER
I actually found out about the v.copyInto(dlm.toArray()),
does not matter what type if objects are in the list
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ahh I didnt make myself clear I want it to be converted to a Vector<String> and then it seems to matter, at least my editor thinks so. I want to make sure that the vector contains only Strings in order to avoid exceptions later on in the application.
if a Vector parameterezied with String, it can't take Object!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Easy enough write though, would just be a simple loop.
Let me know if you need a hand :)
Let me know if you need a hand :)
With a utility method you'd get the added advantage that it would work with *any* ListModel.
So if you wanted a Vector specifically for some reason, you could just do
Vector v = new Vector(collectionsNiceListModel);
ASKER
Nice class, but maybe a little overkill for my school project:-) Yes an utility function would be good, I guess it is just a matter if identifying the class of the elements one by one in the loop and taking action if theyre not strings. However ended up realizing that i had taken care of the String checking otherwhere in the application so thorough handling of non-Strings was never necessary...but of course it is always good code to handle everything to increase re-usability I know:-)
:-)
Using a custom list model is unnecessary and just adds another (messy) class to maintain.
Not to mention that all that code does is what the simple loop I described would do just with a lot less code. It doesn't do anything that the existing model classes don't already do.
Not to mention that all that code does is what the simple loop I described would do just with a lot less code. It doesn't do anything that the existing model classes don't already do.
Vector v = new Vector(listmodel.toArray()