A quick look through the modules last night made me aware of two conventions that we need to clarify.<div><br></div><div><b>Implementation JAR names:</b></div><div><br></div><div>All modules are following the naming convention seam-%module%-api for the API JAR. However, the names of the implementation JARs are inconsistent. There are three naming patterns in use: seam-%module%, seam-%module%-impl (persistence) and seam-%module%-core (js-remoting)</div>
<div><br></div><div>Several modules use the root name seam-%module% to make it easy to remember and aesthetic when including as a dependency. However, seam-%module%-impl is more technically correct since it only contains the implementation classes, with just a dependency on the API.</div>
<div><br></div><div>My proposed solution is to publish the api and impl JARs as normal, then publish a third JAR that combines the two into one using the maven-shade-plugin.</div><div><br></div><div><b>Event types:<br></b><div>
<br></div><div>I&#39;m seeing some event types (the type of the event payload) that use the suffix &quot;Event&quot; and those that do not. I think we should either have one or the other...or have rules as to when one is chosen.</div>
<div><br></div><div>My proposed solution is that we should try to use the data object as the payload with an event qualifier to specify the action if possible. If it needs to be wrapped to bundle up other information, then the wrapper type should be named with the Event suffix.</div>
<div><br></div><div>Here are examples of the data object as payload:</div><div><br></div><div>@Initialized ServletContext</div><div>@Updated @Client DateTimeZone</div><div>@Created SeamManagedPersistenceContext  &lt;- proposed change</div>
<div><br></div><div>Event wrappers are used when the payload is a composite (and there isn&#39;t already a logical wrapper type). However, I&#39;m finding it hard to come up with cases where a data object + qualifiers won&#39;t suffice. Could also just be a style thing.</div>
<div><br></div><div>I also think we should push the standard action qualifiers into Seam Solder (Weld Extensions). Where possible, we should avoid synonyms (e.g., both @Changed and @Altered). Candidates so far are:</div><div>
<br></div><div>@Initialized</div><div>@Destroyed</div><div>@Updated (or @Changed or @Altered)</div><div>@Created (can this just be @Initialized?)</div><div>@Before</div><div>@After</div><div><br></div><div>maybe...</div><div>
@Failed</div><div>@Added</div><div>@Replaced</div><div>@Inserted</div><div>@Deleted</div><div><br></div><div>Please note these are suggestions. Feel free to provide feedback.</div><div><br></div><div>-Dan</div><div><br>-- <br>
Dan Allen<br>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
</div></div>