Quantcast

JA-SIG Conference: Building Portable Portlets

Chuck is talking a bit more about his experience with portlets, and the implications for uPortal, Sakai, etc. Sakai portlet notes: * Preferences – site.upd to change * Edit Mode – site.upd again * `isUserInRole()` mapped to Sakai permissions site.upd, content.read, etc. The `isUserInRole()` mapping seems a little counter-intuitive — seems like really portlet.xml should ...

I finally get REST. Wow.

I finally get REST. Wow. It’s depressing to think that SOAP started just about 10 years ago and that now that everything is said and done, we built RPC again. I know SOAP is really an XML messaging protocol, you can do oneway async stuff, etc, etc, but let’s face it. The tools make the ...

uP3 Day 6: More Layouts & GAPS

Published lots of portlets… edited lots of data.xml… really need a publishing tool. 🙂 Faizan’s been struggling all day without to much traction working on getting GAPS working – looks like some kinks between the updated PersonDirectory code and changes Dan’s been making on GAPS as the API evolves. I saw he posted last night ...

uP3 Day 5: More Person Directory & Data.xml Channel Publishing

Faizan’s PersonDirectory changes didn’t seem to take on my machine — not sure why, maybe the UserAttributesPortlet got patched, and I don’t have the most current version? I think he started looking at GAPS at home, but was running into some problems. I’m still looking at migrating our template user into the portal framework. For ...

uP3 Day 4: PersonDirectory & Portlet Publishing

Faizan got PersonDirectory working — after several updates and IRC exchanges with Eric. So uP3 now hits Rutgers LDAP to retrieve a mapping of our person attributes. Hard to test since the Portlet spec makes you explicitly declare the user attributes a portlet recieves. Probably privacy friendly, though writing a “show me all the attibutes” ...