public static T unproxy(T entity)
{
if (entity instanceof HibernateProxy)
{
entity = (T)((HibernateProxy)entity).getHibernateLazyInitializer().getImplementation();
}
return entity;
}

If you are working with hibernate-persisted entities, or objects that may be proxied in some other way, the object passed in to the constructor may be a proxy (i.e. it is of a proxy class, not the OR-mapped class). This obviously causes a problem when you come to regenerate the object (in hibernate this will give an unmapped entity exception).

The solution is to check if the class is a proxy class before attempting to load the entity. If it is a proxy, then retrieve the mapped class and use that to load.

e.g. for CGLIB proxies:

Class entityClass = clazz;
if ( net.sf.cglib.proxy.Enhancer.isEnhanced(entityClass) ) {
// is a proxy
entityClass = clazz.getSuperclass();
}

Am I missing something?

It is pretty easy to set up a single-transaction-per-request pattern in wicket. It is not as granular as a transaction for the form submit, but it should still work.

public class WicketRequestCycle extends WebRequestCycle
{
    private TransactionStatus txn;
 
    @Dependency
    private PlatformTransactionManager txm;
 
    public WicketRequestCycle(WebApplication application, WebRequest request, Response response)
    {
        super(application, request, response);
    }
 
    @Override
    protected void onBeginRequest()
    {
        txn = txm.getTransaction(new DefaultTransactionDefinition());
        super.onBeginRequest();
    }
 
    @Override
    protected void onEndRequest()
    {
        super.onEndRequest();
        if (txn != null)
        {
            txm.commit(txn);
            txn = null;
        }
    }
 
    @Override
    public Page onRuntimeException(Page page, RuntimeException e)
    {
        if (txn != null)
        {
            txm.rollback(txn);
            txn = null;
        }
        return super.onRuntimeException(page, e);
    }
}