-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: ClassValidator warnings
PostPosted: Tue May 16, 2006 10:37 am 
Beginner
Beginner

Joined: Sat Apr 15, 2006 12:49 pm
Posts: 20
Location: austria
core 3.2.0.cr2, ann 3.2.0.cr2

Hi,

I'm using Hibernate annotations on an entity's method that is declared in an interface (see below). When starting hibernate or using hibernate tools to generate my ddl I get the following warning:

Code:
2006-05-16 16:05:02,293 WARN [org.hibernate.validator.ClassValidator] - <Original type of property public abstract java.util.Set org.mydomain.acl.AccessControllable.getAclEntries() is unbound and has been approximated.>


Is this something I can take care of or will Hibernate work properly besides this warning?

Regards,

john

Interface
Code:
public interface AccessControllable <ACLType extends AclEntryBase> {
   public Set<ACLType> getAclEntries();
}


Implementing class
Code:
public abstract class Customer implements AccessControllable<CustomerAcl> {

      private Set<CustomerAcl> aclEntries = new HashSet<CustomerAcl>();

   @Column(name = "aclEntries")
   @OneToMany(targetEntity = CustomerAcl.class, mappedBy = "entity", fetch = FetchType.LAZY)
   @Type(type="AccessControlList")
   public Set<CustomerAcl> getAclEntries() {
      return this.aclEntries;
   }

...

}


Top
 Profile  
 
 Post subject: ClassValidator throw warning (unbound type)
PostPosted: Thu Jun 01, 2006 11:47 am 
Newbie

Joined: Thu Jun 01, 2006 11:31 am
Posts: 9
I have the same symptoms, with a very similar case (same version of Hibernate involved).


The interface looks like this:

public abstract interface ExampleEntity<P extends DescribedEntity, C extends DescribedEntity> extends Entity {
...
public C getChild();

...
}

My implementation class's method looks like this:

@ManyToOne(cascade={CascadeType.PERSIST, CascadeType.MERGE}, optional=false) @JoinColumn(name="CHILD", nullable=false)
public C getChild() { return child; }

The application appears to run correctly (albeit considerably more slowly than the same application written in 'pure' hibernate). However, since I worry about warnings, I'd really like to know if I need to worry about this or raise a case.

-Thom


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.