> I am working on the nested DC feature. I started by creating a demo
> application with Click front-end. What I discovered though is that since
> Click provides another layer of objects (UI stateful widgets) in front
> of Cayenne-based model, I can't come up with a scenario where a nested
> context is needed (as opposed to say a peer context)!
>
> The need for it was clear in WebObjects when object state was
> dynamically bound to the page, so you'd have to prepare your object
> model on GET without any guarantee that the matching POST would happen.
>
> But if you use frameworks like Click (and actually Struts, with
> ActionBean playing the "front row buffer" role), where does it fit here?
>
> I am probably just having a bad day, as I am sure there were a few
> important scenarios that I am missing now.
What about 'non-web' based applications? e.g. Swing based?
Aren't in this case more usage scenarios for nested DCs?
Many such applications simply do not use ORMs. In many cases this is also
due to the fact that ORMs do not have "complete" examples for such applications(Swing), and it
would be a too high risk to use the ORM and just to find later that it's too complicated, or it's
not fitting at all.
Maybe I'm wrong, but nested DCs seem more suitable for such applications since they are pretty
"statefull", "processes"/"work flows" span across many screens/steps.
Ahmed.
This archive was generated by hypermail 2.0.0 : Sun Jan 15 2006 - 08:37:20 EST