[seam-dev] DWG Meeting minutes

People present: Jason Porter Ken Finnigan Shane Bryzak 1) Standardised error codes We discussed the idea of implementing standard error codes throughout all Seam modules. These error codes would be unique, and allow Seam developers to reference a central database (such as Seam University) describing each error and possible workarounds. The error codes themselves will be prefixed with a 2 or 3 letter code (that represents the module), followed by a number. For example: [SEC-1234] Invalid credentials supplied The SEC prefix represents an exception in the Seam Security module. Other modules would have different codes, for example CAT = Seam Catch, VAL = Seam Validation, SVL = Seam Servlet, and so forth. The number part of the error code will start at 0000 for each module. The error message itself should support internationalisation, which will be a bonus to our non-english speaking users. Each module will define its own internationalised message resources. Ken is going to work on creating a new API in Solder which we can use to perform the logging of these errors. 2) Inter-module dependencies The second topic we discussed was how we manage dependencies between modules. It was agreed that wherever possible, dependencies should be optional. An example of this is the dependency that seam-faces has on seam-catch. In some cases it may be necessary for a module to have a hard dependency on another module, however if this becomes an issue in the future we may look at alternatives such as creating sub-modules that separate the integration from the rest of the module. If anyone has any questions, feel free to ask. We will be holding the DWG meeting in TeamSpeak once per month, on the first tuesday of the month - details can be found in the seam-dev calendar. Thanks, Shane