[sergeypk2]

Here's my hacked version of EntityLoader that worked for me:

@Name("org.jboss.seam.ui.entityLoader")
@Scope(STATELESS)
public class CustomEntityLoader extends EntityLoader {

 @Override
 protected Identifier createIdentifier(Object entity) {
 return new CustomEntityIdentifier(entity, getPersistenceContext());
 }
}

public class CustomEntityIdentifier extends EntityIdentifier {

 public CustomEntityIdentifier(Object entity, EntityManager entityManager) {
 super(entity, entityManager);
 }

 @Override
 public Object find(EntityManager entityManager) {
 Object result = super.find(entityManager);

 if (result instanceof HibernateProxy) {
 return ((HibernateProxy) result).getHibernateLazyInitializer()
 .getImplementation((SessionImplementor) entityManager.getDelegate());
 }

 return result;
 }
}

[franck93]

Here's my hacked version of EntityLoader that worked for me

So you just put that in your classpath and thanks to the annotation

@Name("org.jboss.seam.ui.entityLoader")

it gets called automatically??

[sergeypk2]

Yes, that's my understanding of how Seam components are meant to be replaced/extended.

[stian]

Is it really necessary to apply such dirty hacks just to get simple management of many-to-one relationships working?

I would expect that such simple things should work out of the box with a framework with all sort of advanced stuff...

[pmuir]

No one put this in JIRA so that we can fix it - its a bug probably. If you want it fixed, put in JIRA, don't just complain.

[bad]

This maybe solves the problem:

https://community.jboss.org/thread/183558

In short: use x.getId() not id directly.