Really nice the wayback machine. I remember read about it quite time ago, but never used it... and works like a charm!
I didn't pretended to open a debate about the role of Workflows on DDD or NakedObjects. It was just an example of an infrastructure service provided by MS CRM that could be also a higher-level "Infrastructure Service" available on Isis. My intention was to open a debate about the possibility that "higher-level" building blocks were also part of Isis, such as a collection of "infrastructure level services" (like Dan's Email Service, the Event Service recently commited by Dan, the publish-subscribe service, a Geographic Mapping Service - available on different , the Workflow service, a generic interface to a SMS Service with implementations based on different providers - such as Twilio, or Apache Camel - useful in multiple uses cases -, etc.). Also, some generic "infrastructure domain services" (such as the recently commented "Shiro's Security Domain Service", or a "Human Task Service" - more on this after). All them can be used as "infrastructure services" on a great variety of Bounded Contexts implementing Domains. If not possible to be part of Isis, at least been available on a "centralized" git repository that can be used and growth by the community. Same happens with different implementation examples that have been made by different community members that are hard to be found. We could contribute some of them (like Twilio's SMS Service or the Human Task Service) and I'm sure there are also other members with valuable services. Together with the "infrastructure services" I mentioned other parts of MS CRM architecture, a framework envisioned for building custom solutions over it. Specially relevant are those regarding the User Interface. What I read about the DHTMLX viewer, its DSL and the custom "scripting" capabilities is really close to the current MS CRM "viewer's" architecture. They have an editor to customize each entity view, but the technology is quite close to Maurizio's one. The fact is that they also have a user interface "metamodel" that allows the User Interface representation to be customized at real-time (also really close to what Maurizio showed on his demo): - MS CRM "Entity Forms" internals: http://msdn.microsoft.com/en-us/library/gg334527.aspx - MS CRM "Entity Forms" metamodel: http://msdn.microsoft.com/en-us/library/gg327975.aspx - MS CRM different "Entity Forms" presentations available: http://msdn.microsoft.com/en-us/library/hh913610.aspx And that DSL / FormXml can be associated through the "Metadata Service" / Isis ObjectRepresentation with the Entity, including the possibility to associate custom designs with different Security Roles: - MS CRM "Role Based Forms": http://msdn.microsoft.com/en-us/library/gg309517.aspx Here is a link to all customizations available on MS CRM 2011: http://msdn.microsoft.com/en-us/library/gg328235.aspx Regarding the "Human Tasks Service" I mentioned before and on the previous email, it was just an example. But I've found that it's really close to what Richard Pawnson's propose on his post as an example of what has worked for him. See the following documentation about the JBoss JBPM Human Task Service (the one we have been using, with Apache license). JBPM contains both an automated workflow implementation based on BPMN (what Richard thinks is not working :-), and also a Human Services implementation based on the WS-HumanTask (WS-HT) specification: http://docs.jboss.org/jbpm/v5.2/userguide/ch.Human_Tasks.html#d0e3725 We are using it as the basis of a "small" Ticketing/ServiceDesk Bounded Context and works really well. The only intention with all this is just to show a proven architecture that has been commercially successful that contains building blocks quite close to those present or planned for Isis and that can serve as "an inspiration" for a future roadmap. Some things are made differently on Isis (are really simplified), but some others can show a higher-level path that can provide higher value (more closely aligned with business solutions needs) to Apache Isis users. Hope this helps, Oscar El 29/06/2013, a las 11:31, Dan Haywood <[email protected]> escribió: > You can read it via way back machine if you really want... I re-read it > again myself this morning that way. > > Sorry to be brief, sent from my phone > On 29 Jun 2013 10:02, "GESCONSULTOR" <[email protected]> wrote: > >> Thanks for the link, david. >> >> The blog's database it's down and the post it's not showed. >> >> Enviado desde mi iPhone >> >> El 29/06/2013, a las 02:10, David Tildesley <[email protected]> >> escribió: >> >>> Read Richard Pawson's >> http://blog.nakedobjects.org/2007/11/19/workflow-a-triumph-of-hope-over-experience/ >>> >>> DDD is how you do this stuff and a problem domain is specific to your >> business and nobody elses. Which is why ISIS is so appealing in the first >> place. >>> >>> David. >>> >>> >>> ________________________________ >>> From: GESCONSULTOR - Óscar Bou <[email protected]> >>> To: "[email protected]" <[email protected]> >>> Sent: Saturday, 29 June 2013 12:51 AM >>> Subject: Microsoft CRM as a reference architecture (part 2) >>> >>> >>> >>> Some complementary links for avoiding to be classified as spam. >>> >>> >>> INFRASTRUCTURE LAYER >>> >>> - Workflows: http://msdn.microsoft.com/en-us/library/cc151140.aspx >>> >>> - Security Model: http://msdn.microsoft.com/en-us/library/bb955124.aspx >>> >>> - Plugins and Internal Event Service: >> http://msdn.microsoft.com/en-us/library/cc151086.aspx >>> >>> >>> PRESENTATION - VIEWER LAYER >>> >>> - User interface style guide (that could "inspire" Apache Isis user >> interface "sections"): >>> http://msdn.microsoft.com/en-us/library/cc150858.aspx >>> >>> - Client extensions (Javascript events, etc.): >>> http://msdn.microsoft.com/en-us/library/cc150828.aspx >>> >>> - Future user interface they will incorporate in next major version: >>> http://www.preact.co.uk/preact_blog/dynamics-crm-flow-interface >>> >>> >>> >>> >>> Main link to the MS CRM SDK: >>> >>> http://msdn.microsoft.com/en-us/library/bb928212.aspx >>
