On Feb 19, 2008, at 7:17 PM, Jay D. McHugh wrote:
Hey Joe (and everyone else),
I took a look at both the trunk and 1.1.* branches of Pluto and they
have not (or at least -appear- to have not) gotten around to
implementing the same 'secure portlet page' functionality that was
in 1.0.x.
But, I tried a suggestion that was on one of the Pluto mailing list
of simply commenting out the throwing of the exception (the only
thing that the setSecure() method does is throw an exception saying
that setSecure is not implemented).
In my testing, the https protocol is being carried along to the
successive pages though - so until Pluto does implement (or we
submit a patch for) secure portlet pages - It seems to me that we at
least need a functioning console. Once Pluto trunk or a release
begins supporting secure portlet pages - then we can get back onto
an unmodified copy.
I am in the middle of running through a full build with tests before
committing a new pinned version of Pluto.
Does anyone have any other thoughts before I do my commit?
Sounds good to me Jay. Thanks for digging into this one...
--kevan
