Continued Activity

Today the goal is to make sure uP3 can work with all of Sakai and try to do all the patches with changes to the uP3 build.xml rather than patches to my tomcat instance after the fact.
Start with clean Tomcat, deploy full Sakai – modify build.xml in uPortal – deploy uP, Drat – forgot “ant hsql” in my quickstart – I must figure out how to do this without my quickstart crutch.
Sweet – both come up with nothing more than uP3 build.xml changes commenting out jar deployments.
vi webpages/stylesheets/uP2/adaptedLayoutSample.xml
cp webpages/stylesheets/uP2/adaptedLayoutSample.xml ~/dev/jakarta-tomcat-5.5.9/webapps/uP3/WEB-INF/classes/uP2/adaptedLayoutSample.xml
oops – layout is now in a database.
vi properties/db/data.xml
Sweet – admin now has a Sakai folder… Now what to do about it?
– Stick in the Sakai-168 portlet?
– Stick in a iframe to Charon
– Build a peer to Charon?
– Modify the 168 portlet to short-circuit web services when in the same JVM
– What about making worksites dynamically appear as possible channels…
– What about making registered Sakai tools appear as uPortal channels and when placed they get context that is completely unique.
And how to do all this without adding hard Sakai dependencies throughout uPortal. (i.e. how to best factor all of this stuff??) Hmmm.