My main concern with the orderby in the JAR is that it may make tracking down errors more difficult.
Lets say you install a 3rd party jar where the orderby for X is 2, and you set up another X component but orderby is 1 (thinking it overrides a default of 0), it's going to take a while to track down the orderby setting in the jar to know to set yours to > 2. You are back to relying on the 3rd party jar documentation of the orderby, or looking through the JAR for the components.xml to figure it out. How can we make this more obvious? Would including the orderby value in the log output when Seam installs a component be enough? Maybe! We also need to think about what happens when 2 components with the same name have the same value for orderby. Who wins? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955753#3955753 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955753 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
