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

[Juergen H. <ju...@in...>]

No worries, that's already in the works :-)

It's one of the things I personally wanted to see changed before the =
move
into the core.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
Cris J. Holdorph
Sent: Thursday, July 07, 2005 5:43 PM
To: spr...@li...
Subject: Re: [Springframework-developer] old dependencies on spring =
portlet
in webflow

Can we PLEASE PLEASE consider changing the two "handleRequest" methods =
to
different names?  This is a violation of what is consider good 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 =

> part of Spring 1.2.3 in about two weeks. Web Flow RC1 will in turn=20
> build 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 =

> would recommend to continue using Web Flow PR3 on Spring 1.2.1 for the =

> time being.
> =20
> Juergen
> =20
>=20
> ----------------------------------------------------------------------
> --
> *From:* spr...@li...
> [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'm having w/ spring portlet=20
> development.  I am attempting to use spring webflow /w the portlets,=20
> and the PR3 release of webflow apparently includes references to older =

> versions of portlet code (that exist in the spring sandbox) - and the=20
> latest version of spring-portlets as released by john lewis includes=20
> significantly updated code, and when attempting to include all those=20
> jars in the portlet environment, theres all sorts of classloader=20
> issues w/ different versions of DispatchPortlet and PortletController=20
> lying around.  I've been trying to rebuild parts to get them all to=20
> talk to each other, but it's 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 - so that webflow can be coded against the=20
> proper classes and those classes being dropped from webflow-support. =20
> I know that this has been under discussion lately to start with 1.3=20
> development, and I'm hoping with the release of 1.2.2 complete, that=20
> things can move in that direction.
>=20



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies =
from
IBM. Find simple to follow Roadmaps, straightforward articles, =
informative
Webcasts and more! Get everything you need to get up to speed, fast.
http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer