The problem is that EJBs can't be abstract. That's an EJB requirement, not a Seam choice. Since Seam deals primarily in EJBs, Gavin can't help you much here.
Seam does support non EJB POJOs, however I wouldn't think the semantics of the framework should change to support abstract JavaBean components. The semantics should be uniform and unfortunately that forces you to conform to the lowest common denominator. Anyway, I think the lack of abstract EJB support is the problem you're looking for. -Jim View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947155#3947155 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947155 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
