Three things are messed up in pluto 1.1 right now
==== Bug in pageId lookup in trunk ======
======= Neither trunk nor beta1 will build unless maven.test.skip=true ========
===== The beta1 tag builds but will not pluto:install =======
Daily Archives: August 27, 2006
Make sure and come back and fix UsageSessionService
UsageSessionSerivce needs a new method that does not demand an Authorization not a httprequest as a parameter.
For now the code is living in SakaiPortalLogin.jws and SakaiLogin.jws so these can be used in older versions of Sakai.
Need to add the method the the BASE API, test it out, then commit it – then sometime later – likey *after* 2.3 – remove the code from the two web service calls.
Pluto 1.1 Bug Session’s living across server restart
There is a bug (I think) in session handling in Pluto 1.1. Why would Pluto 1.1 keep a session across a Tomcat restart!
I think that this has to do with Tomcat’s session serialization across startups and Pluto’s blind dependence on Tomcat session for storing the Pluto session.
../work/Catalina/localhost/sakai-portlets/SESSIONS.ser
If I am crazy – just tell me so.
Finding an IP Address in a JWS
http://radio.javaranch.com/balajidl/2006/02/06/1139245423141.html
//based on Axis 1.3
import org.apache.axis.Constants;
import org.apache.axis.MessageContext;
….
….
MessageContext messageContext = MessageContext.getCurrentContext();
String ipAddress = messageContext.getStrProp(Constants.MC_REMOTE_ADDR);