Matthieu Codron wrote: > Brandon Black a écrit : > In J2EE projects, the layer model is more like "MSCV-I", for Model --> > Service --> Controller --> View, the "I" standing for Integration layer > (Spring for example, or Catalyst in Perl) > > What is missing in Catalyst is that "Service" layer. But it's not a big > deal in most cases, IMHO.
Nah, you just stick that layer in your model directory and the domain implementation itself somewhere else. It's not really missing, it's more that the tutorials, convenience components etc. all focus on small apps which don't need that extra layer of abstraction so much. By the time you really need the split to be explicit, you've probably got enough architecture for that not to be a problem (or if you haven't you've got bigger problems than any related to Catalyst :) -- Matt S Trout Offering custom development, consultancy and support Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information + Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ + _______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/