On Thu, 2005-05-26 at 14:45 -0600, David Geary wrote:
> Le May 26, 2005 à 12:44 PM, Sean Schofield a écrit :
>
> >> Btw. Sean, is there a place with a good introduction
> >> about Shale, mainly the components and what is being worked on?
> >> I checked the shale site a while ago and could not find anything
> >> except a few comments and a rather vague description.
> >>
> >
> > Just the wiki
> >
> > http://wiki.apache.org/struts/StrutsShale
> >
> > The javadoc actually contains quite a bit of explanation. The
> > usescases are also built nightly and they are an excellent example of
> > how the new dialog stuff works.
>
> I posted a blog entry on Shale Web Flow the other day. See /http://
> jroller.com/page/dgeary
>
>
> david
>
Hello David:
I manage to get back to Shale Dialog and read you blog on Shale Web
Flow. Craig just comes back from vacation. So i decide to fire up some
of the questions. Hope you two may save me time to dig around.
1) You said Shale loads the state's view using the supplied viewId
(which i am able to replace my previous implementation under
DialogController to the new Dialog), and soon we will be able to supply
a tile based on your work. I wonder what is its implication?
2) If i recalled in the previous version of DialogController, Craig said
"soon" we will be able to have different instances of DialogController,
controlling different fragments (tiles) in the same page, so the
deprecated DialogController is similar to Tiles controller but it can
last more than a request. I look at the new Dialog Status and
StatusImpl, there is only 1 property data. Hence, at any point you can
only associate 1 state to the {dialog.data}. I wonder how different work
flows can be independently associated to different fragments in the same
page? Specifically, i am thinking different workflows are associated
with different applications; each application occupies a fragment of a
portal page.
Thanks.
BaTien
DBGROUPS
