Hi Eric, This sounds great, we are really looking forward to JSR-286 support. Any chance of cutting a few preview or beta releases before the official release (3.3?)
cheers, Steve On 10/07/2010, at 1:05 PM, Eric Dalquist wrote: > Well the pluto 2 branch is finally at the point where portlets are generally > functional. There are still things missing (like an error display if a > portlet throws an exception) as well as most of the more complex JSR-286 > features need work. With that said I think I'd like to start working on > merging the pluto 2 branch into trunk next week. I would do the merge locally > and get the changes moved into SVN in a single commit. I just want to make > sure I'm not stepping on other developers toes when I do this though. > > Here is a list of changes as well as issues I know about: > Pluto 2 integration, which means JSR-286 support! > Channels don't work anymore! > JSR-286 events, public parameters, URL properties and a few other things > don't actually work yet > Upgraded to Spring 3.0 > Switched to @Autowired as much as possible, the spring context files are MUCH > smaller now > Consistent portal URLs have been implemented: > https://wiki.jasig.org/display/UPC/Consistent+Portal+URLs > The new URL syntax means that the portal context is the last folder in the > path. The CSS/JS/Image URLs in the theme have all been fixed but all of the > JavaScript callbacks have not. That means very little of the dynamic UI will > work until we go through and get those URLs updated so they are always > absolute. > No CError replacement yet. This means if an exception is thrown while a > portlet is rendering there will be no content for that portlet. If an > exception is thrown during an action I think you just get a blank page. > Exceptions are logged plus hitting refresh actually does re-render everything > on the page. > Lots of missing content in the default layout. A lot of our default content > was still channel based, none of that renders anymore since channels don't > work. > Very little code has been removed yet. I wanted to wait until after the merge > back to trunk was complete and the Pluto 2 integration was better flushed > out. So while things like ChannelManager and ChannelRenderer are still in the > code they are not used anymore. Once we get the Pluto 2 integration more > stable we can start going through and essentially removing anything with > "channel" in the class name (or at least that's the hope). > > So I'll be starting on this merging locally in the next few days, it will be > at least a week before I have something ready to actually commit to trunk. If > I hear objections before then we'll get them addressed, if not I'll post > again when the merge happens! > > -Eric
smime.p7s
Description: S/MIME cryptographic signature
