I like the idea where if the component is defined in component.xml, it overrides the default Seam scanning.
So CptnKirk, like you imply in your post, you only want to end up with a single X component being managed by Seam - this would be the one defined in components.xml. Order-by doesn't seem intuitive to me because of the fact that you only want to know about that single X component in the end - unlike servlets where execution order can be important. We can still override built in components using the class attribute. I'm happy to make these changes and commit them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955721#3955721 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955721 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
