Skip to main content

Java: Generics dont keep it simple stupid

So I was playing around with generics (dont love them because of type erasure - class level is ok method level gets scary) the other day and here are some examples and lessons learned:

1) Method level generics with return types are harder than they look.
2) Wildcards and when to use them confuse me.
3) My code is ugly and I must be missing something but what - who knows.


What I wanted was a Singleton class with generic get and put methods (what you put in is what you get out) without the cast. Something that works a little like Collections.emptyList();


The map I was storing my generic stuff in  ignore the naming for now:

What I wanted to do is something like this:

CacheItem<AnItem>  someCacheItem  = new DateCacheItemImpl<AnItem>();

Cache.getInstance().register(NameCacheItem.class);
Cache.getInstance().put(someCacheItem);

CacheItem<AnotherItem>  anotherCacheItem  = Cache.getInstance().get();



private ConcurrentHashMap<String, CacheItem<? extends ParentItem>> cacheMap =
  new ConcurrentHashMap<String, CacheItem<? extends  Parent Item>>();

public <T extends CacheItem<? extends  ParentItem >> void put(T cacheInstance) {

    cacheMap.put(cacheInstance.getCacheKey(), cacheInstance);
}

public <T extends CacheItem<? extends  ParentItem>> T get(String cacheKey) {
    return (T)cacheMap.get(cacheKey);
}

    public <T extends CacheItem<? extends  ParentItem >> void registerCache(Class<T> clazz) {

        try {
            CacheItem<? extends  ParentItem  > cacheInstance = clazz.newInstance();
            put(cacheInstance);
        } catch (InstantiationException e) {
            LOGGER.warning("Unable to create cache " + clazz.getName());
        } catch (IllegalAccessException e) {
            LOGGER.warning("Unable to create cache " + clazz.getName());
        }
    }


Not exactly what I wanted, will update this post once I have a epiphany.

Comments

Popular posts from this blog

ADF sort of generic screen for tables with the same structure

We have a couple (about a hundred) of tables with the same structure (Code, Description, Create Date, Update Date). So I wanted to do something simple so that I did not have to create all these screens 1) EO   I created the EO based on one of the tables I had that had the above columns. I then Added a transient attribute called table name to my EO based on a groovy expression. (the expression needs to change as I am reading web tier stuff from the model layer but I will fix this later) I then generated a java class for my EO. And added the following overriden method to my newly created java class. protected StringBuffer buildDMLStatement(int i, AttributeDefImpl[] attributeDefImpl,   AttributeDefImpl[] attributeDefImpl2, AttributeDefImpl[] attributeDefImpl3, boolean b) {   StringBuffer statement = super.buildDMLStatement(   i, attributeDefImpl, attributeDefImpl2, attributeDefImpl3, b); return new StringBuffer(StringUtils.replace(statement.to...

Util code

public static MethodExpression getMethodExpression( String expr, Class returnType, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); ExpressionFactory elFactory = fc.getApplication().getExpressionFactory(); return elFactory.createMethodExpression( elctx, expr, returnType, argTypes); } public static javax.faces.el.MethodBinding getMethodBinding( String expr, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); return fc.getApplication().createMethodBinding(expr, argTypes); } SetPropertyListener listener = new SetPropertyListener( ActionEvent.class.getName()); listener.setFrom(link.getRoute()); listener.setValueExpression("to", JSFUtils.getValueExpression("#{pageFlowScope.route}", String.class)); action.addActionListener(listener); AdfFacesContext.getCurrentInstance().getPageFlowScope() .put("route", lin...

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]