http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Hmm interesting, specially for the larger CRM projects, because the customizations are sometimes a little pain in the ****. Never thought about this to be easier than my thinking had in mind. Unfortunately jQuery isn't part of my knowledge, yet. http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment6http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment6Tue, 18 Sep 2007 19:15:46 GMTPart of the things that we did was to enable jQuery integration, so we can have (local on my IIS machine) JS files that does stuff like: $(document).ready(function() { $('#new_startdate').change(onDateChange); $('#new_enddate').change(onDateChange); }); Since jQuery supports ajax with $.getScript('path/to/server') this is ridiculously easy to handle I am thinking of adding MonoRail integration as well, which would make this really a piece of cake. http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment5http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment5Tue, 18 Sep 2007 19:07:31 GMTHmm, that's what I really like. Now the above classes can be built, I'm thinking about the next step. Making these business rules available through webservices, so we can call them from within Javascript. Because after any business rule like the above, the user needs to reenter the complete form, we don't want that, do we? So instead of creating Javascript for the business rules also, I'd like to have a small simple javascript function that internally calls a webservice that can make use of the business rule designed for callouts. This way no duplication of business rules can happen. http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment4http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment4Tue, 18 Sep 2007 19:00:41 GMTYes, the lowest level is still a callout, but that is literally something that I no longer thinks of. Something like this: public void Execute() { DateTime start = PreState.new_startdate, end = PreState.new_enddate; if( start > end ) { ErrorMessage = "Start cannot be bigger than end"; Result = PreCalloutReturnValue.Abort; } } http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment3http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment3Tue, 18 Sep 2007 18:51:03 GMTSounds interesting. Do you on the background still make use of CRM Callouts? How do you set any validation messages? http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment2http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment2Tue, 18 Sep 2007 18:17:16 GMTAnti-corruption layers are well worth the effort, IMHO. We've just done the same thing with the web service interface to SQL Server Reporting Services. I think that the trouble with their API results mostly from limitations of SOAP, but covering it with a facade that can take advantage of things like generics is a huge help. http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment1http://ayende.com/2771/anti-corruption-layers-striving-for-fizzbuzz-level#comment1Tue, 18 Sep 2007 13:40:37 GMT