On 29 June 2013 21:32, David Tildesley <[email protected]> wrote: > We separated out the "UI layer objects" from the domain layer objects via > packaging. > I would like to see a more enforced separation - I'm not sure how to go > about it though. >
Me neither. I'm not sure that Isis should have anything to enforce such separation - I think you can achieve all that you want with Maven modules. > > With a system oriented UI (could be invoked in any number of ways: soap > web service, JMS message, ...) > as with a human UI, the trick is not to allow bleeding of domain business > logic in to the UI > and ensure that the domain never depends on the UI. This way, you can bolt > on any number of UI's to the same domain layer. > > If I understand you, are you saying that your UI code is not Isis; it's a bespoke layer handling the JMS messages etc? If that's the case, then I'm curious to know (I can't remember us discussing this) how you ensure that all the declarative business rules are enforced in your non Isis UI code? One approach is to use the WrapperFactory, but I imagine I'd've remember you saying if you were using that approach. Dan [snip] > David. >
