The errors you see in the testsuite are probably due to bugs in 1.1. While 1.1 is mostly functional, it still has many rough edges and we have progress to do. I think currently about 75% of the testsuite passes.
I'm currently working on the session problems. Action Parameters would be my next priority, though I'm also in the middle of some portal enhancements that I may get distracted by.
David
On 10/26/05, Graham Klyne <[EMAIL PROTECTED]> wrote:
David H. DeWolf wrote:
> Everything looks good in the new install. I think the only error now is
> that our index page IS simply a Hello World page. We should probably
> make it redirect to:
>
> http://localhost:8080/pluto/portal
>
> If you go there manually, I'll bet you see the portal.
Yes, you're right! I should have thought of that. Now I think I'm
nearly back to where I was with 1.0.1.
Running quickly through the tests, get failures from the following:
Simple Action Parameter Test - "RESULT NOT FOUND"
External App Scoped Attribute Test -
I still need to do 'emptySessionPath="true"'
Simple Preference Test - "RESULT NOT FOUND"
Window State Test -
when I select 'min', the sub-window disappears completely:
is that right?
Misc Test -
"Portal info: pluto-portal-driver/1.1-ALPHA.
Expected: pluto-driver/1.1.0-ALPHA"
Security Mapping Test - get a warning; I should try logging in
Resource Bundle Test - multiple failures:
Get Property Keys Test Keys:
javax.portlet.short-title, are not defined.
checkGetGermanBundle
checkGetEnglishBundle
> I'll take a look through the diff, but my guess is that the differences
> are due to 1) the exe install and 2) previously installing pluto 1.0.1.
> Perhaps we should investigate and document an "upgrade" path.
I hope it's not the former. I'll have a go at doing a new Tomcat .exe
install and see if that works. I'll let you know.
#g
--
Graham Klyne
Research Technology Service
Oxford University Computing Services
