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

[Erwin V. <erw...@er...>]

We're going for a SWF PR4 release which will temporarily drop Portlet =
support but will work correctly on top of Spring 1.2.2. A SWF 1.0 =
release on top of Spring 1.2.3 with full Potlet support will follow =
shortly, as Juergen indicates.

Erwin Vervaet
erw...@er...
  ----- Original Message -----=20
  From: Juergen Hoeller=20
  To: spr...@li...=20
  Sent: Thursday, July 07, 2005 12:41 PM
  Subject: Re: [Springframework-developer] old dependencies on spring =
portlet in webflow


  Hi Tim.

  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 build =
on that release then.

  For the meantime, there might be a Web Flow PR4 as a remedy for the =
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 Behalf =
Of Tim Kettering
  Sent: Wednesday, July 06, 2005 7:56 PM
  To: spr...@li...
  Subject: [Springframework-developer] old dependencies on spring =
portlet in webflow


  =20

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

  =20

  I see the best solution being that John being allowed to merge his =
portlet code in the cvs - so that webflow can be coded against the =
proper classes and those classes being dropped from webflow-support.  I =
know that this has been under discussion lately to start with 1.3 =
development, and I'm hoping with the release of 1.2.2 complete, that =
things can move in that direction.