Re: [Springframework-developer] Re: Portlet Form Controllers

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

That sounds like a good plan to me! It would be great to get this going
ASAP. After all, our timeplan for Spring 1.3 is pretty aggressive, so
waiting till after 1.2 final might not leave enough time.

Bill, Dmitriy, anyone volunteering to manage the sandbox code in the
meantime? :-) This would have to be someone with commit rights, after all,
and ideally someone already using the Portlet code.

First step would be to merge all existing contributions in. Let's assume
that the Portlet code will become part of Spring 1.3 proper (which is
likely), and continue to work on it in the sandbox.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Rainer Schmitz
Sent: Wednesday, March 30, 2005 11:53 AM
To: spr...@li...
Subject: Re: [Springframework-developer] Re: Portlet Form Controllers


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

While the "official" work on the Portlet support are postponed to Spring
1.3 I still would like to have a place for discussions and code
contributions. At this time the discussion is spread across this list,
the forum, confluence, and JIRA, which makes it hard to follow.

As for discussions, I would propose to stick to this list - we *are*
talking about Spring development, and this way the experienced Spring
developers may take the opportunity to participate.

As for code contributios: during the past couple of month several people
(William, Nick, John, and me) have contributed some code, but after each
contribution there was a big gap. One reason might be that it's very
inconvenient to get the up-to-date version of the code (none of the
changes made it into CVS; you have to fetch the sandbox version and copy
the content of several zip files from confluence). Without a proper code
management facility it's pointless to add more contributions.

I'm undecided wether portlet support should be part of main Spring or a
sub project, but for the time being it would really help if the portlet
code would be located at a place where all interested people could find
the up-to-date version and contribute enhancements. When the official
work in the Spring 1.3 context begins, this code could be an
implementation base for any portlet code handled in the traditional way.

What do you think?

Rainer



Juergen Hoeller schrieb:
> John,
>
> Sorry for the late reply. Thanks for volunteering! :-)
>
> Let's continue to proceed in the Portlet area once Spring 1.2 is out. Both
> Spring Web Flows and the Portlet support are currently planned to be
> cornerstones of Spring 1.3.
>
> Regarding commit rights, let's discuss this once 1.2 is out too. We're
> willing to extend the developer team, but there's a couple of things to be
> clarified (CLA etc).
>
> In the meantime, feel free to create a JIRA issue for your enhancements!
I'm
> sure that Dmitriy, Bill and co will be happy to have an early look at
this.
>
> Juergen
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCSnb7w+xsU7A7UOgRAo39AJ9LlKn1KvEOFzItXO83+oUoUhvMHgCfWoVy
rv556WE9CYsBzgbrTtkRqLU=
=qCQl
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer