Re: [Springframework-developer] old dependencies on spring portlet in webflow

[Cris J. H. <hol...@un...>]

Can we PLEASE PLEASE consider changing the two "handleRequest" method=
s=20
to different names?  This is a violation of what is consider good=
=20
practice for overriding.  They are fundamentally different methods.=
=20
This change REALLY should be made before it is moved into the core.

---- Cris J H

Juergen Hoeller wrote:
> Hi Tim.
> =20
> We actually intend to release the core Portlet support earlier now:=
 as=20
> part of Spring 1.2.3 in about two weeks. Web Flow RC1 will in turn =
build=20
> on that release then.
> =20
> For the meantime, there might be a Web Flow PR4 as a remedy for the=
=20
> current situation, but that's up to Keith and Erwin to decide. Else=
, I=20
> would recommend to continue using Web Flow PR3 on Spring 1.2.1 for =
the=20
> time being.
> =20
> Juergen
> =20
>=20
> -------------------------------------------------------------------=
-----
> *From:* spr...@li...=20
> [mailto:spr...@li...] *On=
=20
> Behalf Of *Tim Kettering
> *Sent:* Wednesday, July 06, 2005 7:56 PM
> *To:* spr...@li...
> *Subject:* [Springframework-developer] old dependencies on spring=
=20
> portlet in webflow
>=20
> =20
>=20
> This really addresses two issues I=92m having w/ spring portlet=
=20
> development.  I am attempting to use spring webflow /w the portlets=
, and=20
> the PR3 release of webflow apparently includes references to older=
=20
> versions of portlet code (that exist in the spring sandbox) =96 and=
 the=20
> latest version of spring-portlets as released by john lewis include=
s=20
> significantly updated code, and when attempting to include all thos=
e=20
> jars in the portlet environment, theres all sorts of classloader is=
sues=20
> w/ different versions of DispatchPortlet and PortletController lyin=
g=20
> around.  I=92ve been trying to rebuild parts to get them all to tal=
k to=20
> each other, but it=92s been a big time-sink.
>=20
> =20
>=20
> I see the best solution being that John being allowed to merge his=
=20
> portlet code in the cvs =96 so that webflow can be coded against th=
e=20
> proper classes and those classes being dropped from webflow-support=
.  I=20
> know that this has been under discussion lately to start with 1.3=
=20
> development, and I=92m hoping with the release of 1.2.2 complete, t=
hat=20
> things can move in that direction.
>=20