[Building Sakai] Portals and transactions

[Sean Keesler]

My experience is that changing the xsl-portal is a lot easier than the
default portal that Sakai runs with OOTB.
To use the xsl-portal set the following sakai or local.properties:

               portalPath=/xsl-portal
               toolPath=/xsl-portal/tool
               loggedOutUrl=/xsl-portal
               xslt-portal.cacheTemplates=false (while developing the
look and feel...set it to true to improve performance after you're
done)

Your skin will include all of the your css files and an xsl file which
you can copy from:
osp/xsltcharon//xsltcharon-portal/xsl-portal/src/webapp/WEB-INF/transform/portal.xsl
as a starter. If you don't specify one, that is the one it ends up
using.

>From there you can modify your portal html with XSL and skin it with your CSS.


Sean Keesler
130 Academy Street
Manlius, New York 13104 USA
315-663-7756
sean.keesler at threecanoes.com



On Fri, Nov 13, 2009 at 5:13 AM, Tania Tritean <ttritean at loi.nl> wrote:
> Any ideas about the problems below?
>
>
>
> Thanks
>
>
>
>
>
> ________________________________
>
> From: sakai-dev-bounces at collab.sakaiproject.org
> [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Tania
> Tritean
> Sent: Wednesday, November 11, 2009 4:26 PM
> To: sakai-dev at collab.sakaiproject.org
> Subject: [Building Sakai] Portals and transactions
>
>
>
>
>
>
>
> ________________________________
>
> Hi,
>
>
>
> I have 2 questions, if somebody can help meJ :
>
>
>
> Question 1 – About Sakai Portals (sakai version 2.5.3)
>
>
>
> How can we create a new Sakai portal? I’ve been looking for some
> documentation on this or maybe a short guide on creating/adjusting Sakai
> portals, but didn’t find anything atm.
>
> For example we would like a portal that contains only the header (with the
> Sakai logo and the login) and the content sections displayed.
>
>
>
>
>
> Question 2 – About transactions on Sakai Services
>
>
>
> We are using several Sakai services on various purposes, and we would like
> to have everything transactional.
>
> How can we wrap this services in transactions?
>
> Here is the list of the Sakai services we are using is:
>
> -          org.sakaiproject.component.api.ServerConfigurationService
>
> -          org.sakaiproject.user.api.UserDirectoryService
>
> -          org.sakaiproject.tool.api.SessionManager
>
> -          org.sakaiproject.site.api.SiteService
>
> -          org.etudes.mneme.api.SubmissionService
>
> -          org.etudes.mneme.api.AssessmentService
>
> -          org.sakaiproject.authz.api.AuthzGroupService
>
> -          org.sakaiproject.entity.api.EntityManager
>
> -          org.sakaiproject.tool.api.ToolManager
>
>
>
> We tried an approach like bellow:
>
>             <bean id="transactionalServerConfigurationService"
> class="org.springframework.transaction.interceptor.TransactionProxyFactoryBean">
>
>                         <property name="transactionManager"
> ref="org.sakaiproject.springframework.orm.hibernate.GlobalTransactionManager"/>
>
>                         <property name="target"
> ref="org.sakaiproject.component.api.ServerConfigurationService"/>
>
>                         <property name="transactionAttributes">
>
>                                    <props>
>
>                                                <prop
> key="*">PROPAGATION_REQUIRED</prop>
>
>                                    </props>
>
>                         </property>
>
>             </bean>
>
>
>
> but it didn’t worked for all services for the list above.
>
>
>
> Can someone give us a hint about how this should be done? (maybe our
> approach was not the right one)
>
>
>
>
>
>
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"
>