Menu
▾
▴
springframework-developer
|
From: John L. <jl...@ar...> - 2005-06-09 18:06:15
|
I just posted a major update to the Spring Portlet MVC Framework. It is available here: http://opensource.atlassian.com/confluence/spring/display/JSR168/Home This update includes a number of major changes: * It is now integrated with (and requires) Spring 1.2. All classes have been updated with changes from their equivalent classes from the Servlet area. * A number of classes have been renamed and/or moved into different packages in order to better align it with the Servlet MVC framework. * The concept of Handlers is now included, instead of directly mapping to Controllers. This will allow other Portlet MVC frameworks to be used with a Spring web application. * Expanded controller hierarchy that more closely follows the Servlet MVC framework. * A number of HandlerMappings are now provided, including one for PortletMode, one for a request parameter, and one for PortletMode combined with a request parameter. * OpenSessionInViewInterceptor for both Hibernate 2 and Hibernate 3 are now included and fully functional. * Lots of other minor updates and bug fixes. Please send me any feedback. Juergen, what are your current thoughts on getting this integrated into the sandbox and into Spring 1.3? John Lewis jl...@ar... |
|
From: Martin D. <mdu...@gm...> - 2005-06-09 19:46:47
|
Hi John, thank you very much for this! I am using the framework in production and it works great. Hope there will be an official home for the portlet MVC soon. I beg the spring team to decide soon about the future of the framework. Either in the core or as a subproject. But the current situation is not very good. In my opinion the portlet MVC is an outstanding framework to build portlets. Martin 2005/6/9, John Lewis <jl...@ar...>: > I just posted a major update to the Spring Portlet MVC Framework. It is > available here: >=20 > http://opensource.atlassian.com/confluence/spring/display/JSR168/Home >=20 > This update includes a number of major changes: > * It is now integrated with (and requires) Spring 1.2. All classes have > been updated with changes from their equivalent classes from the Servlet > area. > * A number of classes have been renamed and/or moved into different > packages in order to better align it with the Servlet MVC framework. > * The concept of Handlers is now included, instead of directly mapping > to Controllers. This will allow other Portlet MVC frameworks to be used > with a Spring web application. > * Expanded controller hierarchy that more closely follows the Servlet > MVC framework. > * A number of HandlerMappings are now provided, including one for > PortletMode, one for a request parameter, and one for PortletMode > combined with a request parameter. > * OpenSessionInViewInterceptor for both Hibernate 2 and Hibernate 3 are > now included and fully functional. > * Lots of other minor updates and bug fixes. >=20 > Please send me any feedback. >=20 > Juergen, what are your current thoughts on getting this integrated into > the sandbox and into Spring 1.3? >=20 > John Lewis > jl...@ar... >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you sho= tput > a projector? How fast can you ride your desk chair down the office luge t= rack? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Keith D. <ke...@in...> - 2005-06-09 20:10:11
|
Yes, the sandbox is not the place for code such as Spring Porlet or Spring Web Flow. The sandbox should really be only for scratch code that is truly experimental. This weekend Spring Web Flow will move to its own module within the springframework project repository, along with a major upgrade to its build system. I propose something similiar happen to Spring Portlet. Specifically I could see Spring Portlet as either: - A core module hosted at the main springframework site, maintained by core spring developers, with its own release schedule. OR - A Spring module hosted at the java.net site. In either case all modules should leverage our new common project build system using ivy for automated dependency management. Colin has put a lot of effort into a very strong build system essential to managing dependencies between our various products--and Spring Web Flow and Spring Portlet are both core products. So the question is which home is better for Spring Portlet: here at sourceforge, or over at Spring Modules, right? We favor hosting Web Flow here at SF along side springframework as it's a *core product* maintained by core spring developers. Spring Portlet seems similiar to me. And in general, Spring modules seems a better fit for smaller, focused extension products, e.g commons validator with a wider committer community -- so my gut tells me Spring Portlet should also be hosted here as well. Thoughts? Keith p.s. great to see the Portlet MVC work moving forward! > Hi John, > > thank you very much for this! > > I am using the framework in production and it works great. Hope there > will be an official home for the portlet MVC soon. > > I beg the spring team to decide soon about the future of the > framework. Either in the core or as a subproject. But the current > situation is not very good. In my opinion the portlet MVC is an > outstanding framework to build portlets. > > Martin > > > 2005/6/9, John Lewis <jl...@ar...>: >> I just posted a major update to the Spring Portlet MVC Framework. It is >> available here: >> >> http://opensource.atlassian.com/confluence/spring/display/JSR168/Home >> >> This update includes a number of major changes: >> * It is now integrated with (and requires) Spring 1.2. All classes have >> been updated with changes from their equivalent classes from the Servlet >> area. >> * A number of classes have been renamed and/or moved into different >> packages in order to better align it with the Servlet MVC framework. >> * The concept of Handlers is now included, instead of directly mapping >> to Controllers. This will allow other Portlet MVC frameworks to be used >> with a Spring web application. >> * Expanded controller hierarchy that more closely follows the Servlet >> MVC framework. >> * A number of HandlerMappings are now provided, including one for >> PortletMode, one for a request parameter, and one for PortletMode >> combined with a request parameter. >> * OpenSessionInViewInterceptor for both Hibernate 2 and Hibernate 3 are >> now included and fully functional. >> * Lots of other minor updates and bug fixes. >> >> Please send me any feedback. >> >> Juergen, what are your current thoughts on getting this integrated into >> the sandbox and into Spring 1.3? >> >> John Lewis >> jl...@ar... >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: NEC IT Guy Games. How far can you >> shotput >> a projector? How fast can you ride your desk chair down the office luge >> track? >> If you want to score the big prize, get to know the little guy. >> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you > shotput > a projector? How fast can you ride your desk chair down the office luge > track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > -- Keith Donald Principal Consultant, Interface21 http://www.springframework.com - Spring Services From the Source |
|
From: John L. <jl...@ar...> - 2005-06-09 20:28:54
|
Donald, Thansk for the quick feedback -- I agree with all of it. I think the Portlet MVC framework should be a core product as well, particularly because other areas (such as Spring Web Flow) are already starting to depend on it. Also, since it so closely mirrors the servlet Web MVC framework, it would be good to keep them together so that their functionality can be kept in sync. There is a fair amount of rendundant code between the Portlet and Servlet frameworks, and keeping them together will make it possible to refactor a lot of this code. Let me know what I can do to help. John Lewis Keith Donald wrote: > Yes, the sandbox is not the place for code such as Spring Porlet or Spring > Web Flow. The sandbox should really be only for scratch code that is > truly experimental. > > This weekend Spring Web Flow will move to its own module within the > springframework project repository, along with a major upgrade to its > build system. I propose something similiar happen to Spring Portlet. > > Specifically I could see Spring Portlet as either: > > - A core module hosted at the main springframework site, maintained by > core spring developers, with its own release schedule. > > OR > > - A Spring module hosted at the java.net site. > > In either case all modules should leverage our new common project build > system using ivy for automated dependency management. Colin has put a lot > of effort into a very strong build system essential to managing > dependencies between our various products--and Spring Web Flow and Spring > Portlet are both core products. > > So the question is which home is better for Spring Portlet: here at > sourceforge, or over at Spring Modules, right? We favor hosting Web Flow > here at SF along side springframework as it's a *core product* maintained > by core spring developers. Spring Portlet seems similiar to me. And in > general, Spring modules seems a better fit for smaller, focused extension > products, e.g commons validator with a wider committer community -- so my > gut tells me Spring Portlet should also be hosted here as well. > > Thoughts? > > Keith > > p.s. great to see the Portlet MVC work moving forward! > > > >>Hi John, >> >>thank you very much for this! >> >>I am using the framework in production and it works great. Hope there >>will be an official home for the portlet MVC soon. >> >>I beg the spring team to decide soon about the future of the >>framework. Either in the core or as a subproject. But the current >>situation is not very good. In my opinion the portlet MVC is an >>outstanding framework to build portlets. >> >>Martin >> >> >>2005/6/9, John Lewis <jl...@ar...>: >> >>>I just posted a major update to the Spring Portlet MVC Framework. It is >>>available here: >>> >>>http://opensource.atlassian.com/confluence/spring/display/JSR168/Home >>> >>>This update includes a number of major changes: >>>* It is now integrated with (and requires) Spring 1.2. All classes have >>>been updated with changes from their equivalent classes from the Servlet >>>area. >>>* A number of classes have been renamed and/or moved into different >>>packages in order to better align it with the Servlet MVC framework. >>>* The concept of Handlers is now included, instead of directly mapping >>>to Controllers. This will allow other Portlet MVC frameworks to be used >>>with a Spring web application. >>>* Expanded controller hierarchy that more closely follows the Servlet >>>MVC framework. >>>* A number of HandlerMappings are now provided, including one for >>>PortletMode, one for a request parameter, and one for PortletMode >>>combined with a request parameter. >>>* OpenSessionInViewInterceptor for both Hibernate 2 and Hibernate 3 are >>>now included and fully functional. >>>* Lots of other minor updates and bug fixes. >>> >>>Please send me any feedback. >>> >>>Juergen, what are your current thoughts on getting this integrated into >>>the sandbox and into Spring 1.3? >>> >>>John Lewis >>>jl...@ar... >>> >>>------------------------------------------------------- >>>This SF.Net email is sponsored by: NEC IT Guy Games. How far can you >>>shotput >>>a projector? How fast can you ride your desk chair down the office luge >>>track? >>>If you want to score the big prize, get to know the little guy. >>>Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 >>>_______________________________________________ >>>Springframework-developer mailing list >>>Spr...@li... >>>https://lists.sourceforge.net/lists/listinfo/springframework-developer >>> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: NEC IT Guy Games. How far can you >>shotput >>a projector? How fast can you ride your desk chair down the office luge >>track? >>If you want to score the big prize, get to know the little guy. >>Play to win an NEC 61" plasma display: http://www.necitguy.com/?r >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > > > |
|
From: Erwin V. <erw...@er...> - 2005-06-09 20:41:09
|
> Thansk for the quick feedback -- I agree with all of it. I think the > Portlet MVC framework should be a core product as well, particularly > because other areas (such as Spring Web Flow) are already starting to > depend on it. Also, since it so closely mirrors the servlet Web MVC > framework, it would be good to keep them together so that their > functionality can be kept in sync. There is a fair amount of rendundant > code between the Portlet and Servlet frameworks, and keeping them together > will make it possible to refactor a lot of this code. Great to see this kind of activity with the PortletMVC code. Seems like Spring 1.3 preparation are starting up! Erwin |
|
From: Colin S. <col...@ex...> - 2005-06-09 21:27:09
|
I really think it makes complete sense for this to be part of the main project, as a separate module alongside the webflow and any other modules that are brought out. The common-build stuff I got going in the spring-modules module in CVS can easily handle dependencies between everything, and allow people to concentrate on the code and not the build or dependency handling. It's now been proven in real use too. Regards, Colin John Lewis wrote: > Donald, > > Thansk for the quick feedback -- I agree with all of it. I think the > Portlet MVC framework should be a core product as well, particularly > because other areas (such as Spring Web Flow) are already starting to > depend on it. Also, since it so closely mirrors the servlet Web MVC > framework, it would be good to keep them together so that their > functionality can be kept in sync. There is a fair amount of > rendundant code between the Portlet and Servlet frameworks, and > keeping them together will make it possible to refactor a lot of this > code. > > Let me know what I can do to help. > > John Lewis > > > Keith Donald wrote: > >> Yes, the sandbox is not the place for code such as Spring Porlet or >> Spring >> Web Flow. The sandbox should really be only for scratch code that is >> truly experimental. >> >> This weekend Spring Web Flow will move to its own module within the >> springframework project repository, along with a major upgrade to its >> build system. I propose something similiar happen to Spring Portlet. >> >> Specifically I could see Spring Portlet as either: >> >> - A core module hosted at the main springframework site, maintained by >> core spring developers, with its own release schedule. >> >> OR >> >> - A Spring module hosted at the java.net site. >> >> In either case all modules should leverage our new common project build >> system using ivy for automated dependency management. Colin has put >> a lot >> of effort into a very strong build system essential to managing >> dependencies between our various products--and Spring Web Flow and >> Spring >> Portlet are both core products. >> >> So the question is which home is better for Spring Portlet: here at >> sourceforge, or over at Spring Modules, right? We favor hosting Web >> Flow >> here at SF along side springframework as it's a *core product* >> maintained >> by core spring developers. Spring Portlet seems similiar to me. And in >> general, Spring modules seems a better fit for smaller, focused >> extension >> products, e.g commons validator with a wider committer community -- >> so my >> gut tells me Spring Portlet should also be hosted here as well. >> >> Thoughts? >> >> Keith >> >> p.s. great to see the Portlet MVC work moving forward! >> >> >> >>> Hi John, >>> >>> thank you very much for this! >>> >>> I am using the framework in production and it works great. Hope there >>> will be an official home for the portlet MVC soon. >>> >>> I beg the spring team to decide soon about the future of the >>> framework. Either in the core or as a subproject. But the current >>> situation is not very good. In my opinion the portlet MVC is an >>> outstanding framework to build portlets. >>> >>> Martin >>> >>> >>> 2005/6/9, John Lewis <jl...@ar...>: >>> >>>> I just posted a major update to the Spring Portlet MVC Framework. >>>> It is >>>> available here: >>>> >>>> http://opensource.atlassian.com/confluence/spring/display/JSR168/Home >>>> >>>> This update includes a number of major changes: >>>> * It is now integrated with (and requires) Spring 1.2. All classes >>>> have >>>> been updated with changes from their equivalent classes from the >>>> Servlet >>>> area. >>>> * A number of classes have been renamed and/or moved into different >>>> packages in order to better align it with the Servlet MVC framework. >>>> * The concept of Handlers is now included, instead of directly mapping >>>> to Controllers. This will allow other Portlet MVC frameworks to be >>>> used >>>> with a Spring web application. >>>> * Expanded controller hierarchy that more closely follows the Servlet >>>> MVC framework. >>>> * A number of HandlerMappings are now provided, including one for >>>> PortletMode, one for a request parameter, and one for PortletMode >>>> combined with a request parameter. >>>> * OpenSessionInViewInterceptor for both Hibernate 2 and Hibernate 3 >>>> are >>>> now included and fully functional. >>>> * Lots of other minor updates and bug fixes. >>>> >>>> Please send me any feedback. >>>> >>>> Juergen, what are your current thoughts on getting this integrated >>>> into >>>> the sandbox and into Spring 1.3? >>>> >>>> John Lewis >>>> jl...@ar... >>>> >>>> ------------------------------------------------------- >>>> This SF.Net email is sponsored by: NEC IT Guy Games. How far can you >>>> shotput >>>> a projector? How fast can you ride your desk chair down the office >>>> luge >>>> track? >>>> If you want to score the big prize, get to know the little guy. >>>> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 >>>> _______________________________________________ >>>> Springframework-developer mailing list >>>> Spr...@li... >>>> https://lists.sourceforge.net/lists/listinfo/springframework-developer >>>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by: NEC IT Guy Games. How far can you >>> shotput >>> a projector? How fast can you ride your desk chair down the office luge >>> track? >>> If you want to score the big prize, get to know the little guy. >>> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework-developer >>> >> >> >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you > shotput > a projector? How fast can you ride your desk chair down the office > luge track? > If you want to score the big prize, get to know the little guy. Play > to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Erwin V. <erw...@er...> - 2005-06-09 20:37:43
|
> So the question is which home is better for Spring Portlet: here at > sourceforge, or over at Spring Modules, right? We favor hosting Web Flow > here at SF along side springframework as it's a *core product* maintained > by core spring developers. Spring Portlet seems similiar to me. And in > general, Spring modules seems a better fit for smaller, focused extension > products, e.g commons validator with a wider committer community -- so my > gut tells me Spring Portlet should also be hosted here as well. I agree. It would be a bit strange to have a 'core product' like SWF depend on an add-on module like Spring PortletMVC, if that's how we would organize it. Ofcourse we could also decide to move the Portlet MVC support in SWF over to the Portlet module, instead of keeping it with SWF. Erwin |
