Leszek Gawron wrote:
Upayavira wrote:
I think you are getting something wrong here.
If you have two objects bizObj1 and bizObj2, and you pass these to a pipeline that does
JXT(bizObj1)->tx->tx-\ >-aggregate->tx->serlialize JXT(bizObj2)->tx->tx-/
You would do:
sendPage("your-pipeline", {"bizObj1": bizObj1, "bizObj2": bizObj2});
It feel like it breaks SoC a little as controller has to know how your view is rendered. Also if you change your rendering to 3 aggregate parts you have to make appropriate changes in controller.
Huh? Surely, your controller needs to tell the view what information (models) it needs to display? This is a necessary part of MVC?
<huge-snip about="wrapping a heavy business object"/>
Does that make sense?
Now it does. I never thought of a wrapper. It's real pleasure to discuss with you all.
Glad that helped.
It seems to me that Sylvains suggested extension of jxt has a great deal of power in it.
OK. Then I'll continue my work and try to provide the appropriate patch as I have already started to make needed changes.
Great. I'd love to see a cacheable jxt.
Regards, Upayavira
