Hi, its a pity that nobody had an idea.
It's possible, that my post is to stupid to be answered. But in my opinion, there are many cases in which a DB-wide unique identifier could be usefull or needed. Its also possible to retrieve it from the underlying db using hibernate before the entity is persisted, but if those retrieved value will be used as surrogate pk we need an approach to say the hibernate, that the entity is transient and must be inserted and not updated (so we need no select before, since its clear to us, the entity is transient).
The second possibility is to create a dummy entity with a desired id generation strategy and get the unique id for it but not persist this heler entity at all (its a dummy). We get the same problem as in a paragraph above, because the id will be retrieved only at the insertion time. We need to use a hibernate metadata of a desired (dummy) entity with a desired id-generation strategy to get an unique identifier by using hibernate.
If some one is intrested on this approach/idea, please read following article i found usefull:
http://www.devx.com/Java/Article/30396/1954?pf=true