Aye wrote:
Thats very interesting. It sounds like your UI is handling the underlying connection also to be using HTTP HEAD (non-browser based?).
Client is JavaWebStart, using Restlet for client+server resource definitions.
I'm leaning towards using Wicket for my pet project but still researching workflow engines and rules engine to help with domain security and processes. I was excited to discover qi4j and it might replace my mess of a Spring/JPA/hibernate domain and entity layer. It's going to be very hard to fight the relational database crowd but hopefully the flexibility in process and security model can win the non-technical crowd over (they make the decisions anyway!). If you've got any more 'goodness' ideas, definitely feel free to throw them my way :)
For now not more than what I've already said: expose the domain model using Restlet resources that implement instance-level RBAC security, and then expose operations as resources. It feels right. But, will have to implement it more fully to know the results of this choice.
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
