<div class="gmail_quote">On Sun, Apr 4, 2010 at 10:40 AM, Lincoln Baxter, III <span dir="ltr"><<a href="mailto:lincolnbaxter@gmail.com">lincolnbaxter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
IMO -- If we having a naming conflict, then we have a problem -- We should put in an effort across modules to coordinate naming and functionality. If there are two modules providing the @Secure or two modules providing the @Conversational attribute, then we probably have duplicate functionality, and need to re-think where that functionality should go, in a common place; new modules could even be spawned for such reusable functionality.<br>
<br>These types of naming conflicts will also cause usability issues when people try to use both modules -- package differences aside, you'll still have to be referencing them by the fully qualified name, and that's not cool.<br>
<br>We shouldn't be duplicating much of anything.<br></blockquote><div><br></div><div>Yes, I agree we should avoid duplicate class names in the public API as a general rule, because we've seen the confusion that has caused in the Java EE API (@ManagedBean, @*Scoped, etc). But still, too much package sharing can also be confusing for the developer because it becomes somewhat unclear which modules are providing which classes. So we are agreeing that modules use the base name space of org.jboss.seam.[module], correct? (With the special case of interceptors/decorators, see next).</div>
<div><br></div><div>That said, Shane had brought up that interceptors and decorators should at least be under the module's base package (the second proposed convention for interceptors/decorators above). We need a vote on that convention:</div>
<div><div><br></div><div>a) org.jboss.seam.intercept / org.jboss.seam.decorate</div></div><div>b) org.jboss.seam.[module].intercept / org.jboss.seam.[module].decorate</div><div><br></div><div>Let's find a common ground quickly on this...it's not worth dragging out.</div>
<div><br></div><div>-Dan</div><div><br></div></div>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>