Trouble Injecting DAO Into Hibernate Validator

[schevus.swosborne.magellanhealth.com]

I am trying to insert a DAO into a custom validator to perform  unique constraint validation. Code is below:

Field in my domain object

@Required
    @Length(max = 45)
    @RestrictSpecialCharacters
    @UniqueAliasName
    public String getName() {
        return name;
    }

Validator Interface

@Documented
@ValidatorClass(value = UniqueAliasNameValidator.class)
@Target(value = {ElementType.METHOD})
@Retention(value = RetentionPolicy.RUNTIME)
public @interface UniqueAliasName {

    String message() default "Alias name is already in use.";
}

Validator Class

public class UniqueAliasNameValidator implements Validator<UniqueAliasName> {

    private AliasDao aliasDao;

    public boolean isValid(Object value) {
        aliasDao = (AliasDao) Component.getInstance("aliasDao");

        boolean result = aliasDao.validateAliasNameUnique((String) value);

        return result;
    }

    public void initialize(UniqueAliasName uniqueAliasName) {}
}

validateAliasNameUnique Method

public boolean validateAliasNameUnique(String aliasName) {
        Query query = entityManager.createNamedQuery("Alias.findByExactName");
        query.setParameter("aliasName", aliasName.toLowerCase());

        List aliasList = query.getResultList();

        return aliasList.isEmpty();
    }

Originally my problem was injecting my DAO, but that seems to be working fine with the manual lookup. Everything seems to work fine until flush() is called on my EntityManager, at which point the process flow gets stuck in an infinite loop bouncing back and forth from my custom validator class to my DAO method, eventually resulting in a StackOverflowException.

I realize this may be hibernate related (and I will post there also), but what I'm wondering is are there any repercussions for calling Component.getInstance()? Do I need to clear something out after doing that? I have seen at least a half dozen form posts with this problem with no clear resolution, so any help is appreciated. Thanks.

[admin.admin.email.tld]

from the Seam 2.0.1 ref doc pdf:

Seam.Component.getInstance()

The getInstance() method is used to get a reference to a Seam session bean component stub, which can then
be used to remotely execute methods against your component. This method returns a singleton for the specified
component, so calling it twice in a row with the same component name will return the same instance of the
component.

So apparently your DAO is a SLSB?  if yes, the reason the @In injection is not working may be b/c you're not using the local interface name as the private instance variable name and as the type of the variable.

e.g. if the local interface is AliasDaoLocal, try something like:

@In(create = true) 
private ActivityLogLocalDAO activityLogDAO;

I wouldn't worry about clearing anything out...

[schevus.swosborne.magellanhealth.com]

I tried injecting like that originally, and I could never get anything but null. Sounds like my problem isn't with the getInstance() call, so I'm guessing it's hibernate related. Thanks for the info.

[emeric]

Hello,
please have you found a solution for your problem.
Please let me know.
Thank you in advance and best regards
Emeric