Yeehaw. I've got it. Although I've only one @DataModel, only one @DataModelSelction and only one @DataModelSelectionIndex I had to add the parameter value to the @DataModelSelection annotation:
@DataModelSelection | @Out(required=false, scope=ScopeType.SESSION) | private Testaction foundTestaction; became to @DataModelSelection(value="getFoundTestactions") | @Out(required=false, scope=ScopeType.SESSION) | private Testaction foundTestaction; After that the application deployed or to be more precise: this component got loaded without errors. But this causes another problem: I've a class hierarchy in which the superclass holds @DataModelSelection and @DataModelSelectionIndex and its three subclasses have a @DataModel and a @Factory. The superclass is a normal class, not an entity and not a component. The three subclasses are components with different names. I think you see the problem: Since the @DataModel annotation is used in the subclasses on methods with different names, I can't add the value parameter to the @DataModelSelection in the superclass because there are three @DataModel names, one for each component. With Seam 1.0 beta2 this hierarchy wasn't a problem. It worked very well. The class hierarhy was introduced since before I had three classes with almost the same behaviour. And this behaviour is now encapsulated by the superclass. This made my subclasses pretty small and developing more effectively. I don't want to return to three single classes. I hope there is another workaround or I revealed a bug, which will be fixed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3948617#3948617 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3948617 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
