Skip to main content

Arrays.asList() throws java.lang.UnsupportedOperationException

Arrays.asList() throws java.lang.UnsupportedOperationException

You might get the UnsupportedException when you tries to use the add() method in the List.

If your code looks something similar to this :

String[] data = new String[] {"hari","krushna"};
List<String> asList = Arrays.asList(data);
asList.add("test");

Then you will see the following exception :

java.lang.UnsupportedOperationException
at java.util.AbstractList.add(Unknown Source)
at java.util.AbstractList.add(Unknown Source)
at ArrayConvert.trial(ArrayConvert.java:14)
at ArrayConvert.main(ArrayConvert.java:8)



Solution of the above problem is :
 you need to create an ArrayList or LinkedList and add the objects to the newly created Array/LinkedList:

String[] data = new String[] {"","",""};
List<String> asList = Arrays.asList(data);
List<String> newList = new LinkedList<>(asList);
newList.add("test");

Reason for the UnsupportedOperationException:

Arrays.asList Method is returning a sub class object of Arrays class : java.util.Arrays.ArrayList

Following is the signature of the class :

private static class ArrayList<E> extends AbstractList<E> implements RandomAccessjava.io.Serializable

Here ArrayList extends java.util.AbstractList class.

Following are the add() method in AbstractList:

public boolean add(E e) {
 add(size(), e);
 return true;
}

public void add(int index, E element) {
  throw new UnsupportedOperationException();
}

As you see above add() method is not implemented, so when add() method is called directly from asList() object then it will throw an Exception.

This will be Runtime exception so difficult to identify at the time of coding. 




Comments

Popular posts from this blog

Could not launch the product because the associated workspace is currently in use by another Eclipse application

If you are seeing following error at the beginning of the Eclipse or any RCP based product then here is the solution: Error Message: "Could not launch the product because the associated workspace is currently in use by another Eclipse application." or “Workspace in use or cannot be created chose a different one.” Solution :  go to workspace location remove file <workspace location>/.metadata/.lock Reason: Through eclipse, user can create multiple Workspace locations. One Workspace location can be edited by one user at a time. A workspace contains the data related to various project configuration and local file storage. To avoid multiple users to access the same workspace, eclipse is maintaining a ".lock" file inside the Workspace. Eclipse will remove this ".lock" file when you will close the Eclipse. But in some cases, the Eclipse will crash due to some error, due to which it could not able to remove ".lock" file from

HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException

HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException If you get following error while connecting to your Database with Spring boot, try the suggested solution below: 2018 - 11 - 25 15 : 28 : 50.078 INFO 5335 --- [ main] o. h . e . j . e . i . LobCreatorBuilderImpl : HHH000424: Disabling contextual LOB creation as createClob() method threw error : java. lang . reflect . InvocationTargetException java. lang . reflect . InvocationTargetException : null at sun. reflect . NativeMethodAccessorImpl . invoke0 (Native Method) ~[na: 1.8 . 0 _161] at sun. reflect . NativeMethodAccessorImpl . invoke (NativeMethodAccessorImpl. java : 62 ) ~[na: 1.8 . 0 _161] at sun. reflect . DelegatingMethodAccessorImpl . invoke (DelegatingMethodAccessorImpl. java : 43 ) ~[na: 1.8 . 0 _161] at java. lang . reflect . Method . invoke (Method. java : 498 ) ~[na: 1.8 . 0 _161] at org. hibernate . engin

Use these Eclipse RCP Testing tools before your code goes to LIVE

Use these Eclipse RCP Testing tools before your code goes to LIVE Testing is most important part of any software development lifecycle. There are different type of testing required before Eclipse RCP tool is released to productions. Eclipse RCP is very easy to test with the these testing tools: UI Testing: RCP Testing Tool RCP Testing Tool is a project for GUI testing automation of Eclipse-based applications. RCPTT is fully aware about Eclipse Platform's internals, hiding this complexity from end users and allowing QA engineers to create highly reliable UI tests at great pace. SWT Bot SWTBot is an open-source Java based UI/functional testing tool for testing SWT, Eclipse and GEF based applications.  SWTBot provides APIs that are simple to read and write. The APIs also hide the complexities involved with SWT and Eclipse. This makes it suitable for UI/functional testing by everyone, not just developers. SWTBot also provides its own set of ass