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

[Tim K. <tim...@vi...>]

 

Hi Erwin,

 

Can you give a little more information about the timeline (at least how you
see it) for the SWF 1.0 / 1.2.3 release.  We are trying to set up some
priorities here in-house and we are hoping to use spring, portlets and SWF.
it is my understanding that 1.2.3 is due for a release next week.  Are you
anticipating on releasing SWF 1.0 at around the same time?  Is there
anything I can do to help with this?

 

-tim

 

  _____  

From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Erwin Vervaet
Sent: Friday, July 08, 2005 2:46 AM
To: spr...@li...
Subject: Re: [Springframework-developer] old dependencies on spring portlet
in webflow

 

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 ----- 

From: Juergen <mailto:ju...@in...>  Hoeller 

To: spr...@li... 

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

 

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.

 

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.