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

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

We are currently leaning towards releasing the Portlet support in an =
earlier
1.3 release candidate by the end of July, with a quick 1.2.3 release
inbetween (early next week). Web Flow RC1 will then build on Spring 1.3 =
RC1.

Shipping mock objects for the Portlet API is certainly valuable - thanks =
for
pointing this out! I envision a set of mock objects analogous to our
existing Servlet API mocks, to be included in spring-mock.jar. We should
certainly provide this in Spring 1.3 RC1.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
Yujin Kim
Sent: Friday, July 08, 2005 8:27 PM
To: spr...@li...
Subject: Re: [Springframework-developer] old dependencies on spring =
portlet
in webflow

Not knowing what's in the scope for 1.2.3, I'd also like to mention that
current versions(both sandbox and john's versions) lacks the unit =
testing
capabilities.  I did create some really basic mock objects for portet
request and response, but it would be great if some testing capabilities =
are
included in 1.2.3 or 1.2.4 (not sure what you have in mind after 1.2.3).

john and some of us also have exchanged emails regarding how to map the
controllers based on both state (as in portlet mode) as well as custom
parameters using nested map.  While we both have somewhat functional
version, i think it's one of the areas that might require a
bit of discussion.   I haven't even started mapping the window state
in the mix yet.  so that could potentially add a little bit more =
elements to
it.  Probably this is where WebFlow could help a lot I am guessing.

Yujin

On 7/8/05, Juergen Hoeller <ju...@in...> wrote:
> No worries, that's already in the works :-)
>=20
> It's one of the things I personally wanted to see changed before the=20
> move into the core.
>=20
> Juergen
>=20
>=20
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On=20
> Behalf Of Cris J. Holdorph
> Sent: Thursday, July 07, 2005 5:43 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] old dependencies on spring=20
> portlet in webflow
>=20
> Can we PLEASE PLEASE consider changing the two "handleRequest" methods =

> to different names?  This is a violation of what is consider good=20
> practice for overriding.  They are fundamentally different methods.
> This change REALLY should be made before it is moved into the core.
>=20
> ---- Cris J H
>=20
> Juergen Hoeller wrote:
> > Hi Tim.
> >
> > We actually intend to release the core Portlet support earlier now:=20
> > as part of Spring 1.2.3 in about two weeks. Web Flow RC1 will in=20
> > turn build on that release then.
> >
> > 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.
> >
> > Juergen
> >
> >
> > --------------------------------------------------------------------
> > --
> > --
> > *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
> >
> >
> >
> > This really addresses two issues I'm having w/ spring portlet=20
> > development.  I am attempting to use spring webflow /w the portlets, =

> > and the PR3 release of webflow apparently includes references to=20
> > older versions of portlet code (that exist in the spring sandbox) -=20
> > and the latest version of spring-portlets as released by john lewis=20
> > includes significantly updated code, and when attempting to include=20
> > all those jars in the portlet environment, theres all sorts of=20
> > classloader issues w/ different versions of DispatchPortlet and=20
> > PortletController lying around.  I've been trying to rebuild parts=20
> > to get them all to talk to each other, but it's been a big =
time-sink.
> >
> >
> >
> > 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.
> > 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 =

> > things can move in that direction.
> >
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies =

> from IBM. Find simple to follow Roadmaps, straightforward articles,=20
> 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=20
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar=20
> happening July 14 at 8am PDT/11am EDT. We invite you to explore the=20
> latest in dual core and dual graphics technology at this free one hour =

> event hosted by HP, AMD, and NVIDIA.  To register visit=20
> http://www.hp.com/go/dualwebinar=20
> _______________________________________________
> Springframework-developer mailing list=20
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar =
happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by =
HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer