This really depends on what exactly you mean by 'mapping'
It might be that a simple java.util.Map does the job, although
some kind of proxy/deligate/facade sounds more like it.
Can you give an example of what kind of objects we are talking and what's the purpose of the mapping?
I wouldn't know of a pattern to do such a thing ... except you consider refactoring a pattern.
But in the jakarta/apache common project is class or package to access bean properties by their names. Maybe you could use those, together with a properties file for configuration to do your mapping.
Of course ... while this might safe some coding time it will use reflection and there for is relativly slow.
regards
Spieler