You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Oleg V Alexeev <oa...@apache.org> on 2002/02/05 15:03:41 UTC
Re[2]: J2EE BluePrints and Struts
Hello Ted,
Tuesday, February 05, 2002, 4:58:37 PM, you wrote:
TH> Oleg had a pager as part of his BeanFactory, but that was never made
TH> part of the framework. Perhaps he will get back to that after the
TH> ServiceManager work (Go Oleg!).
Pager bean is already ok and I can commit it to the repository
anytime. But I think that it is not struts-related stuff and can be
used with any project - so is it right to commit pager bean to the
struts repository? There is one reason only to do so - struts has not
any pager code now... 8)
TH> Generally, these type of model-centric patterns do not need be a part of
TH> the core framework. The framework provides places where you can plug
TH> into the model (Actions). And ways to pass control back and forth
TH> between the View (struts-config elements). But the implementation of
TH> something like paging is an excercise left to the developer.
TH> A patterns-based approach to paging might be something I would put into
TH> the optional Scaffold package, which has a number of
TH> implementation-pattern type classes.
--
Best regards,
Oleg mailto:oalexeev@apache.org
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re[2]: J2EE BluePrints and Struts
Posted by Oleg V Alexeev <oa...@apache.org>.
Hello Ted,
Tuesday, February 05, 2002, 6:20:19 PM, you wrote:
TH> Or, I guess the Commons -- there's a tag, but it's mostly a JavaBean,
TH> yes?
It is not tag - it is bean only. Developer can set properties and read
page count, iterator with page labels and so all. To generate actual
pager at JSP-page developer can use logic:iterate and so all.
TH> And of course, everything we're saying about Oleg's would also go for
TH> Pierre's, if he would like to donate it to the cause.
TH> If the two implementations are sufficient differently, and each would
TH> work better under different circumstnaces, perhaps we could offer them
TH> together.
TH> -T.
--
Best regards,
Oleg mailto:oalexeev@apache.org
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: J2EE BluePrints and Struts
Posted by Ted Husted <hu...@apache.org>.
Or, I guess the Commons -- there's a tag, but it's mostly a JavaBean,
yes?
And of course, everything we're saying about Oleg's would also go for
Pierre's, if he would like to donate it to the cause.
If the two implementations are sufficient differently, and each would
work better under different circumstnaces, perhaps we could offer them
together.
-T.
Ted Husted wrote:
>
> Well, we should commit it ~someplace~ :-)
>
> It should probably go to Taglibs, but if you are not up for that right
> now, we could just park it under Contrib, or in the Scaffold package.
>
> I'd be happy to help propose it to Taglibs, but Cedric and I should
> finish doing that with Tiles first.
>
> -T.
>
> Oleg V Alexeev wrote:
> >
> > Hello Ted,
> >
> > Tuesday, February 05, 2002, 4:58:37 PM, you wrote:
> >
> > TH> Oleg had a pager as part of his BeanFactory, but that was never made
> > TH> part of the framework. Perhaps he will get back to that after the
> > TH> ServiceManager work (Go Oleg!).
> >
> > Pager bean is already ok and I can commit it to the repository
> > anytime. But I think that it is not struts-related stuff and can be
> > used with any project - so is it right to commit pager bean to the
> > struts repository? There is one reason only to do so - struts has not
> > any pager code now... 8)
> >
> > TH> Generally, these type of model-centric patterns do not need be a part of
> > TH> the core framework. The framework provides places where you can plug
> > TH> into the model (Actions). And ways to pass control back and forth
> > TH> between the View (struts-config elements). But the implementation of
> > TH> something like paging is an excercise left to the developer.
> >
> > TH> A patterns-based approach to paging might be something I would put into
> > TH> the optional Scaffold package, which has a number of
> > TH> implementation-pattern type classes.
> >
> > --
> > Best regards,
> > Oleg mailto:oalexeev@apache.org
> >
> > --
> > To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> > For additional commands, e-mail: <ma...@jakarta.apache.org>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Java Web Development with Struts.
-- Tel +1 585 737-3463.
-- Web http://www.husted.com/struts/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: J2EE BluePrints and Struts
Posted by Ted Husted <hu...@apache.org>.
Well, we should commit it ~someplace~ :-)
It should probably go to Taglibs, but if you are not up for that right
now, we could just park it under Contrib, or in the Scaffold package.
I'd be happy to help propose it to Taglibs, but Cedric and I should
finish doing that with Tiles first.
-T.
Oleg V Alexeev wrote:
>
> Hello Ted,
>
> Tuesday, February 05, 2002, 4:58:37 PM, you wrote:
>
> TH> Oleg had a pager as part of his BeanFactory, but that was never made
> TH> part of the framework. Perhaps he will get back to that after the
> TH> ServiceManager work (Go Oleg!).
>
> Pager bean is already ok and I can commit it to the repository
> anytime. But I think that it is not struts-related stuff and can be
> used with any project - so is it right to commit pager bean to the
> struts repository? There is one reason only to do so - struts has not
> any pager code now... 8)
>
> TH> Generally, these type of model-centric patterns do not need be a part of
> TH> the core framework. The framework provides places where you can plug
> TH> into the model (Actions). And ways to pass control back and forth
> TH> between the View (struts-config elements). But the implementation of
> TH> something like paging is an excercise left to the developer.
>
> TH> A patterns-based approach to paging might be something I would put into
> TH> the optional Scaffold package, which has a number of
> TH> implementation-pattern type classes.
>
> --
> Best regards,
> Oleg mailto:oalexeev@apache.org
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>