Not true, you can map interfaces as a superclass. But in this case Matthew is anyway using any <any> association by the looks of it, so he doesn't need to. Can't see the problem though.

Bear Giles wrote:
Matthew E.Porter wrote:

I have a interface called PaymentType which has 2 implementing classes- CreditCardPaymentType and EmailPaymentType.

No persister for: com.demandsolutions.merovingian.payment.entity.PaymentType; nested exception is: net.sf.hibernate.MappingException: No persister for:

> com.demandsolutions.merovingian.payment.entity.PaymentType


I'm not 100% certain of this answer, but I believe the problem is that PaymentType is an interface instead of a class. Hibernate can only persist a class. (Even if it's an abstract class?)

I'm not sure why you didn't have problems persisting PaymentType directly.



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel

-- Gavin King JBoss Group +61 410534454 http://hibernate.org



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to