Shane,<br><br>Looks good to me.<br><br>I know we discussed a possible API for Solder to support the error messages, but can't recall (and didn't write it down, doh!) what you suggested. Can you remember?<br><br>Thanks<br>
Ken<br><br><br><div class="gmail_quote">On Tue, Sep 6, 2011 at 8:23 PM, Shane Bryzak <span dir="ltr"><<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
People present:<br>
<br>
Jason Porter<br>
Ken Finnigan<br>
Shane Bryzak<br>
<br>
1) Standardised error codes<br>
<br>
We discussed the idea of implementing standard error codes throughout<br>
all Seam modules. These error codes would be unique, and allow Seam<br>
developers to reference a central database (such as Seam University)<br>
describing each error and possible workarounds. The error codes<br>
themselves will be prefixed with a 2 or 3 letter code (that represents<br>
the module), followed by a number. For example:<br>
<br>
[SEC-1234] Invalid credentials supplied<br>
<br>
The SEC prefix represents an exception in the Seam Security module.<br>
Other modules would have different codes, for example CAT = Seam Catch,<br>
VAL = Seam Validation, SVL = Seam Servlet, and so forth. The number<br>
part of the error code will start at 0000 for each module. The error<br>
message itself should support internationalisation, which will be a<br>
bonus to our non-english speaking users. Each module will define its<br>
own internationalised message resources. Ken is going to work on<br>
creating a new API in Solder which we can use to perform the logging of<br>
these errors.<br>
<br>
2) Inter-module dependencies<br>
<br>
The second topic we discussed was how we manage dependencies between<br>
modules. It was agreed that wherever possible, dependencies should be<br>
optional. An example of this is the dependency that seam-faces has on<br>
seam-catch. In some cases it may be necessary for a module to have a<br>
hard dependency on another module, however if this becomes an issue in<br>
the future we may look at alternatives such as creating sub-modules that<br>
separate the integration from the rest of the module.<br>
<br>
If anyone has any questions, feel free to ask. We will be holding the<br>
DWG meeting in TeamSpeak once per month, on the first tuesday of the<br>
month - details can be found in the seam-dev calendar.<br>
<br>
Thanks,<br>
Shane<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</blockquote></div><br>