[seam-dev] Seam common module

[Shane Bryzak]

These two were just examples, in reality there's a lot more than that.  
I do like the idea though of making the modules as independent as 
possible, so for now I'll just copy any utility classes that are 
required into the module itself.

Pete Muir wrote:
> Really, if you need two methods off Strings and one from Base64, it's 
> better to copy those methods into your modules. A small bit of code 
> duplication is better than the extra dependency IMO.
>
> I really want to avoid this common crap unless we have to have it for 
> some non-trivial piece of code, and even then it would be better to 
> create a shared library that does just what it says (e.g. document-store)
>
> On 22 Apr 2009, at 07:36, Shane Bryzak wrote:
>
>> We need some place to put utility classes that are shared across the 
>> other modules, such as Strings, Base64, etc.  For now, I've added a 
>> common module which is currently very minimal (which we can add to as 
>> required), however I'm not sure if this is the way we ultimately want 
>> to go.  I can't currently think of any alternative though - does 
>> anyone else have an opinion on this?  If we go down this route, then 
>> we will probably be able to do away with the root /common directory 
>> and just have modules/common instead.  Actually the more I think 
>> about it, since we are restructuring everything into modules anyway 
>> it doesn't make much sense to have a root common directory at all.
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>
> -- 
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>