Thread safe cache implementation
Your cache can only be initialised once with the put method (hence your set flag): why not use a constructor instead and get rid of the flag?
If 2 items with the same UUID are identical and you only need to store one of them, using a map would simplify your design a lot
The map gives you an O(1) algorithm for contains and getById instead of O(n) in your code
Since the class is now immutable, you don't need to synchronize the methods any more which should result in much better result in case of heavy concurrency (no lock contention)


Here is what I would propose:

public class StaticCacheImpl&lt;T extends Entity&gt; implements StaticCache&lt;T&gt; 
{
    //Assumes that 2 items with the same UUID only need to be stored once
    private final Map&lt;UUID, T&gt; cache = new HashMap&lt;UUID, T&gt;();

    public StaticCacheImpl(List&lt;T&gt; cachedList) {
        for (T t : cachedList) {
            cache.put(t.getUuid(), t);
        }            
    }

    @Override
    public boolean isSet() {
        return true;
    }

    @Override
    public void put(List&lt;T&gt; cachedList) {
        throw new IllegalStateException("Cache has already been set");
    }

    @Override
    public List&lt;T&gt; get() {
        return new ArrayList&lt;T&gt; (cache.values()); //defensive copy
    }

    @Override
    public boolean contains(UUID uuid) {
        return cache.containsKey(uuid);
    }

    @Override
    public T getById(UUID uuid){
        return cache.get(uuid);
    }
}


If you can't use a constructor and need the put method to work as in your original design, then the only change I would make is to use a map, but you would still need to synchronize the methods and use the set flag.