tag:old.nabble.com,2006:forum-18101Nabble - Sakai2009-11-23T18:17:41Z<a href="http://www.sakaiproject.org/" target="_top" rel="nofollow">Sakai</a> is an online Collaboration and Learning Environment. Many users of Sakai deploy it to support teaching and learning, ad hoc group collaboration, support for portfolios and research collaboration.
<br><br>Sakai is a free and open source product that is built and maintained by the Sakai community. Sakai's development model is called "Community Source" because many of the developers creating Sakai are drawn from the "community" of organizations that have adopted and are using Sakai.tag:old.nabble.com,2006:post-26489534Re: [Building Sakai] Export calendar problem.2009-11-23T18:17:41Z2009-11-23T18:17:41ZSam ChowDear Beth,
<br><br>Thanks for your reply, i am looking for information to export the merged
<br>calendars of a teacher.
<br><br>Best Regards,
<br>Sam
<br><br>----- Original Message -----
<br>From: "Beth Kirschner" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=0" target="_top" rel="nofollow">bkirschn@...</a>>
<br>To: "Sam Chow" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=1" target="_top" rel="nofollow">samchow@...</a>>
<br>Cc: <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=2" target="_top" rel="nofollow">sakai-dev@...</a>>
<br>Sent: Monday, November 23, 2009 11:12 PM
<br>Subject: Re: [Building Sakai] Export calendar problem.
<br><br><div class='shrinkable-quote'><br>> The export will only work on individual calendars (not merged calendars
<br>> in your "My Workspace"), so you'll have to export your teacher's class
<br>> calendar separately.
<br>>
<br>> - Beth
<br>>
<br>> On Nov 20, 2009, at 2:33 AM, Sam Chow wrote:
<br>>
<br>>> Dear Beth,
<br>>>
<br>>> After i modifiied this java method, its work fine. Many Thanks.
<br>>>
<br>>> But i found that, the exported ical didnt include the schedule of the
<br>>> teacher's class. Any idea, if i want the exported icalendar include all
<br>>> of the teacher schedlue? Many Thanks.
<br>>>
<br>>>
<br>>> Best Regards,
<br>>> Sam Chow
<br>>>
<br>>>
<br>>> ----- Original Message ----- From: "Beth Kirschner" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=3" target="_top" rel="nofollow">bkirschn@...</a>
<br>>> >
<br>>> To: "Sam Chow" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=4" target="_top" rel="nofollow">samchow@...</a>>
<br>>> Cc: <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=5" target="_top" rel="nofollow">sakai-dev@...</a>>
<br>>> Sent: Thursday, November 19, 2009 9:47 PM
<br>>> Subject: Re: [Building Sakai] Export calendar problem.
<br>>>
<br>>>
<br>>>> Hi Sam,
<br>>>>
<br>>>> If you'd like to have the DTEND field included, you should write up
<br>>>> your request in JIRA
<br>>>> (<a href="http://jira.sakaiproject.org/secure/Dashboard.jspa" target="_top" rel="nofollow">http://jira.sakaiproject.org/secure/Dashboard.jspa</a> ) and if possible,
<br>>>> submit a patch to go along with it. The code that generates the iCal
<br>>>> events is in the
<br>>>> org.sakaiproject.calendar.impl.BaseCalendarService.generateIcal()
<br>>>> method.
<br>>>>
<br>>>> - Beth
<br>>>>
<br>>>> On Nov 19, 2009, at 3:05 AM, Sam Chow wrote:
<br>>>>
<br>>>>> Dear Sir,
<br>>>>>
<br>>>>> I am using Sakai 2.6 and i have enabled the funciton of export a
<br>>>>> schedule in to a iCal file. I have set up a phpicalendar to link with
<br>>>>> the exported sakai calendar, but i found that the end time didnt
<br>>>>> show. After i check the iCal file, it have dtstart but dont have
<br>>>>> dtend. But so funny that google can get the end time, i guess it is
<br>>>>> using the Duration to get it.
<br>>>>>
<br>>>>> Can i add the DTEND in the exported iCal file?
<br>>>>>
<br>>>>> Many Thanks.
<br>>>>>
<br>>>>> Best Regards,
<br>>>>> Sam Chow
<br>>>>> _______________________________________________
<br>>>>> sakai-dev mailing list
<br>>>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=6" target="_top" rel="nofollow">sakai-dev@...</a>
<br>>>>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>>>>>
<br>>>>> TO UNSUBSCRIBE: send email to
<br>>>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=7" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of
<br>>>>> "unsubscribe"
<br>>>>
<br>>>
<br>>>
<br>>>
<br>>>
<br>>
<br>>
</div><br><br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=8" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26489534&i=9" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26488383Re: [DG: Teaching & Learning] [DG: User Experience] Leading Design2009-11-23T16:03:51Z2009-11-23T16:03:51ZDavid Goodrum-2<html><head></head><body><div style="font-family:tahoma, 'new york', times, serif;font-size:10pt"><div>It's been interesting to see the level of collaboration the document has seen and how it has evolved because of that collaboration.</div><div><br></div><div>According to Google docs, there's been at least 15 collaborators on the document... likely more, since no login is required to edit it -- it is a totally open brainstorming document right now.</div><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The spreadsheet is certainly not exhaustive nor complete, nor is that the intent for this phase. It currently does not necessarily reflect the best capabilities of <span class="yshortcuts" id="lw_1259019825_0" style="border-bottom-style: dashed; border-bottom-width: 1px; border-bottom-color: rgb(0, 102, 204); cursor: pointer;
">Sakai</span> 2.x; it does not reflect what all is missing or frustrating about Sakai 2.x; it does not reflect all of what Sakai 3 should aspire to; it doesn't even fully represent what teaching and learning goals should be supported in Sakai 3. So what's the point?</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">With 60+ rows right now, it begins to represent a fair cross section of many ambitions Sakai 3 perhaps ought to have in the teaching and learning space. </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">And it attempts to show how different levels of complexity and functional capabilities both link together and link back to a basic teaching and learning
goal, hopefully expressed in everyday language.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Perhaps a bad analogy for the document would be the recent cell coverage maps... Ideally, our teaching and learning map would look like Verizon's 3G map... with nearly the whole map filled in. This brainstorming document today is more like the <span class="yshortcuts" id="lw_1259019825_1" style="border-bottom-style: dashed; border-bottom-width: 1px; border-bottom-color: rgb(0, 102, 204); cursor: pointer; ">AT&T</span> 3G coverage map: a lot of white space still to be filled in, but there is coverage of many core areas and outlines of many others.</div><div><br></div><div>For now it's a place to play out some ideas.</div><div><br></div><div><span class="Apple-style-span" style="font-size:
small;">Got a teaching and learning idea? Something instructors want their students to do? Something students wish instructors would do? Something that <span class="Apple-style-span" style="-webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">develops collaboration and cooperation among students, encourages active learning, gives prompt feedback, emphasizes time on task, communicates high expectations, or respects diverse talents and ways of learning? Then add it to the brainstorm.</span></span></div><div><span class="Apple-style-span" style="font-size: small; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;"><br></span></div><div><span class="Apple-style-span" style="font-size: small; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;">- David</span></div></div><div style="font-family:tahoma, new york, times,
serif;font-size:10pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Clay Fenlason <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488383&i=0" target="_top" rel="nofollow">clay.fenlason@...</a>><br><b><span style="font-weight: bold;">To:</span></b> Sakai UX <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488383&i=1" target="_top" rel="nofollow">sakai-ux@...</a>>; pedagogy Learning <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488383&i=2" target="_top" rel="nofollow">pedagogy@...</a>><br><b><span style="font-weight: bold;">Sent:</span></b> Wed, November 18, 2009 7:28:43 PM<br><b><span style="font-weight: bold;">Subject:</span></b> [DG: User Experience] Leading Design<br></font><br>
In recent weeks I've been trying to promote the maturation of the<br>learning capabilities spreadsheet [1] that David Goodrum has<br>championed. At the same time I've heard concerns that it might come to<br>naught or not be listened to. Just a couple days ago Josh Baron was<br>asking me when and how I thought the spreadsheet might actually be<br>used to inform the design. I told him, "It's happening right now." I'm<br>not sure he believed me, so I made a blog post with evidence:<br><span><a target="_blank" href="http://sakaipm.wordpress.com" rel="nofollow">http://sakaipm.wordpress.com</a></span><br><br>~Clay<br><br>[1] <a href="https://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en" target="_blank" rel="nofollow">https://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en</a><br>_______________________________________________<br>sakai-ux mailing list<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488383&i=3" target="_top" rel="nofollow">sakai-ux@...</a><br><span><a target="_blank" href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a></span><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488383&i=4" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"<br></div></div><div style="position:fixed"></div>
<!-- cg7.c4.mail.gq1.yahoo.com compressed/chunked Mon Nov 23 15:10:44 PST 2009 -->
</div><br>
</body></html><br />_______________________________________________
<br>pedagogy mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488383&i=5" target="_top" rel="nofollow">pedagogy@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/pedagogy" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/pedagogy</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488383&i=6" target="_top" rel="nofollow">pedagogy-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Pedagogy-f24248.html" embed="fixTarget[24248]" target="_top" >Sakai - Pedagogy</a></p>tag:old.nabble.com,2006:post-26488380Re: [DG: User Experience] Leading Design2009-11-23T16:03:51Z2009-11-23T16:03:51ZDavid Goodrum-2<html><head></head><body><div style="font-family:tahoma, 'new york', times, serif;font-size:10pt"><div>It's been interesting to see the level of collaboration the document has seen and how it has evolved because of that collaboration.</div><div><br></div><div>According to Google docs, there's been at least 15 collaborators on the document... likely more, since no login is required to edit it -- it is a totally open brainstorming document right now.</div><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The spreadsheet is certainly not exhaustive nor complete, nor is that the intent for this phase. It currently does not necessarily reflect the best capabilities of <span class="yshortcuts" id="lw_1259019825_0" style="border-bottom-style: dashed; border-bottom-width: 1px; border-bottom-color: rgb(0, 102, 204); cursor: pointer;
">Sakai</span> 2.x; it does not reflect what all is missing or frustrating about Sakai 2.x; it does not reflect all of what Sakai 3 should aspire to; it doesn't even fully represent what teaching and learning goals should be supported in Sakai 3. So what's the point?</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">With 60+ rows right now, it begins to represent a fair cross section of many ambitions Sakai 3 perhaps ought to have in the teaching and learning space. </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">And it attempts to show how different levels of complexity and functional capabilities both link together and link back to a basic teaching and learning
goal, hopefully expressed in everyday language.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Perhaps a bad analogy for the document would be the recent cell coverage maps... Ideally, our teaching and learning map would look like Verizon's 3G map... with nearly the whole map filled in. This brainstorming document today is more like the <span class="yshortcuts" id="lw_1259019825_1" style="border-bottom-style: dashed; border-bottom-width: 1px; border-bottom-color: rgb(0, 102, 204); cursor: pointer; ">AT&T</span> 3G coverage map: a lot of white space still to be filled in, but there is coverage of many core areas and outlines of many others.</div><div><br></div><div>For now it's a place to play out some ideas.</div><div><br></div><div><span class="Apple-style-span" style="font-size:
small;">Got a teaching and learning idea? Something instructors want their students to do? Something students wish instructors would do? Something that <span class="Apple-style-span" style="-webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">develops collaboration and cooperation among students, encourages active learning, gives prompt feedback, emphasizes time on task, communicates high expectations, or respects diverse talents and ways of learning? Then add it to the brainstorm.</span></span></div><div><span class="Apple-style-span" style="font-size: small; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;"><br></span></div><div><span class="Apple-style-span" style="font-size: small; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;">- David</span></div></div><div style="font-family:tahoma, new york, times,
serif;font-size:10pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Clay Fenlason <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488380&i=0" target="_top" rel="nofollow">clay.fenlason@...</a>><br><b><span style="font-weight: bold;">To:</span></b> Sakai UX <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488380&i=1" target="_top" rel="nofollow">sakai-ux@...</a>>; pedagogy Learning <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488380&i=2" target="_top" rel="nofollow">pedagogy@...</a>><br><b><span style="font-weight: bold;">Sent:</span></b> Wed, November 18, 2009 7:28:43 PM<br><b><span style="font-weight: bold;">Subject:</span></b> [DG: User Experience] Leading Design<br></font><br>
In recent weeks I've been trying to promote the maturation of the<br>learning capabilities spreadsheet [1] that David Goodrum has<br>championed. At the same time I've heard concerns that it might come to<br>naught or not be listened to. Just a couple days ago Josh Baron was<br>asking me when and how I thought the spreadsheet might actually be<br>used to inform the design. I told him, "It's happening right now." I'm<br>not sure he believed me, so I made a blog post with evidence:<br><span><a target="_blank" href="http://sakaipm.wordpress.com" rel="nofollow">http://sakaipm.wordpress.com</a></span><br><br>~Clay<br><br>[1] <a href="https://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en" target="_blank" rel="nofollow">https://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en</a><br>_______________________________________________<br>sakai-ux mailing list<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488380&i=3" target="_top" rel="nofollow">sakai-ux@...</a><br><span><a target="_blank" href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a></span><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488380&i=4" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"<br></div></div><div style="position:fixed"></div>
<!-- cg7.c4.mail.gq1.yahoo.com compressed/chunked Mon Nov 23 15:10:44 PST 2009 -->
</div><br>
</body></html><br />_______________________________________________
<br>sakai-ux mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488380&i=5" target="_top" rel="nofollow">sakai-ux@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26488380&i=6" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---User-Experience-f30853.html" embed="fixTarget[30853]" target="_top" >Sakai - User Experience</a></p>tag:old.nabble.com,2006:post-26486503Re: [Building Sakai] Gradebook2 and Sakai 2.6.x2009-11-23T13:45:10Z2009-11-23T13:45:10ZKevin Chan<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks James, those additional SQL statements did the trick (as far as
loading of both the old and new Gradebooks go).<br>
<pre class="moz-signature" cols="72"> Kevin Chan
Operations Team
Educational Technology Services
University of California, Berkeley</pre>
<br>
On 11/20/09 1:24 PM, James Renfro wrote:
<blockquote cite="mid:bb0662030911201324lcb83368va686d5c0ac1a5391@mail.gmail.com" type="cite">Apologies, it looks like I managed to check in a slightly
newer patch under the 1.1.x branches, so the gradebook module's data
model objects are now up-to-date with trunk, rather than the 1.1.x sql
scripts. <br>
<br>
This is not an issue at all, since those fields will just be left null,
but you'll need to apply the following in your db:<br>
<br>
<a moz-do-not-send="true" href="https://source.sakaiproject.org/contrib/gradebook2/trunk/sakai/2-6-x/sql/oracle/GRBK-367.sql" target="_top" rel="nofollow">https://source.sakaiproject.org/contrib/gradebook2/trunk/sakai/2-6-x/sql/oracle/GRBK-367.sql</a><br>
<br>
and possibly also<br>
<br>
<a moz-do-not-send="true" href="https://source.sakaiproject.org/contrib/gradebook2/trunk/sakai/2-6-x/sql/oracle/GRBK-234.sql" target="_top" rel="nofollow">https://source.sakaiproject.org/contrib/gradebook2/trunk/sakai/2-6-x/sql/oracle/GRBK-234.sql</a><br>
<br>
I'll update the 1.1.x-dev and 1.1.x-test branches to fix this, and I'm
planning to bring gradebook2.sql up-to-date so that's the only script
new installers need to run.<br>
<br>
<br>
<br>
<div class="gmail_quote">On Thu, Nov 19, 2009 at 4:24 PM, Kevin Chan <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26486503&i=0" target="_top" rel="nofollow">kevin@...</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">Hi James,<br>
<br>
Thanks for the notes. With the exception of using the 1.1.x-dev branch
instead of 1.1.x-test, I had followed the instructions very closely
(there was a part of a patch to Assignments.java that failed (easily
merged) and some "alter table" SQL that were unnecessary as the added
columns are already in our 2.6.x DB) and had gotten errors as I
described previously.<br>
<br>
I rebuilt GB2 today with a clean copy of data from our production DB
and got the same results.<br>
<br>
If I try to view GB2, I get:<br>
<br>
org.sakaiproject.portal.api.PortalHandlerException:
org.sakaiproject.tool.api.ToolException: Request processing failed;
nested exception is
org.springframework.dao.InvalidDataAccessResourceUsageException: could
not execute query; nested exception is
org.hibernate.exception.SQLGrammarException: could not execute query
<br>
at
org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:769)<br>
...<br>
caused by: java.sql.SQLException: ORA-00904:
"GRADEBOOK0_"."DO_SHOW_ITEM_STATS": invalid identifier
<br>
--end of snippet<br>
<br>
I am not familiar with any table called "GRADEBOOK0", all Gradebook
tables begin with "GB_".<br>
<br>
If I try to view Gradebook, I get:<br>
<br>
org.sakaiproject.portal.api.PortalHandlerException:
org.sakaiproject.tool.api.ToolException: Cannot get value for
expression '#{bean.pageName ne 'gradebookSetup' &&
bean.userAbleToEditAssessments}'
<br>
at
org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:769)
<br>
caused by: org.sakaiproject.tool.api.ToolException: Cannot get
value for expression '#{bean.pageName ne 'gradebookSetup' &&
bean.userAbleToEditAssessments}'
<br>
--end of snippet<br>
<br>
Let me know if I should open a Jira ticket or if it is something that I
overlooked. Also, do you know if rSmart built GB2/2.6.x with the
default Sakai modules (like portal, we have a slightly customized
version of portal so maybe that is the problem) or if there were heavy
changes/other modules needed to make it work?
<div class="im"><br>
<br>
Thanks,<br>
<pre cols="72"> Kevin Chan
Operations Team
Educational Technology Services
University of California, Berkeley</pre>
<br>
</div>
<div>
<div class="h5">On 11/18/09 7:58 PM, James Renfro wrote:
<blockquote type="cite">Hi Kevin,<br>
It is definitely possible to get Gradebook2 working with a Sakai 2.6.x
deployment. RSmart has it running, and I'm working with it locally on
my desktop. Most of the other institutions that are using Gradebook2
are running 2.5.x afaik. <br>
<br>
Not sure which tag you're installing. We're currently running 1.1.3 in
production at UCDavis, and this is our current "recommended" build for
all institutions, but ootb that tag is organized to build against 2.5.x
right now. <br>
<br>
Versions 1.1.3, 1.1.4, and 1.1.5 are all the same as far as actual
code, and represent incremental improvements to the build process. <br>
<br>
For 2.6.x compatibility I would recommend 1.1.5, which has not yet been
cut, but which will soon be our latest fully QA'd version that has been
put together explicitly to build against 2.6.x -- it will still require
patches to be applied to both the original gradebook module and sam
module, which is unfortunately going to be the case for gb2 in general
at least until 2.7.x, but it should no longer require any patching to
the gradebook2 code itself to run against 2.6.x -- you can run this
code currently from our test branch. <br>
<br>
<a moz-do-not-send="true" href="https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test" target="_blank" rel="nofollow">https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test</a><br>
<br>
We should be cutting 1.1.5 itself in the next week, depending how long
the QA process takes, at which point the code will be at:<br>
<br>
<a moz-do-not-send="true" href="https://source.sakaiproject.org/contrib/gradebook2/tags/1.1.5" target="_blank" rel="nofollow">https://source.sakaiproject.org/contrib/gradebook2/tags/1.1.5</a><br>
<br>
<br>
If you're running with auto.ddl off, you will also need to run one or
more of the scripts included in:<br>
<br>
<a moz-do-not-send="true" href="https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test/client/src/sql/oracle/" target="_blank" rel="nofollow">https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test/client/src/sql/oracle/</a><br>
<br>
For other instructions you may want to consult the 2.6.x install
directions, if you haven't dug them out already (they have been updated
in the last few days to match the current code). <br>
<br>
<a moz-do-not-send="true" href="https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test/sakai/2-6-x/INSTALL.txt" target="_blank" rel="nofollow">https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test/sakai/2-6-x/INSTALL.txt</a><br>
<br>
Finally, you may want to tweak the version of 2.6.x for the build...
you can do this by running this script:<br>
<br>
<a moz-do-not-send="true" href="https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test/setSakaiVersion.sh" target="_blank" rel="nofollow">https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test/setSakaiVersion.sh</a><br>
<br>
<br>
Please let me know if you run into any problems,<br>
James<br>
<br>
<br>
<br>
<div class="gmail_quote">On Wed, Nov 18, 2009 at 5:06 PM, Kevin
Chan <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26486503&i=1" target="_top" rel="nofollow">kevin@...</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>
I am looking to do a test build of Gradebook2 as a part of UC Berkeley's<br>
Sakai 2.6.x deployment. It looks like rSmart has already completed this<br>
implementation and the effort to document/implement this is happening
in:<br>
<br>
<a moz-do-not-send="true" href="http://jira.sakaiproject.org/browse/GRBK-330" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/GRBK-330</a><br>
<a moz-do-not-send="true" href="http://jira.sakaiproject.org/browse/GRBK-422" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/GRBK-422</a><br>
<br>
Although I managed to compile GB2 with our code, there were some DB<br>
errors when I attempted to view both GB2 and the 2.6.x gradebook. This<br>
issue may very well be self generated (I am not working with a clean<br>
DB), but I just wanted to see if anyone can confirm that this is<br>
possible and any instruction (perhaps something not currently in any<br>
INSTALL.txt files) would be great.<br>
<br>
I am working with the GB2 1.1.x-dev branch as that appears to be the one<br>
that is being used for 2.6.x integration.<br>
<br>
Thanks,<br>
<br>
--<br>
Kevin Chan<br>
<br>
Operations Team<br>
Educational Technology Services<br>
University of California, Berkeley<br>
<br>
_______________________________________________<br>
sakai-dev mailing list<br>
<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26486503&i=2" target="_top" rel="nofollow">sakai-dev@...</a><br>
<a moz-do-not-send="true" href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_blank" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>
<br>
TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26486503&i=3" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with
a subject of "unsubscribe"<br>
</blockquote>
</div>
<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</blockquote>
</body>
</html>
<br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26486503&i=4" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26486503&i=5" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26484820Re: [Portfolio] portfolio Digest, Vol 9, Issue 232009-11-23T11:59:53Z2009-11-23T11:59:53ZAllison Mollica<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title></title>
</head>
<body marginleft="10" marginright="10" margintop="10" marginbottom="10">
<div align="left" style="text-align:left;"><font face="Geneva" size="+0" color="#000000" style="font-family:Geneva;font-size:10pt;color:#000000;">Thank you for contacting me. I am out of the office until November 30th and will get back to you then. Have a wonderful holiday! </font></div>
</body>
</html>
<br />_______________________________________________
<br>portfolio mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26484820&i=0" target="_top" rel="nofollow">portfolio@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/portfolio" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/portfolio</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26484820&i=1" target="_top" rel="nofollow">portfolio-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Portfolio-f18155.html" embed="fixTarget[18155]" target="_top" >Sakai - Portfolio</a></p>tag:old.nabble.com,2006:post-26483566[Announcements] Call for items for the November 26, 2009 Sakai Newsletter2009-11-23T10:34:15Z2009-11-23T10:34:15ZMargaret Wagner<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Please send suggestions for items for the Sakai Newsletter by 12:00 noon EST (GMT -5) on Wednesday, November 25, 2009 to:<br><br><br>Margaret Wagner<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26483566&i=0" target="_top" rel="nofollow">mwagner@...</a><br><br><br>Thanks!</body></html><br />_______________________________________________
<br>announcements mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26483566&i=1" target="_top" rel="nofollow">announcements@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/announcements" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/announcements</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26483566&i=2" target="_top" rel="nofollow">announcements-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Announce-f28489.html" embed="fixTarget[28489]" target="_top" >Sakai - Announce</a></p>tag:old.nabble.com,2006:post-26483128Re: [Building Sakai] Automating the site creation process AND Sakai 3 Groups2009-11-23T10:06:17Z2009-11-23T10:06:17ZRay DavisI think of the Oxford admin case as an example of using cross-context
<br>(or cross-site) group references: there is a "Course Administrators"
<br>space whose Sakai-managed membership list is used in many other contexts
<br>(or sites). When the only purpose of such a "site" is reaching
<br>group-management capabilities, then we could think of the "site" part as
<br>disposable.
<br><br>Another approach, though, is to make "navigable collaborative spaces"
<br>less dependent on traditional site creation and management. We often
<br>hear about institutions who would like to do something like "let
<br>academic department administrators have authoring access to all sites
<br>associated with courses in that department." If the necessary
<br>information to set this up is available externally, then there's no need
<br>to explicitly manage "sites".
<br><br>Example: Classics Admin Matthew logs in and sees on his dashboard:
<br><br>* My Contacts
<br>...
<br>* My Workspaces
<br>...
<br>* My Department
<br>** Byzantine Greek
<br>** Latin 1a
<br>*** Latin 1a 02 2009
<br>*** Latin 1a 03 2009
<br>...
<br><br>If information on Matthew's department and its courses and their
<br>enrollments is available to Sakai 3 (via IMS LIS or Kuali or LDAP, say),
<br>that information can be used by Sakai 3 in a site-like way *without*
<br>requiring explicit site creation: view the enrollment history of Latin
<br>1a, look at course catalog data for Byzantine Greek, send messages to
<br>the instructors for Latin 1a 03 2009, etc. Sakai 3 capabilities (whether
<br>"content authoring", "pedagogical activity", or "group management")
<br>could be smoothly layered on non-Sakai-hosted functionality only as needed.
<br><br>Best,
<br>Ray
<br><br>On 11/23/09 2:09 AM, Matthew Buckett wrote:
<div class='shrinkable-quote'><br>> 2009/11/22 John Norman <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26483128&i=0" target="_top" rel="nofollow">john@...</a>>:
<br>>> The Oxford document makes an interesting read as an example of a 'group' structure that
<br>>> doesn't really need a site.
<br>>
<br>> Just for a bit of background. The reason used a site is that the tools
<br>> (Site Info) for managing this group could be reused.
<br>>
<br>> In a short summary any user who has a permission in an admin site gets
<br>> it in all sites that are managed by that admin site. This allows for
<br>> people to admin large numbers of sites (by the fact they have site.upd
<br>> in the admin site) without being members of them. It also allows for
<br>> external auditors to get read only access (content.read, site.visit,
<br>> etc) to sites.
<br>>
</div><br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26483128&i=1" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26483128&i=2" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26483018Re: [Building Sakai] P.S. --> What's new in Mneme 1.2M4 thru 1.2M62009-11-23T09:59:51Z2009-11-23T09:59:51ZVivie Sinou-2<br>>>We're running Mneme 1.2M3 in production and I would like to
<br>>>know whether I should update to Mneme 1.2M6. I can't find a
<br>>>changelog anywhere. Does anybody have any information about
<br>>>what is new in M4 - M6?
<br>>>
<br>>>Thanks,
<br>>>Maarten van Hoof, Edia
<br><br>Maarten - To answer your question briefly...
<br><br>Our work between Mneme 1.2m4 and m6 has to do with code changes in
<br>"archives" (Etudes code) and "site import" to fix cross-references issues --
<br>URL's that point to previous term Resources.
<br><br>With this x-ref fixing code, we do 'deep harvesting' of resources that are
<br>used in Mneme (upon running "import from site" and "archiving") and we
<br>translate the Resources tool URL's that are hard-coded in Mneme content by
<br>instructors to the new site id.
<br><br>I hope that was explained clearly enough. :) Let me know.
<br><br>Best,
<br>Vivie
<br><br>--
<br>Vivie Sinou
<br>Executive Director, Etudes, Inc.
<br><a href="http://etudes.org/" target="_top" rel="nofollow">http://etudes.org/</a><br><br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26483018&i=0" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26483018&i=1" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26482785Re: [Building Sakai] What's new in Mneme 1.2M62009-11-23T09:45:30Z2009-11-23T09:45:30ZVivie Sinou-2Maarten:
<br><br>Please wait for our next milestone release, Mneme 1.2m7. It's a pretty
<br>significant release, with a number of workflow enhancements and new features
<br>in the Assessments module.
<br><br>We'll be deploying it onto our Etudes production within the next few days.
<br>I'll have release notes for our users and will be happy to share them with
<br>you, including an archives link to a webcast demo that I am giving across
<br>our colleges here in California.
<br><br>A public release of Mneme 1.2 will be out later next spring.
<br><br>Best,
<br>Vivie
<br><br>--
<br>Vivie Sinou
<br>Executive Director, Etudes, Inc.
<br><a href="http://etudes.org/" target="_top" rel="nofollow">http://etudes.org/</a><br><br><br><br>
<br><div class='shrinkable-quote'><br>>-----Original Message-----
<br>>From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26482785&i=0" target="_top" rel="nofollow">sakai-dev-bounces@...</a>
<br>>[mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26482785&i=1" target="_top" rel="nofollow">sakai-dev-bounces@...</a>] On Behalf
<br>>Of Maarten van Hoof
<br>>Sent: Monday, November 23, 2009 8:52 AM
<br>>To: Sakai Dev
<br>>Subject: [Building Sakai] What's new in Mneme 1.2M6
<br>>
<br>>Hi,
<br>>
<br>>We're running Mneme 1.2M3 in production and I would like to
<br>>know whether I should update to Mneme 1.2M6. I can't find a
<br>>changelog anywhere. Does anybody have any information about
<br>>what is new in M4 - M6?
<br>>
<br>>Thanks,
<br>>Maarten van Hoof, Edia
<br>>
<br>>
</div><br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26482785&i=2" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26482785&i=3" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26486595[Building Sakai] Access view and sferyx and basedir params for editor integration2009-11-23T09:43:48Z2009-11-23T09:43:48ZStephen MarquardHi,
<br><br>Does anyone familiar with the Sferyx and FCK support in Sakai know whether the sbasedir and basedir parameters are still used in CollectionAccessFormatter, i.e.
<br><br><a href="http://nightly2.sakaiproject.org:8087/access/content/public/" target="_top" rel="nofollow">http://nightly2.sakaiproject.org:8087/access/content/public/</a><br><br>vs
<br><br><a href="http://nightly2.sakaiproject.org:8087/access/content/public/?sbasedir=something" target="_top" rel="nofollow">http://nightly2.sakaiproject.org:8087/access/content/public/?sbasedir=something</a><br><a href="http://nightly2.sakaiproject.org:8087/access/content/public/?basedir=something" target="_top" rel="nofollow">http://nightly2.sakaiproject.org:8087/access/content/public/?basedir=something</a><br><br>The code in CollectionAccessFormatter.java (in the kernel) is somewhat convoluted, and removing support for basedir and sbasedir would simplify it considerably if they're no longer used.
<br><br>Regards
<br>Stephen
<br><br><br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26486595&i=0" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26486595&i=1" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26481847[Building Sakai] What's new in Mneme 1.2M62009-11-23T08:52:20Z2009-11-23T08:52:20ZMaarten van Hoof-2Hi,<br><br>We're running Mneme 1.2M3 in production and I would like to know whether I should update to Mneme 1.2M6. I can't find a changelog anywhere. Does anybody have any information about what is new in M4 - M6?<br>
<br>Thanks,<br>Maarten van Hoof, Edia<br>
<br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26481847&i=0" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26481847&i=1" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26481067Re: [DG: User Experience] Exploited ignorance2009-11-23T08:13:26Z2009-11-23T08:13:26ZChris-704Just saw, just before hitting the send button, that Oszkar posted
<br>something on the list so there could be some overlapping in my notes:
<br><br>Last week I did some work on the prototype templates [1]. I completely
<br>reorganised the pages so it is possible that some links are broken on
<br>[2].
<br><br>> The bulk of the activity right now seems to be focussed on the
<br>> introduction of "Prototype templates," though many of them still seem
<br>> to just be screenshots so far, like patterns without descriptive
<br>> information.
<br><br>Currently only the discussion & messaging section should have
<br>screenshots. The main reason for this is that Oszkar was still making
<br>some
<br>design modifications to the "compact view templates" from Adrian [3].
<br>So I
<br>didn't want to do the conversion yet. All the other prototypes (16 out
<br>of 18)
<br>should have appropriate HTML and CSS. I can agree that some look like
<br>screenshots but they are iframes.
<br><br>> Where are the prototype templates coming from? By a reasoned
<br>> deconstruction of what sits on 3akai.sakaiproject.org?
<br><br><br>I do get most of my HTML and CSS from <a href="http://3akai.sakaiproject.org" target="_top" rel="nofollow">http://3akai.sakaiproject.org</a>.
<br>This process also gives me a view of which CSS needs to be
<br>re-factored in the near future.
<br><br><br>As a last note I would also like to mention some things that are
<br>currently
<br>spinning in my head:
<br><br>1) To make the prototype library more useful for other I was thinking of
<br>providing the user with a zip file that would contain the latest
<br>prototypes with their appropriate CSS/HTML and images.
<br><br>2) Hosting: currently we upload the prototype pages & files to [4].
<br>The main problem with this solution is that as soon as we redeploy
<br>Sakai3 on that server, I'll need to re-upload all the files. Maybe
<br>we could use one of servers hosted by the foundation for this purpose?
<br><br><br>[1] <a href="http://confluence.sakaiproject.org/display/UX/Prototype+Templates" target="_top" rel="nofollow">http://confluence.sakaiproject.org/display/UX/Prototype+Templates</a><br>[2] <a href="http://confluence.sakaiproject.org/display/UX/Patterns+and+templates" target="_top" rel="nofollow">http://confluence.sakaiproject.org/display/UX/Patterns+and+templates</a><br>[3] <a href="http://github.com/oszkarnagy/3akai-ux/commit/87f3f80f089140a2e2f23012de2f04a275e0ebd7" target="_top" rel="nofollow">http://github.com/oszkarnagy/3akai-ux/commit/87f3f80f089140a2e2f23012de2f04a275e0ebd7</a><br>[4] <a href="http://3akai.sakaiproject.org/dev/_patterns/" target="_top" rel="nofollow">http://3akai.sakaiproject.org/dev/_patterns/</a><br><br>On 23 Nov 2009, at 15:49, Oszkar Nagy wrote:
<br><div class='shrinkable-quote'><br>> Hi Clay,
<br>>
<br>> Probably the best person to answer the questions about the Pattern
<br>> Library is Sam, but nevertheless I'll go ahead and try to explain a
<br>> bit,
<br>> to the best of my knowledge and interpretation, based on Sam's brief.
<br>>
<br>>
<br>> Categories:
<br>> I am still not sure about what Sam wants the final categories to be,
<br>> but
<br>> there are 2 candidates as far as I know:
<br>>
<br>> 1
<br>> Primary user groups (as it is now, Students, Instructors,
<br>> Educators/Researchers ) which is based on a distinction that there are
<br>> basic UI elements (Buttons, Layouts, Tabs etc...) which will build
<br>> up a
<br>> higher level pattern, aimed to solve a certain UI problem to a certain
<br>> group (Sites widget for example)
<br>>
<br>> 2
<br>> Another approach which he sent us was a more general categorization,
<br>> which structure can be found here:
<br>> <a href="http://confluence.sakaiproject.org/display/UX/Prototype+Templates" target="_top" rel="nofollow">http://confluence.sakaiproject.org/display/UX/Prototype+Templates</a>
<br>> which
<br>> is based upon his design master file categories.
<br>>
<br>> Not sure which will be the final one though.
<br>>
<br>>
<br>>
<br>> Patterns:
<br>> A source for a pattern as far as I understand should be coming from
<br>> Sam
<br>> and Flow Interactive. Not sure though whether the the data would come
<br>> from a current UI taken from the latest UX version, or would be
<br>> re-thinked and we would perfect some of the examples which are there.
<br>> Also you are right that, we only have worked a little bit on this
<br>> from a
<br>> technical point of view (ripping out some standalone HTML and CSS) and
<br>> creating a start to illustrate Sam's vision, but no real content is
<br>> placed in it so far. My personal view is that we should only have
<br>> discussed and locked down designs in the pattern library, which
<br>> could be
<br>> used as a base for technical CSS cleanup and organization as well.
<br>>
<br>>
<br>>
<br>> HTML - CSS examples (prototypes):
<br>> These would serve as a basis for rapid prototyping in HTML. Sam thinks
<br>> we could do faster prototyping straight in HTML. The idea would be to
<br>> take lower level elements and build higher level constructs by cutting
<br>> and pasting together HTML and CSS from the patterns: Grab a layout,
<br>> grab
<br>> tabs, grab buttons, etc.. to create a page design and almost a
<br>> prototype
<br>> as well at the same time. As far as I know the prototype would reflect
<br>> faithfully a certain pattern, and wouldn't drift from the design. One
<br>> question about this is how we share prototypes for wider discussion,
<br>> and
<br>> stakeholder feedback as implied in the proposed design cycle. Another
<br>> one would be the state of current UI elements, ie do we take those as
<br>> base level or do we need to re-visit them? Not sure how this would
<br>> work
<br>> in practice, especially with a lot of dependency CSS.
<br>>
<br>>
<br>>
<br>> Sitemap:
<br>> This ultimately would be an interactive site-map highlighting the
<br>> pages
<br>> within Sakai which uses a certain pattern. We have code for this, but
<br>> still no final hosting for it (also links will need updating from the
<br>> pattern pages).
<br>>
<br>>
<br>>
<br>> I am pretty sure there are opportunities for other people to be
<br>> involved, but again Sam would probably be a better person to ask as he
<br>> has a clearer view of the process I am pretty sure.
<br>>
<br>> Hope this helps a bit,
<br>> Oszkar
<br>>
<br>>
<br>>
<br>>
<br>>
<br>> On 23/11/2009 13:56, Clay Fenlason wrote:
<br>>> I've been wanting to highlight the component/pattern library starting
<br>>> to emerge in the UX wiki space [1] for Sakai 3, but as I was
<br>>> reviewing
<br>>> it again this morning I was reminded that it's not clear to me what's
<br>>> happening or how it will be used. Happy coincidence! I can now ask my
<br>>> embarrassed questions (to Oszkar and Christian) behind a mask of
<br>>> feigned naivety for the benefit of others. Selfishness that serves.
<br>>>
<br>>> There is a FAQ [2], but it seems to just be a placeholder for the
<br>>> moment. This might be something I can help with.
<br>>>
<br>>> The first section of what seems to be the introductory page [1] is
<br>>> broken down by user, and that looks like a good start. Within those
<br>>> regions it looks like components are identified particular to them,
<br>>> from three different angles: a) pattern, b) prototype, and c)
<br>>> sitemap.
<br>>> The latter (c) looks like it will eventually be a way to locate
<br>>> these
<br>>> components within the application hierarchy, but it looks like it's
<br>>> set up in such a way that I'd have to discover them serendipitously
<br>>> by
<br>>> clicking around - but it may just be too soon to assess what the
<br>>> sitemap will do. The pattern (a) looks like a wireframe with some
<br>>> description of how it's used and the problem it's trying to solve.
<br>>> The
<br>>> prototype (b) includes actual HTML and CSS for reuse, which seems
<br>>> very
<br>>> helpful to UI developers.
<br>>>
<br>>> Then beneath the breakdown by users there are "basic components,"
<br>>> presumably generic in how they are not tailored to solving problems
<br>>> for particular personas.
<br>>>
<br>>> The bulk of the activity right now seems to be focussed on the
<br>>> introduction of "Prototype templates," though many of them still seem
<br>>> to just be screenshots so far, like patterns without descriptive
<br>>> information. I'm assuming they'll progressively have their HTML and
<br>>> CSS filled in as well - have I got that right? Also, the focus on the
<br>>> prototypes seems to suggest that the work is mostly technical for the
<br>>> moment, or that's the overall impression - components are seeing more
<br>>> attention than the design justification of their patterns.
<br>>>
<br>>> Where are the prototype templates coming from? By a reasoned
<br>>> deconstruction of what sits on 3akai.sakaiproject.org?
<br>>>
<br>>> What is the connection between a pattern and a prototype? Is a
<br>>> prototype a faithful implementation of a pattern, in which case why
<br>>> separate them - does that risk having the implementation drift from
<br>>> the design? Or is it rather a distinction of process, whereby the
<br>>> pattern needs to be reviewed and tested up until a point where it
<br>>> makes sense to do the work to turn it into a prototype?
<br>>>
<br>>> Is there an opportunity here for others to get involved, say, by
<br>>> fleshing out the 'pattern' side of the library?
<br>>>
<br>>> ~Clay
<br>>>
<br>>> [1] <a href="http://confluence.sakaiproject.org//x/bQUAB" target="_top" rel="nofollow">http://confluence.sakaiproject.org//x/bQUAB</a><br>>> [2] <a href="http://confluence.sakaiproject.org//x/owYAB" target="_top" rel="nofollow">http://confluence.sakaiproject.org//x/owYAB</a><br>>> _______________________________________________
<br>>> sakai-ux mailing list
<br>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26481067&i=0" target="_top" rel="nofollow">sakai-ux@...</a>
<br>>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br>>>
<br>>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26481067&i=1" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a>
<br>>> with a subject of "unsubscribe"
<br>> _______________________________________________
<br>> sakai-ux mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26481067&i=2" target="_top" rel="nofollow">sakai-ux@...</a>
<br>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br>>
<br>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26481067&i=3" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a>
<br>> with a subject of "unsubscribe"
</div><br>_______________________________________________
<br>sakai-ux mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26481067&i=4" target="_top" rel="nofollow">sakai-ux@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26481067&i=5" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---User-Experience-f30853.html" embed="fixTarget[30853]" target="_top" >Sakai - User Experience</a></p>tag:old.nabble.com,2006:post-26480593Re: [DG: User Experience] Exploited ignorance2009-11-23T07:49:41Z2009-11-23T07:49:41ZOszkar NagyHi Clay,
<br><br>Probably the best person to answer the questions about the Pattern
<br>Library is Sam, but nevertheless I'll go ahead and try to explain a bit,
<br>to the best of my knowledge and interpretation, based on Sam's brief.
<br><br><br>Categories:
<br>I am still not sure about what Sam wants the final categories to be, but
<br>there are 2 candidates as far as I know:
<br><br>1
<br>Primary user groups (as it is now, Students, Instructors,
<br>Educators/Researchers ) which is based on a distinction that there are
<br>basic UI elements (Buttons, Layouts, Tabs etc...) which will build up a
<br>higher level pattern, aimed to solve a certain UI problem to a certain
<br>group (Sites widget for example)
<br><br>2
<br>Another approach which he sent us was a more general categorization,
<br>which structure can be found here:
<br><a href="http://confluence.sakaiproject.org/display/UX/Prototype+Templates" target="_top" rel="nofollow">http://confluence.sakaiproject.org/display/UX/Prototype+Templates</a> which
<br>is based upon his design master file categories.
<br><br>Not sure which will be the final one though.
<br><br><br><br>Patterns:
<br>A source for a pattern as far as I understand should be coming from Sam
<br>and Flow Interactive. Not sure though whether the the data would come
<br>from a current UI taken from the latest UX version, or would be
<br>re-thinked and we would perfect some of the examples which are there.
<br>Also you are right that, we only have worked a little bit on this from a
<br>technical point of view (ripping out some standalone HTML and CSS) and
<br>creating a start to illustrate Sam's vision, but no real content is
<br>placed in it so far. My personal view is that we should only have
<br>discussed and locked down designs in the pattern library, which could be
<br>used as a base for technical CSS cleanup and organization as well.
<br><br><br><br>HTML - CSS examples (prototypes):
<br>These would serve as a basis for rapid prototyping in HTML. Sam thinks
<br>we could do faster prototyping straight in HTML. The idea would be to
<br>take lower level elements and build higher level constructs by cutting
<br>and pasting together HTML and CSS from the patterns: Grab a layout, grab
<br>tabs, grab buttons, etc.. to create a page design and almost a prototype
<br>as well at the same time. As far as I know the prototype would reflect
<br>faithfully a certain pattern, and wouldn't drift from the design. One
<br>question about this is how we share prototypes for wider discussion, and
<br>stakeholder feedback as implied in the proposed design cycle. Another
<br>one would be the state of current UI elements, ie do we take those as
<br>base level or do we need to re-visit them? Not sure how this would work
<br>in practice, especially with a lot of dependency CSS.
<br><br><br><br>Sitemap:
<br>This ultimately would be an interactive site-map highlighting the pages
<br>within Sakai which uses a certain pattern. We have code for this, but
<br>still no final hosting for it (also links will need updating from the
<br>pattern pages).
<br><br><br><br>I am pretty sure there are opportunities for other people to be
<br>involved, but again Sam would probably be a better person to ask as he
<br>has a clearer view of the process I am pretty sure.
<br><br>Hope this helps a bit,
<br>Oszkar
<br><br><br><br><br><br>On 23/11/2009 13:56, Clay Fenlason wrote:
<div class='shrinkable-quote'><br>> I've been wanting to highlight the component/pattern library starting
<br>> to emerge in the UX wiki space [1] for Sakai 3, but as I was reviewing
<br>> it again this morning I was reminded that it's not clear to me what's
<br>> happening or how it will be used. Happy coincidence! I can now ask my
<br>> embarrassed questions (to Oszkar and Christian) behind a mask of
<br>> feigned naivety for the benefit of others. Selfishness that serves.
<br>>
<br>> There is a FAQ [2], but it seems to just be a placeholder for the
<br>> moment. This might be something I can help with.
<br>>
<br>> The first section of what seems to be the introductory page [1] is
<br>> broken down by user, and that looks like a good start. Within those
<br>> regions it looks like components are identified particular to them,
<br>> from three different angles: a) pattern, b) prototype, and c) sitemap.
<br>> The latter (c) looks like it will eventually be a way to locate these
<br>> components within the application hierarchy, but it looks like it's
<br>> set up in such a way that I'd have to discover them serendipitously by
<br>> clicking around - but it may just be too soon to assess what the
<br>> sitemap will do. The pattern (a) looks like a wireframe with some
<br>> description of how it's used and the problem it's trying to solve. The
<br>> prototype (b) includes actual HTML and CSS for reuse, which seems very
<br>> helpful to UI developers.
<br>>
<br>> Then beneath the breakdown by users there are "basic components,"
<br>> presumably generic in how they are not tailored to solving problems
<br>> for particular personas.
<br>>
<br>> The bulk of the activity right now seems to be focussed on the
<br>> introduction of "Prototype templates," though many of them still seem
<br>> to just be screenshots so far, like patterns without descriptive
<br>> information. I'm assuming they'll progressively have their HTML and
<br>> CSS filled in as well - have I got that right? Also, the focus on the
<br>> prototypes seems to suggest that the work is mostly technical for the
<br>> moment, or that's the overall impression - components are seeing more
<br>> attention than the design justification of their patterns.
<br>>
<br>> Where are the prototype templates coming from? By a reasoned
<br>> deconstruction of what sits on 3akai.sakaiproject.org?
<br>>
<br>> What is the connection between a pattern and a prototype? Is a
<br>> prototype a faithful implementation of a pattern, in which case why
<br>> separate them - does that risk having the implementation drift from
<br>> the design? Or is it rather a distinction of process, whereby the
<br>> pattern needs to be reviewed and tested up until a point where it
<br>> makes sense to do the work to turn it into a prototype?
<br>>
<br>> Is there an opportunity here for others to get involved, say, by
<br>> fleshing out the 'pattern' side of the library?
<br>>
<br>> ~Clay
<br>>
<br>> [1] <a href="http://confluence.sakaiproject.org//x/bQUAB" target="_top" rel="nofollow">http://confluence.sakaiproject.org//x/bQUAB</a><br>> [2] <a href="http://confluence.sakaiproject.org//x/owYAB" target="_top" rel="nofollow">http://confluence.sakaiproject.org//x/owYAB</a><br>> _______________________________________________
<br>> sakai-ux mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26480593&i=0" target="_top" rel="nofollow">sakai-ux@...</a>
<br>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br>>
<br>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26480593&i=1" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"
</div>_______________________________________________
<br>sakai-ux mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26480593&i=2" target="_top" rel="nofollow">sakai-ux@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26480593&i=3" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---User-Experience-f30853.html" embed="fixTarget[30853]" target="_top" >Sakai - User Experience</a></p>tag:old.nabble.com,2006:post-26479810Re: [Building Sakai] Export calendar problem.2009-11-23T07:12:00Z2009-11-23T07:12:00ZBeth KirschnerThe export will only work on individual calendars (not merged
<br>calendars in your "My Workspace"), so you'll have to export your
<br>teacher's class calendar separately.
<br><br>- Beth
<br><br>On Nov 20, 2009, at 2:33 AM, Sam Chow wrote:
<br><div class='shrinkable-quote'><br>> Dear Beth,
<br>>
<br>> After i modifiied this java method, its work fine. Many Thanks.
<br>>
<br>> But i found that, the exported ical didnt include the schedule of
<br>> the teacher's class. Any idea, if i want the exported icalendar
<br>> include all of the teacher schedlue? Many Thanks.
<br>>
<br>>
<br>> Best Regards,
<br>> Sam Chow
<br>>
<br>>
<br>> ----- Original Message ----- From: "Beth Kirschner" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26479810&i=0" target="_top" rel="nofollow">bkirschn@...</a>
<br>> >
<br>> To: "Sam Chow" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26479810&i=1" target="_top" rel="nofollow">samchow@...</a>>
<br>> Cc: <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26479810&i=2" target="_top" rel="nofollow">sakai-dev@...</a>>
<br>> Sent: Thursday, November 19, 2009 9:47 PM
<br>> Subject: Re: [Building Sakai] Export calendar problem.
<br>>
<br>>
<br>>> Hi Sam,
<br>>>
<br>>> If you'd like to have the DTEND field included, you should write
<br>>> up your request in JIRA (<a href="http://jira.sakaiproject.org/secure/Dashboard.jspa" target="_top" rel="nofollow">http://jira.sakaiproject.org/secure/Dashboard.jspa</a>
<br>>> ) and if possible, submit a patch to go along with it. The code
<br>>> that generates the iCal events is in the
<br>>> org.sakaiproject.calendar.impl.BaseCalendarService.generateIcal()
<br>>> method.
<br>>>
<br>>> - Beth
<br>>>
<br>>> On Nov 19, 2009, at 3:05 AM, Sam Chow wrote:
<br>>>
<br>>>> Dear Sir,
<br>>>>
<br>>>> I am using Sakai 2.6 and i have enabled the funciton of export a
<br>>>> schedule in to a iCal file. I have set up a phpicalendar to link
<br>>>> with the exported sakai calendar, but i found that the end time
<br>>>> didnt show. After i check the iCal file, it have dtstart but dont
<br>>>> have dtend. But so funny that google can get the end time, i
<br>>>> guess it is using the Duration to get it.
<br>>>>
<br>>>> Can i add the DTEND in the exported iCal file?
<br>>>>
<br>>>> Many Thanks.
<br>>>>
<br>>>> Best Regards,
<br>>>> Sam Chow
<br>>>> _______________________________________________
<br>>>> sakai-dev mailing list
<br>>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26479810&i=3" target="_top" rel="nofollow">sakai-dev@...</a>
<br>>>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>>>>
<br>>>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26479810&i=4" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a>
<br>>>> with a subject of "unsubscribe"
<br>>>
<br>>
<br>>
<br>>
<br>>
</div><br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26479810&i=5" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26479810&i=6" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26478465[DG: User Experience] Exploited ignorance2009-11-23T05:56:07Z2009-11-23T05:56:07ZClay Fenlason-3I've been wanting to highlight the component/pattern library starting
<br>to emerge in the UX wiki space [1] for Sakai 3, but as I was reviewing
<br>it again this morning I was reminded that it's not clear to me what's
<br>happening or how it will be used. Happy coincidence! I can now ask my
<br>embarrassed questions (to Oszkar and Christian) behind a mask of
<br>feigned naivety for the benefit of others. Selfishness that serves.
<br><br>There is a FAQ [2], but it seems to just be a placeholder for the
<br>moment. This might be something I can help with.
<br><br>The first section of what seems to be the introductory page [1] is
<br>broken down by user, and that looks like a good start. Within those
<br>regions it looks like components are identified particular to them,
<br>from three different angles: a) pattern, b) prototype, and c) sitemap.
<br> The latter (c) looks like it will eventually be a way to locate these
<br>components within the application hierarchy, but it looks like it's
<br>set up in such a way that I'd have to discover them serendipitously by
<br>clicking around - but it may just be too soon to assess what the
<br>sitemap will do. The pattern (a) looks like a wireframe with some
<br>description of how it's used and the problem it's trying to solve. The
<br>prototype (b) includes actual HTML and CSS for reuse, which seems very
<br>helpful to UI developers.
<br><br>Then beneath the breakdown by users there are "basic components,"
<br>presumably generic in how they are not tailored to solving problems
<br>for particular personas.
<br><br>The bulk of the activity right now seems to be focussed on the
<br>introduction of "Prototype templates," though many of them still seem
<br>to just be screenshots so far, like patterns without descriptive
<br>information. I'm assuming they'll progressively have their HTML and
<br>CSS filled in as well - have I got that right? Also, the focus on the
<br>prototypes seems to suggest that the work is mostly technical for the
<br>moment, or that's the overall impression - components are seeing more
<br>attention than the design justification of their patterns.
<br><br>Where are the prototype templates coming from? By a reasoned
<br>deconstruction of what sits on 3akai.sakaiproject.org?
<br><br>What is the connection between a pattern and a prototype? Is a
<br>prototype a faithful implementation of a pattern, in which case why
<br>separate them - does that risk having the implementation drift from
<br>the design? Or is it rather a distinction of process, whereby the
<br>pattern needs to be reviewed and tested up until a point where it
<br>makes sense to do the work to turn it into a prototype?
<br><br>Is there an opportunity here for others to get involved, say, by
<br>fleshing out the 'pattern' side of the library?
<br><br>~Clay
<br><br>[1] <a href="http://confluence.sakaiproject.org//x/bQUAB" target="_top" rel="nofollow">http://confluence.sakaiproject.org//x/bQUAB</a><br>[2] <a href="http://confluence.sakaiproject.org//x/owYAB" target="_top" rel="nofollow">http://confluence.sakaiproject.org//x/owYAB</a><br>_______________________________________________
<br>sakai-ux mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26478465&i=0" target="_top" rel="nofollow">sakai-ux@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26478465&i=1" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---User-Experience-f30853.html" embed="fixTarget[30853]" target="_top" >Sakai - User Experience</a></p>tag:old.nabble.com,2006:post-26476686Re: [Building Sakai] Transfer of selective course site from one sakai server to another sakai server2009-11-23T03:51:49Z2009-11-23T03:51:49ZSteve Swinsburg-3Hi,
<br><br>The location of the archives is set in sakai.properties:
<br># root of archive file system area - used to write archive files and to read them
<br># when clustering app servers, this should be a shared network location
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476686&i=0" target="_top" rel="nofollow">storagePath@...</a> = ${sakai.home}/archive/
<br><br>ie next to your sakai.properties under the archive/ directory.
<br><br>Once you archive a site you will have a directory for that site there. You'll need to transfer that directory to your new server and then import.
<br><br>However, certain data does not carry across so depending on what you need you may have mixed results.
<br><br>cheers,
<br>Steve
<br><br><br>On 23/11/2009, at 9:36 PM, GIMMI AGARWAL wrote:
<br><div class='shrinkable-quote'><div class='shrinkable-quote'><br>> Hi Friends,
<br>>
<br>> I would like to transfer some selective course sites from one sakai to the another sakai so that the entire data of that particular course will shift from one sakai to another sakai.
<br>> I am using RHEL as a operating system and apache tomcat as a web server.
<br>>
<br>> I have export the site using site archive but doesn't able to get the exported file therefore suggest me the location of exported file where these files stored.
<br>>
<br>> Please explain me in details.
<br>>
<br>>
<br>> Regards
<br>>
<br>> Gimmi Agarwal
<br>> _______________________________________________
<br>> sakai-dev mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476686&i=1" target="_top" rel="nofollow">sakai-dev@...</a>
<br>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>>
<br>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476686&i=2" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
</div></div><br /> <br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476686&i=3" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476686&i=4" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (5K) <a href="http://old.nabble.com/attachment/26476686/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26475695[Building Sakai] Transfer of selective course site from one sakai server to another sakai server2009-11-23T02:36:49Z2009-11-23T02:36:49ZGIMMI AGARWAL<div dir="ltr">Hi Friends,<br><br>I would like to transfer some selective course sites from one sakai to
the another sakai so that the entire data of that particular course
will shift from one sakai to another sakai.<br>I am using RHEL as a operating system and apache tomcat as a web server.<br><br>I have export the site using site archive but doesn't able to get the exported file therefore suggest me the location of exported file where these files stored.<br>
<br>Please explain me in details.<br><br><br>Regards<br><br>Gimmi Agarwal<br></div>
<br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475695&i=0" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475695&i=1" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26475389Re: [Building Sakai] [sakai-kernel] Re: Automating the site creation process AND Sakai 3 Groups2009-11-23T02:13:25Z2009-11-23T02:13:25ZMatthew Buckett2009/11/23 Matthew Buckett <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475389&i=0" target="_top" rel="nofollow">matthew.buckett@...</a>>:
<br>> 2009/11/22 John Norman <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475389&i=1" target="_top" rel="nofollow">john@...</a>>:
<br>>> The Oxford document makes an interesting read as an example of a 'group' structure that
<br>>> doesn't really need a site.
<br>>
<br>> Just for a bit of background. The reason used a site is that the tools
<br>> (Site Info) for managing this group could be reused.
<br><br>The kernel part of this work is in:
<br><br><a href="http://jira.sakaiproject.org/browse/KNL-300" target="_top" rel="nofollow">http://jira.sakaiproject.org/browse/KNL-300</a><br><br>the changes to site-manage are still in our local repo but should be
<br>bundled up in a patch shortly.
<br><br>--
<br> Matthew Buckett
<br> VLE Developer, LTG, Oxford University Computing Services
<br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475389&i=2" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475389&i=3" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26475354Re: [Building Sakai] [sakai-kernel] Re: Automating the site creation process AND Sakai 3 Groups2009-11-23T02:09:45Z2009-11-23T02:09:45ZMatthew Buckett2009/11/22 John Norman <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475354&i=0" target="_top" rel="nofollow">john@...</a>>:
<br>> The Oxford document makes an interesting read as an example of a 'group' structure that
<br>> doesn't really need a site.
<br><br>Just for a bit of background. The reason used a site is that the tools
<br>(Site Info) for managing this group could be reused.
<br><br>In a short summary any user who has a permission in an admin site gets
<br>it in all sites that are managed by that admin site. This allows for
<br>people to admin large numbers of sites (by the fact they have site.upd
<br>in the admin site) without being members of them. It also allows for
<br>external auditors to get read only access (content.read, site.visit,
<br>etc) to sites.
<br><br>--
<br> Matthew Buckett
<br> VLE Developer, LTG, Oxford University Computing Services
<br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475354&i=1" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475354&i=2" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26474161Re: [Building Sakai] Deploy sakai + cas to listen all ip addresses2009-11-23T00:23:18Z2009-11-23T00:23:18ZSteve Swinsburg-3You'll need to do this as two separate tasks. Get Sakai up and running and get your CAS server up and running. Then attempt to integrate.
<br><br>Your config for joining Sakai to CAS looks ok, I've got some docs here:
<br><a href="http://confluence.sakaiproject.org/display/~steve.swinsburg/CASifying+Sakai" target="_top" rel="nofollow">http://confluence.sakaiproject.org/display/~steve.swinsburg/CASifying+Sakai</a><br><br>cheers,
<br>Steve
<br><br><br>On 23/11/2009, at 5:25 PM, Thach Le wrote:
<br><div class='shrinkable-quote'><div class='shrinkable-quote'><br>> Dear,
<br>>
<br>> I would like to deploy the sakai which supports many address.
<br>> Example: My host "rai-server" has an ip address 192.168.1.1.
<br>>
<br>> I have deployed the sakai 2.6.1 and CAS (<a href="http://rai-server:7433/cas" target="_top" rel="nofollow">http://rai-server:7433/cas</a>)
<br>> with link <a href="http://rai-server:8433/" target="_top" rel="nofollow">http://rai-server:8433/</a>. It's OK. I have not configured
<br>> mod_jk and apache yet.
<br>>
<br>> I found there are many fixed values in CAS configuration.
<br>> Now, I want to configure the sakai + CAS in order to the user can
<br>> access the sakai portal via <a href="http://192.1.168.1.1:8433" target="_top" rel="nofollow">http://192.1.168.1.1:8433</a> or
<br>> <a href="http://rai-server:8433" target="_top" rel="nofollow">http://rai-server:8433</a>.
<br>>
<br>> How can I do?
<br>>
<br>> Thach Le
<br>> <Sakai261_CAS.txt>_______________________________________________
<br>> sakai-dev mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26474161&i=0" target="_top" rel="nofollow">sakai-dev@...</a>
<br>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>>
<br>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26474161&i=1" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
</div></div><br /> <br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26474161&i=2" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26474161&i=3" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (5K) <a href="http://old.nabble.com/attachment/26474161/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26473547Re: [Building Sakai] [WG: Sakai QA] Samigo 2.7 Freeze2009-11-22T23:07:50Z2009-11-22T23:07:50ZLydia LiAll,
<br><br> James has already contacted us about the patch (SAK-17377). We will merge it in 2.7.
<br><br>thanks,
<br>Lydia
<br><br><br>----- "Anthony Whyte" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=0" target="_top" rel="nofollow">arwhyte@...</a>> wrote:
<br><br>| One exception to the Samigo team's decision to freeze new features for
<br>| 2.7: Â Samigo, edu-services and the gradebook teams need to decide if
<br>| GB2-related SAK merges are acceptable for inclusion in 2.7.  I
<br>| recommend the three teams collaborate in order to frame a joint
<br>| recommendation. Â See summary of concerns below.
<br>|
<br>|
<br>| Cheers,
<br>|
<br>|
<br>| Anth
<br>|
<br>|
<br>|
<br>|
<br>|
<br>|
<br>| Begin forwarded message:
<br>|
<br>|
<br>|
<br>|
<br>| From:Â James Renfro < <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=1" target="_top" rel="nofollow">jlrenfro@...</a> >
<br>| Date:Â November 21, 2009 7:43:32 PM GMT-05:00
<br>| To:Â David Horwitz < <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=2" target="_top" rel="nofollow">david.horwitz@...</a> >
<br>| Cc:Â " <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=3" target="_top" rel="nofollow">management@...</a> " <
<br>| <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=4" target="_top" rel="nofollow">management@...</a> >
<br>| Subject:Â Re: [Management] GB2 Concernes
<br>|
<br>| Hi David,
<br>| Not sure if you're looking for responses directly from UCDavis at this
<br>| point, but thought I'd answer what I could here in case that's
<br>| helpful.
<br>|
<br>| See below for inline responses.Â
<br>|
<br>| Thanks,
<br>| James.
<br>|
<br>|
<br>|
<br>| On Fri, Nov 20, 2009 at 5:29 AM, David Horwitz <
<br>| <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=5" target="_top" rel="nofollow">david.horwitz@...</a> > Â wrote:
<br>|
<br>|
<br>| Hi All,
<br>|
<br>| After a brief poke around in GB2 I have a number of concerns that
<br>| seems
<br>| to have slipped through the PC process:
<br>|
<br>| 1) There is no build for the current trunk (This is blocker but should
<br>| be fairly easy to fix)
<br>|
<br>|
<br>| Just to clarify the exact situation here. Building against current
<br>| trunk / 2.7 requires three patches at this moment that are provided as
<br>| part of the module itself.Â
<br>| Â (1) against edu-services to bring the original gradebook data model
<br>| up-to-date
<br>| Â (2) against the gb2 code itself, which is checked in as 2.5.5Â
<br>| Â (3) against the sam module
<br>|
<br>| The (1) patch will be eliminated if and when the Gradebook committers
<br>| approve SAK-17428, and the (2) patch will be eliminated in the next
<br>| couple of days when I commit that change. (3) will be eliminated when
<br>| the Samigo committers approve SAK-17377. Â
<br>|
<br>| Of course, the question then becomes exactly what you want tools to do
<br>| -- should gb2 trunk build against fnd trunk, or the 2.7.x branch? I
<br>| assume trunk. Especially at this moment, with 2.5.x, 2.6.x, 2.7.x, and
<br>| trunk all currently in existence and supported, it is not really
<br>| feasible, afaics, for a tool to create a branch for each, in addition
<br>| to the tool's own versioning and development. It's a merging
<br>| nightmare. Our preference would be to maintain GB2 trunk against FND
<br>| trunk or 2.7.x and provide binary artifacts for distribution via the
<br>| Sakai maven repositories. I believe we can accomplish this currently
<br>| by maintaining sakai comptability patches and applying these ourselves
<br>| on each tag release, compiling a release artifact and uploading it to
<br>| the appropriate maven repo for 2.5.x, 2.6.x, and 2.7.x. Institutions
<br>| that wish to bring down the source code may, and will have to apply
<br>| the Sakai version patches themselves.Â
<br>|
<br>| This is practical for our purposes since the actual Sakai APIs we
<br>| interact with have barely changed since 2.4.x -- while the build
<br>| process and dependency management has shifted tremendously. Our gb2
<br>| patch is almost entirely to accommodate the pre-kernel/post-kernel
<br>| situation. As we make bug fixes and add functionality it is much more
<br>| appealing to us to have all institutions receive those changes
<br>| simultaneously rather than tying them to a particular Sakai verison.Â
<br>|
<br>| c.f.Â
<br>| <a href="http://jira.sakaiproject.org/browse/SAK-17428" target="_top" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-17428</a><br>| <a href="http://jira.sakaiproject.org/browse/SAK-17377" target="_top" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-17377</a><br>|
<br>| Â
<br>|
<br>|
<br>|
<br>| 2) The build process is platform specific (see point six in
<br>| <a href="https://source.sakaiproject.org/contrib//gradebook2/trunk/sakai/2-6-x/INSTALL.txt" target="_top" rel="nofollow">https://source.sakaiproject.org/contrib//gradebook2/trunk/sakai/2-6-x/INSTALL.txt</a><br>| )
<br>| We also need to know if any of our supported platforms may be a
<br>| problem
<br>| - it seems that Solaris might be.
<br>|
<br>|
<br>| Apologies, this particular line of the build process is no longer
<br>| relevant. I'm currently updating the INSTALL.txt to reflect that. The
<br>| system-dependency of GWT disappears at GWT version 2.0 (we're
<br>| expecting to be on 1.7.1 for the next few weeks before the final
<br>| release of 2.0) and in any case is only relevant for compiling the
<br>| Javascript code itself and testing it via GWT "Hosted Mode", a step
<br>| which in our trunk currently is no longer part of the maven build
<br>| process.Â
<br>|
<br>| Â
<br>|
<br>| 3) An open Jira suggests that L18N is incomplete
<br>| ( <a href="http://jira.sakaiproject.org/browse/GRBK-366" target="_top" rel="nofollow">http://jira.sakaiproject.org/browse/GRBK-366</a> ) This also suggests
<br>| that
<br>| L18N/L10N is missing from the PC evaluations
<br>|
<br>|
<br>| Yes, we need to do a due-diligence check through the code and
<br>| eliminate any cases where a string is hard-coded. We'll probably do
<br>| this in the next few days. Localization of numbers has not been
<br>| incorporated yet, but this should be relatively straightforward.Â
<br>| Â
<br>|
<br>| 4) GB2 does need modification to the gradebook service - James is
<br>| Jira'ing a patch so it can go about evaluating it and unfreezing
<br>| edu-services
<br>|
<br>|
<br>|
<br>| Again, this is the issue covered in (1) above. The JIRA isÂ
<br>| <a href="http://jira.sakaiproject.org/browse/SAK-17428" target="_top" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-17428</a><br>|
<br>| On Nov 22, 2009, at 10:39 AM, Berg, A.M. wrote:
<br>|
<br>|
<br>|
<br>|
<br>|
<br>| Hi all,
<br>|
<br>| I would like to announce the freezing of Samigo 2.7
<br>|
<br>| Monday, Anthony will:
<br>|
<br>| 1) create a samigo 2.7.x branch
<br>| 2) update samigo trunk poms to 2.8-SNAPSHOT
<br>|
<br>|
<br>| Alan
<br>|
<br>| Alan Berg
<br>| Interim QA Director - The Sakai Foundation
<br>|
<br>| Senior Developer / Quality Assurance
<br>| Group Education and Research Services
<br>| Central Computer Services
<br>| University of Amsterdam
<br>|
<br>| <a href="http://home.uva.nl/a.m.berg" target="_top" rel="nofollow">http://home.uva.nl/a.m.berg</a><br>|
<br>|
<br>|
<br>|
<br>| -----Original Message-----
<br>| From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=6" target="_top" rel="nofollow">sakai-dev-bounces@...</a> on behalf of Steve
<br>| Swinsburg
<br>| Sent: Sat 11/21/2009 3:16
<br>| To: Anthony Whyte
<br>| Cc: sakai-dev sakai-dev
<br>| Subject: Re: [Building Sakai] Master pom: removing
<br>| myfaces.zones.apache.orgrepo reference
<br>|
<br>| +1.
<br>|
<br>| Does anyone know if it's coming back?
<br>|
<br>| cheers,
<br>| Steve
<br>|
<br>|
<br>| On 21/11/2009, at 8:52 AM, Speelmon, Lance Day wrote:
<br>|
<br>| > +1
<br>| >
<br>| >
<br>| > Lance Speelmon
<br>| > Scholarly Technologist
<br>| >
<br>| > On Nov 20, 2009, at 4:25 PM, Anthony Whyte wrote:
<br>| >
<br>| >> Any objection to commenting out/removing the
<br>| myfaces.zones.apache.org repo reference in the master pom? I checked
<br>| the Apache network and it's nowhere to be seen. Excluding it should
<br>| speed up the builds a wee bit.
<br>| >>
<br>| >> Cheers,
<br>| >>
<br>| >> Anth
<br>| >>
<br>| >> <repository>
<br>| >>Â Â Â Â Â Â Â Â Â Â Â Â <id>apache-repo</id>
<br>| >>Â Â Â Â Â Â Â Â Â Â Â Â <name>apache-repo</name>
<br>| >>Â Â Â Â Â Â Â Â Â Â Â Â <layout>default</layout>
<br>| >>Â Â Â Â Â Â Â Â Â Â Â Â <url>
<br>| <a href="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</a> </url>
<br>| >>Â Â Â Â Â Â Â Â Â Â Â Â <snapshots>
<br>| >>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <enabled>false</enabled>
<br>| >>Â Â Â Â Â Â Â Â Â Â Â Â </snapshots>
<br>| >>Â Â Â Â Â Â Â Â </repository>
<br>| >>
<br>| >> Forbidden
<br>| >>
<br>| >> You don't have permission to access /dist/maven-repository on this
<br>| server.
<br>| >>
<br>| >> Additionally, a 403 Forbidden error was encountered while trying to
<br>| use an ErrorDocument to handle the request.
<br>| >>
<br>| >> Apache/2.0.63 (Unix) DAV/2 Server at myfaces.zones.apache.org Port
<br>| 80
<br>| >>
<br>| >> Begin forwarded message:
<br>| >>
<br>| >>> From: Seth Theriault < <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=7" target="_top" rel="nofollow">slt@...</a> >
<br>| >>> Date: November 19, 2009 2:00:16 AM GMT-05:00
<br>| >>> To: Anthony Whyte < <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=8" target="_top" rel="nofollow">arwhyte@...</a> >
<br>| >>> Cc: Speelman Lance < <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=9" target="_top" rel="nofollow">lance@...</a> >, Maurer Christopher <
<br>| <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=10" target="_top" rel="nofollow">chmaurer@...</a> >, Horwitz David < <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=11" target="_top" rel="nofollow">david.horwitz@...</a> >
<br>| >>> Subject: Re: Apache infrastructure machine status
<br>| >>>
<br>| >>> Anthony Whyte wrote:
<br>| >>>
<br>| >>>> Nothing I see in the Apache network that sheds any light on the
<br>| status
<br>| >>>> <a href="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</a><br>| >>>
<br>| >>> I think this repo is dead or out of date.
<br>| >>>
<br>| >>> Looking at:
<br>| >>>
<br>| >>>
<br>| <a href="http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven" target="_top" rel="nofollow">http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven</a><br>| >>>
<br>| >>> I think the libs are served out of the central maven2 repos
<br>| >>> now.
<br>| >>>
<br>| >>> Seth
<br>| >>>
<br>| >>>
<br>| >>
<br>| >> _______________________________________________
<br>| >> sakai-dev mailing list
<br>| >> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=12" target="_top" rel="nofollow">sakai-dev@...</a>
<br>| >> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>| >>
<br>| >> TO UNSUBSCRIBE: send email to
<br>| <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=13" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of
<br>| "unsubscribe"
<br>| >
<br>| > _______________________________________________
<br>| > sakai-dev mailing list
<br>| > <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=14" target="_top" rel="nofollow">sakai-dev@...</a>
<br>| > <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>| >
<br>| > TO UNSUBSCRIBE: send email to
<br>| <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=15" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of
<br>| "unsubscribe"
<br>|
<br>|
<br>|
<br>|
<br>|
<br>|
<br>|
<br>| _______________________________________________
<br>| sakai-qa mailing list
<br>| <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=16" target="_top" rel="nofollow">sakai-qa@...</a>
<br>| <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-qa" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-qa</a><br>|
<br>| TO UNSUBSCRIBE: send email to
<br>| <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=17" target="_top" rel="nofollow">sakai-qa-unsubscribe@...</a> with a subject of
<br>| "unsubscribe"
<br>|
<br>| _______________________________________________
<br>| sakai-dev mailing list
<br>| <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=18" target="_top" rel="nofollow">sakai-dev@...</a>
<br>| <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>|
<br>| TO UNSUBSCRIBE: send email to
<br>| <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=19" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of
<br>| "unsubscribe"
<br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=20" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473547&i=21" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26473310[Building Sakai] Deploy sakai + cas to listen all ip addresses2009-11-22T22:25:08Z2009-11-22T22:25:08ZThach LeDear,
<br><br>I would like to deploy the sakai which supports many address.
<br>Example: My host "rai-server" has an ip address 192.168.1.1.
<br><br>I have deployed the sakai 2.6.1 and CAS (<a href="http://rai-server:7433/cas" target="_top" rel="nofollow">http://rai-server:7433/cas</a>)
<br>with link <a href="http://rai-server:8433/" target="_top" rel="nofollow">http://rai-server:8433/</a>. It's OK. I have not configured
<br>mod_jk and apache yet.
<br><br>I found there are many fixed values in CAS configuration.
<br>Now, I want to configure the sakai + CAS in order to the user can
<br>access the sakai portal via <a href="http://192.1.168.1.1:8433" target="_top" rel="nofollow">http://192.1.168.1.1:8433</a> or
<br><a href="http://rai-server:8433" target="_top" rel="nofollow">http://rai-server:8433</a>.
<br><br>How can I do?
<br><br>Thach Le
<br><br />1) Modify Tomcat configuration
<br> File: $TOMCAT_HOME/conf/server.xml
<br> Open "SSL HTTP/1.1 Connector on port 8443"
<br> Add attributes:
<br> keystoreFile="${user.home}/keystore/keystore" keystorePass="tomcat"
<br><br>2) Modify sakai.properties
<br> serverUrl
<br> serverUrl=<a href="https://rai-server:8443" target="_top" rel="nofollow">https://rai-server:8443</a><br><br> serverName
<br> serverName=rai-server
<br><br> loggedOutUrl=<a href="https://rai-server:7443/cas/logout?url=http://rai-server/tys" target="_top" rel="nofollow">https://rai-server:7443/cas/logout?url=http://rai-server/tys</a><br><br> top.login=false
<br><br> container.login=true
<br><br> bottom.copyrighttext=
<br> version.sakai=2.5.5
<br><br> server.info.url=/library/content/resources-cdrom.html
<br> myworkspace.info.url=/library/content/resources-cdrom.html
<br><br> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473310&i=0" target="_top" rel="nofollow">setup.request=rai.trainer@...</a>
<br> ui.service=RAI Training Service
<br><br>3) Modify $TOMCAT_HOME\webapps\sakai-login-tool\WEB-INF\web.xml
<br> <filter>
<br> <filter-name>sakai.request</filter-name>
<br> <filter-class>org.sakaiproject.util.RequestFilter</filter-class>
<br> <!-- Thach added for CAS.START -->
<br> <url-pattern>/*</url-pattern>
<br> <dispatcher>REQUEST</dispatcher>
<br> <dispatcher>FORWARD</dispatcher>
<br> <dispatcher>INCLUDE</dispatcher>
<br> <!-- Thach added for CAS.END -->
<br> </filter>
<br><br><br> <!-- Thach added for CAS.START -->
<br> <filter>
<br> <filter-name>sakai.cas</filter-name>
<br> <filter-class>edu.yale.its.tp.cas.client.filter.CASFilter</filter-class>
<br> <init-param>
<br> <param-name>edu.yale.its.tp.cas.client.filter.loginUrl</param-name>
<br> <param-value><a href="https://rai-server:7443/cas/login" target="_top" rel="nofollow">https://rai-server:7443/cas/login</a></param-value>
<br> </init-param>
<br> <init-param>
<br> <param-name>edu.yale.its.tp.cas.client.filter.validateUrl</param-name>
<br> <param-value><a href="https://rai-server:7443/cas/serviceValidate" target="_top" rel="nofollow">https://rai-server:7443/cas/serviceValidate</a></param-value>
<br> </init-param>
<br> <init-param>
<br> <param-name>edu.yale.its.tp.cas.client.filter.serverName</param-name>
<br> <param-value>rai-server:8443</param-value>
<br> </init-param>
<br> <init-param>
<br> <param-name>edu.yale.its.tp.cas.client.filter.wrapRequest</param-name>
<br> <param-value>true</param-value>
<br> </init-param>
<br> </filter>
<br>
<br> <filter-mapping>
<br> <filter-name>sakai.cas</filter-name>
<br> <url-pattern>/container</url-pattern>
<br> </filter-mapping>
<br> <!-- Thach added for CAS.END -->
<br><br>4) Copy "casclient-2.2.0-M3.jar" into $TOMCAT_HOME\webapps\sakai-login-tool\WEB-INF\lib <br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473310&i=1" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473310&i=2" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26470022Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates2009-11-22T14:02:37Z2009-11-22T14:02:37ZNoah Botimer<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Thanks, Sean. This is a helpful sample for isolating the issue. Your account tells me that SAK-17423 is well placed and that we have some work to do.<div><br></div><div>Thanks,</div><div>-Noah<br><div><br></div><div><div><div>On Nov 21, 2009, at 10:12 AM, Sean Keesler wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">This works different for a form renderer than in a portfolio template.<br><br>I have a simple xsl file (using the relative path that seems to work for everyone):<br><br><div style="margin-left: 40px; color: rgb(0, 0, 153);"> <?xml version="1.0" encoding="UTF-8"?><br><xsl:stylesheet xmlns:xsl="<a href="http://www.w3.org/1999/XSL/Transform" target="_top" rel="nofollow">http://www.w3.org/1999/XSL/Transform</a>" version="1.0"><br> <xsl:import href="/group/PortfolioAdmin/authoring/passthrough.xsl"/><br> <br> <xsl:template match="/"><br> <xsl:text>Hey there!</xsl:text><br> </xsl:template><br> <br></xsl:stylesheet><br></div><br>When I use that xsl file for a form renderer, I get "Hey there"...just as I expect. <br>When I use it in a portfolio template, I get an error in the logs:<br><br>ERROR: '/group/PortfolioAdmin/authoring/passthrough.xsl (No such file or directory)'<br> FATAL ERROR: 'Could not compile stylesheet'<br><br>Isn't that weird?<br><br>Sean Keesler<br>130 Academy Street<br>Manlius, New York 13104 USA<br>315-663-7756<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26470022&i=0" target="_top" rel="nofollow">sean.keesler@...</a><br></blockquote></div><br></div></div></body></html><br />_______________________________________________
<br>portfolio mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26470022&i=1" target="_top" rel="nofollow">portfolio@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/portfolio" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/portfolio</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26470022&i=2" target="_top" rel="nofollow">portfolio-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Portfolio-f18155.html" embed="fixTarget[18155]" target="_top" >Sakai - Portfolio</a></p>tag:old.nabble.com,2006:post-26473684Re: [Building Sakai] QA 2.7.0 Compatability list.2009-11-22T13:11:39Z2009-11-22T13:11:39Zjrnorman<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">FWIW I support this proposal.<div><br></div><div>I note that subsequent comments are leading to minor amendments, which I see as healthy but not changing the general thrust of the proposal.</div><div><br></div><div>Thanks Alan</div><div>John</div><div><br><div><div>On 19 Nov 2009, at 18:03, Berg, A.M. wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div>
<!-- Converted from text/plain format --><p><font size="2">Dear Management, QA and Dev list,<br>
<br>
The QA process for 2.7 is starting and we need to pin down the server testing environments for this round. The list below represents the consensus opinion of the release management WG. Unless there is a reasoned opinion against these recommendations, for operational timing reasons we will test Sakai 2.7 as follows:<br>
<br>
1. OS: contingent on stock of available QA servers (historically Solaris, Linux (RHEL, openSuse, Ubuntu, zLinux), Win 2008)<br>
<br>
2. JVM: Java 1.6 compiled with compatibility flags as David Haines has suggested<br>
<br>
See <a href="http://n2.nabble.com/WG-Sakai-QA-SAK-15874-Java-1-6-transition-td4026387.html" target="_top" rel="nofollow">http://n2.nabble.com/WG-Sakai-QA-SAK-15874-Java-1-6-transition-td4026387.html</a><br>
3. Servlet Containers: Tomcat: 5.5.28, Websphere 6.1<br>
<br>
Note: Tomcat 5.5.27+ enforces strict quote escaping which creates issues for certain Sakai JSF-based tools (e.g. OSP). We recommend that these issues be addressed in 2.7.0 so that deployers will not be required to modify their JVM settings with -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false.<br>
<br>
4. Databases: HSQLDB 1.8.0.7, MySQL 5.0, Oracle 9i and 10g, DB2 9.1<br>
<br>
5. Browsers: latest versions of Firefox and IE (including the newest beta) and also IE 6 onwards<br>
<br>
Alan<br>
<br>
Alan Berg<br>
Interim QA Director - The Sakai Foundation<br>
<br>
Senior Developer / Quality Assurance<br>
Group Education and Research Services<br>
Central Computer Services<br>
University of Amsterdam<br>
<br>
<a href="http://home.uva.nl/a.m.berg" target="_top" rel="nofollow">http://home.uva.nl/a.m.berg</a></font>
</p>
</div>
_______________________________________________<br>sakai-dev mailing list<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473684&i=0" target="_top" rel="nofollow">sakai-dev@...</a><br>http://collab.sakaiproject.org/mailman/listinfo/sakai-dev<br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473684&i=1" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"</blockquote></div><br></div></body></html><br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473684&i=2" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473684&i=3" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26466936[Building Sakai] Trunk update: pom versions (2.8-SNAPSHOT)2009-11-22T08:49:59Z2009-11-22T08:49:59ZAnthony Whyte<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Trunk poms have been updated to 2.8-SNAPSHOT. See my email of 20 Nov 2009 (appended below) for more details regarding this update as well as instructions for updating your trunk code and stocking your local .m2 repository.<div><br></div><div>KNOWN ISSUE: build times slowed by dead repo look up (kernel). </div><div><br></div><div>I commented out the inactive myfaces.zones.apache.org/dist/maven-repository in the Sakai trunk master pom but much to my surprise I noticed that Kernel trunk (1.1.0-beta04-SNAPSHOT) also checks the myfaces.zones repository. I was not expecting the kernel to be checking a UI-framework related repo. Anyways, I've updated the Kernel to fix this but I do not have time today to refresh the Kernel snapshot artifacts. If David has time perhaps he can do a kernel snapshot refresh. Otherwise, one of us will do it Monday.</div><div><br></div><div>Cheers,</div><div><br></div><div>Anthony</div><div><div><br></div><div><br></div><div><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>From: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Anthony Whyte <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466936&i=0" target="_top" rel="nofollow">arwhyte@...</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>Date: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">November 20, 2009 5:23:45 PM GMT-05:00</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>To: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">sakai-dev sakai-dev <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466936&i=1" target="_top" rel="nofollow">sakai-dev@...</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>Subject: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; "><b>Trunk: 2.8-SNAPSHOT pom update (Sunday, 22 Nov. 2009)</b></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div></div><div>With the creation of the 2.7.x branch it is time to update all trunk poms to version 2.8-SNAPSHOT. I plan to perform this update over the weekend.<br><br>EXCEPTIONS<br><br>Indie trunk project poms will not be affected by this update. Incrementing their versions will be handled on a project-by-project basis when required. Projects include:<br><br>common<br>edu-services<br>emailtemplateservice<br>entitybroker<br>jsf<br>msgcntr<br>polls<br>samigo<br>search<br><br>Experimental (-Pexperimental)<br><br>basicLTI<br>Profile2<br>SiteStats<br>tinyurlservice<br><br>Note: in case you are wondering the above Indie projects build and deploy properly to Tomcat.<br><br>TRUNK DEVELOPER IMPACT<br><br>1. Perform an svn update.<br><br>2. Confirm you are running Maven 2.0.10 (at a minimum)<br><br>mvn -- version<br><br>3. If not get it here:<br><br><a href="http://maven.apache.org/download.html" target="_top" rel="nofollow">http://maven.apache.org/download.html</a><br><br>4. Install to populate your local .m2 repo with 2.8-SNAPHSHOT artifacts<br><br>mvn clean install<br><br>5. Deploy to Tomcat (a clean Tomcat of course)<br><br>mvn clean install sakai:deploy<br>or<br>mvn -Pexperimental clean install sakai:deploy<br><br>____________________<br><br>My localhost footer:<br><br>Copyright 2003-2008 The Sakai Foundation. All rights reserved. Portions of Sakai are copyrighted by other parties as described in the Acknowledgments screen.<br>LocalSakaiName - TRUNK - Sakai 2.8.0 - Server localhost<br><br>Cheers,<br><br>Anth<br></div></blockquote><div><br></div><div><br></div><div><br></div></div></div></body></html><br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466936&i=2" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466936&i=3" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26466431Re: [Building Sakai] [WG: Sakai QA] Samigo 2.7 Freeze2009-11-22T07:51:37Z2009-11-22T07:51:37ZAnthony Whyte<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">One exception to the Samigo team's decision to freeze new features for 2.7: Samigo, edu-services and the gradebook teams need to decide if GB2-related SAK merges are acceptable for inclusion in 2.7. I recommend the three teams collaborate in order to frame a joint recommendation. See summary of concerns below.<div><br></div><div>Cheers,</div><div><br></div><div>Anth<br><div><br></div><div><br></div><div><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>From: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">James Renfro <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=0" target="_top" rel="nofollow">jlrenfro@...</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>Date: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">November 21, 2009 7:43:32 PM GMT-05:00</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>To: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">David Horwitz <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=1" target="_top" rel="nofollow">david.horwitz@...</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>Cc: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">"<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=2" target="_top" rel="nofollow">management@...</a>" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=3" target="_top" rel="nofollow">management@...</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>Subject: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; "><b>Re: [Management] GB2 Concernes</b></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div></div>Hi David,<br>Not sure if you're looking for responses directly from UCDavis at this point, but thought I'd answer what I could here in case that's helpful.<br><br>See below for inline responses. <br><br>Thanks,<br>James.<br><br><br><div class="gmail_quote">On Fri, Nov 20, 2009 at 5:29 AM, David Horwitz <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=4" target="_top" rel="nofollow">david.horwitz@...</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; padding-left: 1ex; ">Hi All,<br><br>After a brief poke around in GB2 I have a number of concerns that seems<br>to have slipped through the PC process:<br><br>1) There is no build for the current trunk (This is blocker but should<br>be fairly easy to fix)<br></blockquote><div><br>Just to clarify the exact situation here. Building against current trunk / 2.7 requires three patches at this moment that are provided as part of the module itself. <br> (1) against edu-services to bring the original gradebook data model up-to-date<br> (2) against the gb2 code itself, which is checked in as 2.5.5 <br> (3) against the sam module<br><br>The (1) patch will be eliminated if and when the Gradebook committers approve SAK-17428, and the (2) patch will be eliminated in the next couple of days when I commit that change. (3) will be eliminated when the Samigo committers approve SAK-17377. <br><br>Of course, the question then becomes exactly what you want tools to do -- should gb2 trunk build against fnd trunk, or the 2.7.x branch? I assume trunk. Especially at this moment, with 2.5.x, 2.6.x, 2.7.x, and trunk all currently in existence and supported, it is not really feasible, afaics, for a tool to create a branch for each, in addition to the tool's own versioning and development. It's a merging nightmare. Our preference would be to maintain GB2 trunk against FND trunk or 2.7.x and provide binary artifacts for distribution via the Sakai maven repositories. I believe we can accomplish this currently by maintaining sakai comptability patches and applying these ourselves on each tag release, compiling a release artifact and uploading it to the appropriate maven repo for 2.5.x, 2.6.x, and 2.7.x. Institutions that wish to bring down the source code may, and will have to apply the Sakai version patches themselves. <br><br>This is practical for our purposes since the actual Sakai APIs we interact with have barely changed since 2.4.x -- while the build process and dependency management has shifted tremendously. Our gb2 patch is almost entirely to accommodate the pre-kernel/post-kernel situation. As we make bug fixes and add functionality it is much more appealing to us to have all institutions receive those changes simultaneously rather than tying them to a particular Sakai verison. <br><br>c.f. <br><a href="http://jira.sakaiproject.org/browse/SAK-17428" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-17428</a><br><a href="http://jira.sakaiproject.org/browse/SAK-17377" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-17377</a><br><br> <br><br></div><blockquote class="gmail_quote" style="border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; padding-left: 1ex; ">2) The build process is platform specific (see point six in<br><a href="https://source.sakaiproject.org/contrib//gradebook2/trunk/sakai/2-6-x/INSTALL.txt" target="_blank" rel="nofollow">https://source.sakaiproject.org/contrib//gradebook2/trunk/sakai/2-6-x/INSTALL.txt</a>)<br>We also need to know if any of our supported platforms may be a problem<br>- it seems that Solaris might be.<br></blockquote><div><br>Apologies, this particular line of the build process is no longer relevant. I'm currently updating the INSTALL.txt to reflect that. The system-dependency of GWT disappears at GWT version 2.0 (we're expecting to be on 1.7.1 for the next few weeks before the final release of 2.0) and in any case is only relevant for compiling the Javascript code itself and testing it via GWT "Hosted Mode", a step which in our trunk currently is no longer part of the maven build process. <br><br> </div><blockquote class="gmail_quote" style="border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; padding-left: 1ex; ">3) An open Jira suggests that L18N is incomplete<br>(<a href="http://jira.sakaiproject.org/browse/GRBK-366" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/GRBK-366</a>) This also suggests that<br>L18N/L10N is missing from the PC evaluations<br></blockquote><div><br>Yes, we need to do a due-diligence check through the code and eliminate any cases where a string is hard-coded. We'll probably do this in the next few days. Localization of numbers has not been incorporated yet, but this should be relatively straightforward. <br> </div><blockquote class="gmail_quote" style="border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; padding-left: 1ex; ">4) GB2 does need modification to the gradebook service - James is<br>Jira'ing a patch so it can go about evaluating it and unfreezing<br>edu-services<br><br></blockquote><div><br>Again, this is the issue covered in (1) above. The JIRA is <br><a href="http://jira.sakaiproject.org/browse/SAK-17428" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-17428</a></div></div></blockquote></div></div><div><div>On Nov 22, 2009, at 10:39 AM, Berg, A.M. wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <div> <!-- Converted from text/plain format --><p><font size="2">Hi all,<br> <br> I would like to announce the freezing of Samigo 2.7<br> <br> Monday, Anthony will:<br> <br> 1) create a samigo 2.7.x branch<br> 2) update samigo trunk poms to 2.8-SNAPSHOT<br> <br> <br> Alan<br> <br> Alan Berg<br> Interim QA Director - The Sakai Foundation<br> <br> Senior Developer / Quality Assurance<br> Group Education and Research Services<br> Central Computer Services<br> University of Amsterdam<br> <br> <a href="http://home.uva.nl/a.m.berg" target="_top" rel="nofollow">http://home.uva.nl/a.m.berg</a><br> <br> <br> <br> <br> -----Original Message-----<br> From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=5" target="_top" rel="nofollow">sakai-dev-bounces@...</a> on behalf of Steve Swinsburg<br> Sent: Sat 11/21/2009 3:16<br> To: Anthony Whyte<br> Cc: sakai-dev sakai-dev<br> Subject: Re: [Building Sakai] Master pom: removing myfaces.zones.apache.orgrepo reference<br> <br> +1.<br> <br> Does anyone know if it's coming back?<br> <br> cheers,<br> Steve<br> <br> <br> On 21/11/2009, at 8:52 AM, Speelmon, Lance Day wrote:<br> <br> > +1<br> ><br> ><br> > Lance Speelmon<br> > Scholarly Technologist<br> ><br> > On Nov 20, 2009, at 4:25 PM, Anthony Whyte wrote:<br> ><br> >> Any objection to commenting out/removing the myfaces.zones.apache.org repo reference in the master pom? I checked the Apache network and it's nowhere to be seen. Excluding it should speed up the builds a wee bit.<br> >><br> >> Cheers,<br> >><br> >> Anth<br> >><br> >> <repository><br> >> <id>apache-repo</id><br> >> <name>apache-repo</name><br> >> <layout>default</layout><br> >> <url><a href="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</a></url><br> >> <snapshots><br> >> <enabled>false</enabled><br> >> </snapshots><br> >> </repository><br> >><br> >> Forbidden<br> >><br> >> You don't have permission to access /dist/maven-repository on this server.<br> >><br> >> Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.<br> >><br> >> Apache/2.0.63 (Unix) DAV/2 Server at myfaces.zones.apache.org Port 80<br> >><br> >> Begin forwarded message:<br> >><br> >>> From: Seth Theriault <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=6" target="_top" rel="nofollow">slt@...</a>><br> >>> Date: November 19, 2009 2:00:16 AM GMT-05:00<br> >>> To: Anthony Whyte <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=7" target="_top" rel="nofollow">arwhyte@...</a>><br> >>> Cc: Speelman Lance <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=8" target="_top" rel="nofollow">lance@...</a>>, Maurer Christopher <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=9" target="_top" rel="nofollow">chmaurer@...</a>>, Horwitz David <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=10" target="_top" rel="nofollow">david.horwitz@...</a>><br> >>> Subject: Re: Apache infrastructure machine status<br> >>><br> >>> Anthony Whyte wrote:<br> >>><br> >>>> Nothing I see in the Apache network that sheds any light on the status<br> >>>> <a href="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</a><br> >>><br> >>> I think this repo is dead or out of date.<br> >>><br> >>> Looking at:<br> >>><br> >>> <a href="http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven" target="_top" rel="nofollow">http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven</a><br> >>><br> >>> I think the libs are served out of the central maven2 repos<br> >>> now.<br> >>><br> >>> Seth<br> >>><br> >>><br> >><br> >> _______________________________________________<br> >> sakai-dev mailing list<br> >> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=11" target="_top" rel="nofollow">sakai-dev@...</a><br> >> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br> >><br> >> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=12" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<br> ><br> > _______________________________________________<br> > sakai-dev mailing list<br> > <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=13" target="_top" rel="nofollow">sakai-dev@...</a><br> > <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br> ><br> > TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=14" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<br> <br> <br> <br> <br> <br> <br> <br> </font> </p> </div> _______________________________________________<br>sakai-qa mailing list<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=15" target="_top" rel="nofollow">sakai-qa@...</a><br>http://collab.sakaiproject.org/mailman/listinfo/sakai-qa<br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=16" target="_top" rel="nofollow">sakai-qa-unsubscribe@...</a> with a subject of "unsubscribe"</blockquote></div><br></body></html><br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=17" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466431&i=18" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26466345[Building Sakai] Samigo 2.7 Freeze2009-11-22T07:39:55Z2009-11-22T07:39:55ZBerg, A.M.<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>Samigo 2.7 Freeze</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi all,<BR>
<BR>
I would like to announce the freezing of Samigo 2.7<BR>
<BR>
Monday, Anthony will:<BR>
<BR>
1) create a samigo 2.7.x branch<BR>
2) update samigo trunk poms to 2.8-SNAPSHOT<BR>
<BR>
<BR>
Alan<BR>
<BR>
Alan Berg<BR>
Interim QA Director - The Sakai Foundation<BR>
<BR>
Senior Developer / Quality Assurance<BR>
Group Education and Research Services<BR>
Central Computer Services<BR>
University of Amsterdam<BR>
<BR>
<A HREF="http://home.uva.nl/a.m.berg" target="_top" rel="nofollow">http://home.uva.nl/a.m.berg</A><BR>
<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=0" target="_top" rel="nofollow">sakai-dev-bounces@...</a> on behalf of Steve Swinsburg<BR>
Sent: Sat 11/21/2009 3:16<BR>
To: Anthony Whyte<BR>
Cc: sakai-dev sakai-dev<BR>
Subject: Re: [Building Sakai] Master pom: removing myfaces.zones.apache.orgrepo reference<BR>
<BR>
+1.<BR>
<BR>
Does anyone know if it's coming back?<BR>
<BR>
cheers,<BR>
Steve<BR>
<BR>
<BR>
On 21/11/2009, at 8:52 AM, Speelmon, Lance Day wrote:<BR>
<BR>
> +1<BR>
><BR>
><BR>
> Lance Speelmon<BR>
> Scholarly Technologist<BR>
><BR>
> On Nov 20, 2009, at 4:25 PM, Anthony Whyte wrote:<BR>
><BR>
>> Any objection to commenting out/removing the myfaces.zones.apache.org repo reference in the master pom? I checked the Apache network and it's nowhere to be seen. Excluding it should speed up the builds a wee bit.<BR>
>><BR>
>> Cheers,<BR>
>><BR>
>> Anth<BR>
>><BR>
>> <repository><BR>
>> <id>apache-repo</id><BR>
>> <name>apache-repo</name><BR>
>> <layout>default</layout><BR>
>> <url><A HREF="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</A></url><BR>
>> <snapshots><BR>
>> <enabled>false</enabled><BR>
>> </snapshots><BR>
>> </repository><BR>
>><BR>
>> Forbidden<BR>
>><BR>
>> You don't have permission to access /dist/maven-repository on this server.<BR>
>><BR>
>> Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.<BR>
>><BR>
>> Apache/2.0.63 (Unix) DAV/2 Server at myfaces.zones.apache.org Port 80<BR>
>><BR>
>> Begin forwarded message:<BR>
>><BR>
>>> From: Seth Theriault <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=1" target="_top" rel="nofollow">slt@...</a>><BR>
>>> Date: November 19, 2009 2:00:16 AM GMT-05:00<BR>
>>> To: Anthony Whyte <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=2" target="_top" rel="nofollow">arwhyte@...</a>><BR>
>>> Cc: Speelman Lance <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=3" target="_top" rel="nofollow">lance@...</a>>, Maurer Christopher <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=4" target="_top" rel="nofollow">chmaurer@...</a>>, Horwitz David <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=5" target="_top" rel="nofollow">david.horwitz@...</a>><BR>
>>> Subject: Re: Apache infrastructure machine status<BR>
>>><BR>
>>> Anthony Whyte wrote:<BR>
>>><BR>
>>>> Nothing I see in the Apache network that sheds any light on the status<BR>
>>>> <A HREF="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</A><BR>
>>><BR>
>>> I think this repo is dead or out of date.<BR>
>>><BR>
>>> Looking at:<BR>
>>><BR>
>>> <A HREF="http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven" target="_top" rel="nofollow">http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven</A><BR>
>>><BR>
>>> I think the libs are served out of the central maven2 repos<BR>
>>> now.<BR>
>>><BR>
>>> Seth<BR>
>>><BR>
>>><BR>
>><BR>
>> _______________________________________________<BR>
>> sakai-dev mailing list<BR>
>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=6" target="_top" rel="nofollow">sakai-dev@...</a><BR>
>> <A HREF="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</A><BR>
>><BR>
>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=7" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<BR>
><BR>
> _______________________________________________<BR>
> sakai-dev mailing list<BR>
> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=8" target="_top" rel="nofollow">sakai-dev@...</a><BR>
> <A HREF="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</A><BR>
><BR>
> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=9" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML><br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=10" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466345&i=11" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26466278Re: [Building Sakai] Automating the site creation process AND Sakai 3 Groups2009-11-22T07:35:49Z2009-11-22T07:35:49ZjrnormanThe Oxford document makes an interesting read as an example of a 'group' structure that doesn't really need a site.
<br><br>John
<br><br>On 20 Nov 2009, at 10:43, dktr adam marshall wrote:
<br><div class='shrinkable-quote'><br>> We allow staff members to create sites - they basically use the same
<br>> workflow pages as when (us) administrators create sites. All this is managed
<br>> by a new type of site (of type 'admin'). In a nutshell, if a user is a
<br>> participant within one of these sites then they are able to create their
<br>> own.
<br>>
<br>> We are in the process of committing back a patch (or patches) built against
<br>> trunk.
<br>>
<br>> A good place to start is to look at our documentation, this will give an
<br>> idea of what can be done. If you're interested then get back in touch.
<br>>
<br>> <a href="https://weblearn.ox.ac.uk/access/content/group/info/step/adminsites1.pdf" target="_top" rel="nofollow">https://weblearn.ox.ac.uk/access/content/group/info/step/adminsites1.pdf</a><br>>
<br>> and to a lesser extent
<br>>
<br>> <a href="https://weblearn.ox.ac.uk/access/content/group/info/step/hierarchy7.pdf" target="_top" rel="nofollow">https://weblearn.ox.ac.uk/access/content/group/info/step/hierarchy7.pdf</a><br>>
<br>> Feel free to browse our help site at:
<br>>
<br>> <a href="https://weblearn.ox.ac.uk/portal/hierarchy/info" target="_top" rel="nofollow">https://weblearn.ox.ac.uk/portal/hierarchy/info</a>
<br>>
<br>> adam
<br>> -----Original Message-----
<br>> From: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=0" target="_top" rel="nofollow">sakai-dev-bounces@...</a>
<br>> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=1" target="_top" rel="nofollow">sakai-dev-bounces@...</a>] On Behalf Of Robert
<br>> Armstrong
<br>> Sent: 19 November 2009 19:57
<br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=2" target="_top" rel="nofollow">sakai-dev@...</a>
<br>> Subject: [Building Sakai] Automating the site creation process
<br>>
<br>> We are looking to have an automated way that faculty can fill out a form
<br>> that will (a) Create a new course site or (b) copy content from an existing
<br>> course site into a new course site.
<br>>
<br>> Has anyone developed this and would you be willing to share?
<br>>
<br>> Thanks
<br>>
<br>> Bob Armstrong
<br>> Training and Delivery Specialist
<br>> Johns Hopkins University - Whiting School of Engineering
<br>> 6810 Deerpath Road, Suite 200, Elkridge, MD 21075
<br>> Phone:410-516-2280
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=3" target="_top" rel="nofollow">barmstrong@...</a>
<br>>
<br>>
<br>>
<br>> _______________________________________________
<br>> sakai-dev mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=4" target="_top" rel="nofollow">sakai-dev@...</a>
<br>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>>
<br>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=5" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a>
<br>> with a subject of "unsubscribe"
<br>>
<br>> _______________________________________________
<br>> sakai-dev mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=6" target="_top" rel="nofollow">sakai-dev@...</a>
<br>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>>
<br>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=7" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
</div><br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=8" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26466278&i=9" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26465879Re: [DG: User Experience] JavaScript event based development (Sakai 3)2009-11-22T06:47:58Z2009-11-22T06:47:58ZjrnormanAn open question to which I don't have an answer, would be whether to address such questions to the Fluid list? We might start by asking if such issues are welcome there and report back on this list the status of any developing thoughts...
<br><br>Just a suggestion, but potentially it would aid with convergence and create an opportunity to air Sakai issues with a wider set of expertise.
<br><br>John
<br><br>On 18 Nov 2009, at 19:28, Eli Cochran wrote:
<br><div class='shrinkable-quote'><br>> Oszkar,
<br>> You've hit on something that was itching the back of my brain while I was writing my rant on events.
<br>>
<br>> One of the challenges with multiple binding to the same event is having control, or the sense of control, over the order that each listener will be triggered and what to do in those situations where components really are intertwined.
<br>>
<br>> I like your solution of chaining to solve this problem. Although it's worth asking first if there are ways to reduce the dependences before chaining becomes necessary.
<br>>
<br>> Another tricky area is when listeners need to respond to each other or prevent or modify the action of the firer.
<br>>
<br>> Fluid got around this in their library with a concept of "preventable" events. (I put this forward as an example of a concept, and not to push "the Fluid way"). This allows Fluid events to behave like browser events with the ability to stopPropogation and return a boolean to the caller to stop the action.
<br>>
<br>> (Aside: To help keep our heads clear, Fluid uses a naming convention separating our events into "before events" (onPageLoad) and "after events" (afterPageLoad). I highly recommend this convention.)
<br>>
<br>> - Eli
<br>>
<br>>
<br>>
<br>>
<br>> On Nov 18, 2009, at 10:53 AM, Oszkar Nagy wrote:
<br>>
<br>>> 2. Chaining:
<br>>>
<br>>> LoadControl was a result of a site.js cleanup iteration, where I wanted
<br>>> to formulate a clear(er) view of what is happening when, and make the
<br>>> code more readable by seeing the chain of events. The proper way to do
<br>>> this kind of thing is through events IMHO, but we haven't reached that
<br>>> stage yet. But even with events I think it's important to always
<br>>> organise the code in such way that everybody has an instant
<br>>> understanding of the order of events, which perhaps raises questions
<br>>> about the need of a "chainer" where you could simply chain things up and
<br>>> wouldn't need to add callbacks within callbacks within callbacks (as in
<br>>> site_admin.js), but use something like this:
<br>>>
<br>>> sakai.lib.util.chainer.init();
<br>>>
<br>>> sakai.lib.util.chainer.add(load_site_data, param1, param2);
<br>>> sakai.lib.util.chainer.add(load_profile_data, param1);
<br>>> sakai.lib.util.chainer.add(display_profile_data);
<br>>> sakai.lib.util.chainer.add(render_widgets);
<br>>>
<br>>> sakai.lib.util.chainer.execute();
<br>>>
<br>>> which would execute all the added functions, sequentially one after
<br>>> another. Not sure all of the details around the implementation of such a
<br>>> system, but I could imagine something based on dynamically created
<br>>> events for each function chained (basically a dynamically set up event
<br>>> chain).
<br>>>
<br>>> Having access to an easy event based pattern and also to an easy
<br>>> sequential pattern would make life considerably easier for a front-end
<br>>> developer staging page functionality.
<br>>
<br>> . . . . . . . . . . . . . . . . . . .
<br>>
<br>> Eli Cochran
<br>> user interaction developer
<br>> ETS, UC Berkeley
<br>>
<br>>
<br>> _______________________________________________
<br>> sakai-ux mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26465879&i=0" target="_top" rel="nofollow">sakai-ux@...</a>
<br>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br>>
<br>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26465879&i=1" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"
</div><br>_______________________________________________
<br>sakai-ux mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26465879&i=2" target="_top" rel="nofollow">sakai-ux@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26465879&i=3" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---User-Experience-f30853.html" embed="fixTarget[30853]" target="_top" >Sakai - User Experience</a></p>tag:old.nabble.com,2006:post-26465843Re: [DG: User Experience] [3akai] Fluid Framework2009-11-22T06:42:59Z2009-11-22T06:42:59Zjrnorman<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The expressed and realised goal of the UX developers at Cambridge is to use as much of the Fluid work as we reasonably can. However, with very limited resource and time, I have asked that we rely on Fluid's own designation of production readiness in choosing which components and parts of the framework we can use. We do the Fluid project no favours if we take something that is not finished and run into trouble that we then blame the trouble on Fluid.<div><br></div><div>The key expectation that I have of "production ready" Fluid components is that they should work in all our supported browsers (which suggests convergence with the set Fluid support) AND that any bugs are fixed in a few days. This last issue is not trivial, because Fluid (like Sakai) is pushing forward on a lot of new stuff and (AFAIK) does not have dedicated maintenance resource (again like Sakai, but unlike Sakai the Fluid team is not running production systems that depend on Fluid code).</div><div><br></div><div>I want to emphasise that we are fully engaged in using Fluid wherever possible and we are completely aligned with the goals. However, responsible use of their code means waiting until things are baked *unless we plan to get involved in fixing things*. I'd like to be getting involved more, but as I said - we are very resource constrained at present. A desirable consequence of greater UX development engagement may well be the ability to contribute more than adoption and bug reports, but as a community we need to increase our Javascript skills and resource in order to do that alongside our own development.</div><div><br></div><div>John</div><div><br><div><div>On 18 Nov 2009, at 17:43, Eli Cochran wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>During the Sakai 3 UX Developers meeting on Friday, I suggested that we use the Fluid Framework for Sakai 3. A concern was voiced that the Fluid Framework is not "production ready". I've had a little time to think about that characterization and to discuss it with Colin Clark, the Fluid technical lead. </div><div><br></div><div>First, I really must purge the term <i>Fluid Framework</i> from my brain since the Fluid Project now refers to it as the <i>Infusion Framework</i>. </div><div><br></div><div>The <span class="Apple-style-span" style="font-style: italic; ">Infusion Framework</span> is a collection of many different <i>framework</i> <i>capabilities</i> which should be considered both as a whole and individually -- one can pick and choose which capabilities one takes advantage of. </div><div><br></div><div>By using Fluid Infusion components, one is using <i>the Framework</i>. Every component is built on top of <i>Fluid.js</i>, and <i>Fluid.js</i> is the framework*. The framework provides many things: component and sub-component support, glue to bind model and view, a very robust event system, accessibility support, a client-side renderer, etc, etc. </div><div><br></div><div><i>*The Infusion Framework also contains the Fluid Skinning System which is not a part of Fluid.js.</i></div><div><br></div><div>The Infusion Framework is evolving and growing and perhaps that is cause for concern. Then again, if the code were not not changing that would be cause for concern as well. Colin reiterated Fluid's commitment to support the many current users of Fluid, both by supporting the current code and by evolving the code carefully and respectfully. </div><div><br></div><div>In future discussions I will be sure to be more specific when talking about which capabilities we should take advantage of. (On Friday, I was thinking primarily about the Fluid event system.) But let's not dismiss <i>the framework</i> out of hand. We're already loading the library so lets use what we can from it -- the Infusion Framework is full of wonderful functionality. <a href="http://wiki.fluidproject.org/display/fluid/Infusion+Framework" target="_top" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Infusion+Framework</a></div><div><br></div><div>Thanks,</div><div>Eli </div><div><br></div><div><br></div><div><div>
<span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-family: Helvetica; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-family: Helvetica; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-family: Helvetica; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-family: Helvetica; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 12px;"><span class="Apple-style-span" style="font-size: 12px; "><span class="Apple-style-span" style="font-size: 12px; ">. . . . . . . . . . . . . . . . . . .</span></span></span></font></div><div><font class="Apple-style-span" face="Trebuchet MS"><br class="khtml-block-placeholder"></font></div><div><font class="Apple-style-span" face="Trebuchet MS"><span class="Apple-style-span" style="font-family: Trebuchet MS; "><span class="Apple-style-span" style="font-family: Trebuchet MS; "><span class="Apple-style-span" style="font-family: Trebuchet MS; "><span class="Apple-style-span" style="font-family: Trebuchet MS; ">Eli Cochran</span></span></span></span></font></div><div><font class="Apple-style-span" face="Trebuchet MS"><span class="Apple-style-span" style="font-family: Trebuchet MS; "><span class="Apple-style-span" style="font-family: Trebuchet MS; "><span class="Apple-style-span" style="font-family: Trebuchet MS; "><span class="Apple-style-span" style="font-family: Trebuchet MS; ">user interaction developer</span></span></span></span></font></div><div><font class="Apple-style-span" face="Trebuchet MS"><span class="Apple-style-span" style="font-family: Trebuchet MS; "><span class="Apple-style-span" style="font-family: Trebuchet MS; "><span class="Apple-style-span" style="font-family: Trebuchet MS; "><span class="Apple-style-span" style="font-family: Trebuchet MS; ">ETS, UC Berkeley</span></span></span></span></font></div><br class="Apple-interchange-newline"></span></span></span></span>
</div>
<br></div><br>
--~--~---------~--~----~------------~-------~--~----~<br>
You received this message because you are subscribed to the Google Groups "Sakai 3 Design" group. <br> To post to this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26465843&i=0" target="_top" rel="nofollow">3akai@...</a> <br> To unsubscribe from this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26465843&i=1" target="_top" rel="nofollow">3akai+unsubscribe@...</a> <br> For more options, visit this group at <a href="http://groups.google.com/group/3akai?hl=en-GB" target="_top" rel="nofollow">http://groups.google.com/group/3akai?hl=en-GB</a> <br> <br>
-~----------~----~----~----~------~----~------~--~---<br>
</div><br>
</blockquote></div><br></div></body></html><br />_______________________________________________
<br>sakai-ux mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26465843&i=2" target="_top" rel="nofollow">sakai-ux@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-ux" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-ux</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26465843&i=3" target="_top" rel="nofollow">sakai-ux-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---User-Experience-f30853.html" embed="fixTarget[30853]" target="_top" >Sakai - User Experience</a></p>tag:old.nabble.com,2006:post-26457406Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates2009-11-21T07:12:11Z2009-11-21T07:12:11ZSean Keesler-2This works different for a form renderer than in a portfolio template.<br><br>I have a simple xsl file (using the relative path that seems to work for everyone):<br><br><div style="margin-left: 40px; color: rgb(0, 0, 153);">
<?xml version="1.0" encoding="UTF-8"?><br><xsl:stylesheet xmlns:xsl="<a href="http://www.w3.org/1999/XSL/Transform" target="_top" rel="nofollow">http://www.w3.org/1999/XSL/Transform</a>" version="1.0"><br>
   <xsl:import href="/group/PortfolioAdmin/authoring/passthrough.xsl"/><br>   <br>   <xsl:template match="/"><br>      <xsl:text>Hey there!</xsl:text><br>   </xsl:template><br>
   <br></xsl:stylesheet><br></div><br>When I use that xsl file for a form renderer, I get "Hey there"...just as I expect. <br>When I use it in a portfolio template, I get an error in the logs:<br><br>ERROR: '/group/PortfolioAdmin/authoring/passthrough.xsl (No such file or directory)'<br>
FATAL ERROR:Â 'Could not compile stylesheet'<br><br>Isn't that weird?<br><br>Sean Keesler<br>130 Academy Street<br>Manlius, New York 13104 USA<br>315-663-7756<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=0" target="_top" rel="nofollow">sean.keesler@...</a><br>
<br><br><div class="gmail_quote">On Fri, Nov 20, 2009 at 6:58 PM, Noah Botimer <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=1" target="_top" rel="nofollow">botimer@...</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="word-wrap: break-word;">
In general, the Content Hosting URI resolver should be in place when these XSLs execute. That means that an import on something like '/group/PortfolioAdmin/...xsl' should be valid. This also insulates your XSL from instance/hostname changes and so on. You will want to make sure that anything included/imported is public in Resources.<div>
<br></div><div>The tricky bit here is that XSL includes and so on that are not fully qualified URLs are not evaluated the same as they would by a browser. They are resolved locally, which, if the CHS glue isn't in place, will be somewhere deep in the app server (essentially useless). If we find that this is the case anywhere, we should fix it.</div>
<div><br></div><div>Note that this means '/access/content/group/PortfolioAdmin' is incorrect for things like include/import. It is, however, correct for referencing accessible items that the browser would hit (script, images, or stylesheets). There is a different construction for "additional materials" attached to a template, where you would typically pass the path from the XML to sakaifn:getReferenceUrl. (You can also pass your items like script URLs to getReferenceUrl if you remove /access/content.)</div>
<div><br></div><div>I cannot speak to the http/https behavior or the DTD 503s aside from that we should make sure that the local catalog is registered everywhere as in <a href="http://jira.sakaiproject.org/browse/SAK-16536" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-16536</a>. Along with local, internal references to your supplemental materials, this should make sure that your server isn't attempting external requests for what it needs.</div>
<div><div><br></div><div>Thanks,</div><div>-Noah<br><div><br><div><div><div></div><div class="h5"><div>On Nov 20, 2009, at 4:16 PM, hongbo zhang wrote:</div><br></div></div><blockquote type="cite"><div><div></div><div class="h5">
<div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">I just tested it with the localhost 2.6.0 instance.</span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">If I write </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p><p class="MsoNormal"><span style="color: darkgreen;"><xsl:include href="<a href="http://localhost:8080/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl" target="_blank" rel="nofollow">http://localhost:8080/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl</a>"/></span></p>
<p class="MsoNormal"><span style="color: darkgreen;">Â </span></p><p class="MsoNormal"><span style="color: darkgreen;">It does not work. It complains the stylesheet can not be complied. </span></p><p class="MsoNormal"><span style="color: darkgreen;">Â </span></p>
<p class="MsoNormal"><span style="color: darkgreen;">However if I use </span></p><p class="MsoNormal"><span style="color: darkgreen;">Â </span></p><p class="MsoNormal" style=""><span style="color: black;"><xsl:include</span><span style="color: rgb(51, 51, 51);"> href</span><span style="color: rgb(0, 102, 102);">=</span><span style="color: black;">"<a href="https://scholar.vt.edu/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl" target="_blank" rel="nofollow">https://scholar.vt.edu/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl</a>"/> </span></p>
<p class="MsoNormal"><span style="color: black;">   </span></p><p class="MsoNormal"><span style="color: black;">It works. </span></p><p class="MsoNormal"><span style="color: black;"> </span></p><p class="MsoNormal"><span style="color: black;">I attached the worked screen shot as well as the template file for the 2.6.0 test. The texts on the front page comes from a template in another xsl file. </span></p>
<p class="MsoNormal"><span style="color: black;">Â </span></p><p class="MsoNormal"><span style="color: black;">However, interestingly, both localhost and permanent URL methods work for 2.5.3 instance. </span></p><p class="MsoNormal">
<span style="color: black;">Â </span></p><p class="MsoNormal"><span style="color: black;">I guess, the permanent URL is important for 2.6. The URL should not be in the localhost. It should be a good workable URL. Many times, we use localhost for development, which might give some trouble.</span></p>
<p class="MsoNormal"><span style="color: black;">Â </span></p><p class="MsoNormal"><span style="color: black;">Just a thought.</span></p><p class="MsoNormal"><span style="color: black;">Â </span></p><p class="MsoNormal"><span style="color: black;">Hongbo</span></p>
<p class="MsoNormal"><span style="color: black;">Â </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p> <div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=2" target="_top" rel="nofollow">sean@...</a> [<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=3" target="_top" rel="nofollow">sean@...</a>] <b>On Behalf Of </b>Sean Keesler<br>
<b>Sent:</b> Friday, November 20, 2009 12:35 PM<br> <b>To:</b> Maurer, Christopher Wayne<br> <b>Cc:</b> Ackerman, Erica; hongbo zhang; osp<br> <b>Subject:</b> Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates</span></p>
</div><p class="MsoNormal">Â </p><p class="MsoNormal" style="margin-bottom: 12pt;">I'm pretty sure it's importing the 2nd file...if I change the url, I get an error that it can't find the file to import... <br>
My 2nd file is dirt simple...a passthrough stylesheet...just to test.<br> <br> Sean Keesler<br> 130 Academy Street<br> Manlius, New York 13104 USA<br> 315-663-7756<br> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=4" target="_top" rel="nofollow">sean.keesler@...</a><br>
<br> </p> <div><p class="MsoNormal">On Fri, Nov 20, 2009 at 11:56 AM, Maurer, Christopher Wayne <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=5" target="_top" rel="nofollow">chmaurer@...</a>> wrote:</p> <div><p class="MsoNormal">The only difference I see is that Sean's import uses a full url to the xsl file while Erica's is just a path to a content resource.</p>
<div><p class="MsoNormal">Â </p> </div> <div><p class="MsoNormal">Not sure if that makes a difference or not, but worth noting!</p> </div> <div><p class="MsoNormal">Â </p> </div> <div><p class="MsoNormal">Chris</p> </div> <div>
<p class="MsoNormal">Â </p> <div> <div> <div> <div><p class="MsoNormal">On Nov 20, 2009, at 11:34 AM, Ackerman, Erica wrote:</p> </div><p class="MsoNormal">Â </p> </div> </div> <blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<div> <div> <div> <div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Sean,</span></p> </div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p>
</div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.</span></p> </div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p>
</div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">For example:</span></p> </div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p> </div>
<div><p class="MsoNormal" style="margin-bottom: 12pt;"><span style="color: rgb(0, 100, 200);"><xsl:stylesheet</span><span style="color: rgb(245, 132, 76);">Â version</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"1.0"</span><span style="color: rgb(245, 132, 76);">Â xmlns</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"<a href="http://www.w3.org/1999/xhtml" target="_blank" rel="nofollow">http://www.w3.org/1999/xhtml</a>"</span><span style="color: rgb(245, 132, 76);">Â xmlns:sakaifn</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"org.sakaiproject.metaobj.utils.xml.XsltFunctions"</span><span style="color: rgb(245, 132, 76);">Â xmlns:xsl</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"<a href="http://www.w3.org/1999/XSL/Transform" target="_blank" rel="nofollow">http://www.w3.org/1999/XSL/Transform</a>"</span><span style="color: rgb(245, 132, 76);">xmlns:xhtml</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"<a href="http://www.w3.org/1999/xhtml" target="_blank" rel="nofollow">http://www.w3.org/1999/xhtml</a>"</span><span style="color: rgb(245, 132, 76);">Â xmlns:osp</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"<a href="http://www.osportfolio.org/OspML" target="_blank" rel="nofollow">http://www.osportfolio.org/OspML</a>"</span><span style="color: rgb(245, 132, 76);">Â xmlns:xs</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"<a href="http://www.w3.org/2001/XMLSchema" target="_blank" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"</span><span style="color: rgb(0, 0, 150);">></span><span style="color: black;"><br>
    </span><span style="color: rgb(0, 100, 200);"><xsl:output</span><span style="color: rgb(245, 132, 76);"> method</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"html"</span><span style="color: rgb(245, 132, 76);"> doctype-system</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"<a href="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" target="_blank" rel="nofollow">http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd</a>"</span><span style="color: rgb(245, 132, 76);"> doctype-public</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"-//W3C//DTD XHTML 1.0 Transitional//EN"</span><span style="color: rgb(0, 0, 150);">/></span><span style="color: black;"><br>
    </span><span style="color: rgb(0, 100, 200);"><xsl:import</span><span style="color: rgb(245, 132, 76);"> href</span><span style="color: rgb(255, 128, 64);">=</span><span style="color: rgb(153, 51, 0);">"/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl"</span><span style="color: rgb(245, 132, 76);"> </span><span style="color: rgb(0, 0, 150);">/></span></p>
</div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Could there be something wrong with the imported file?</span></p> </div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p>
</div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Erica</span></p> </div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p> </div> <div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<div><p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=6" target="_top" rel="nofollow">portfolio-bounces@...</a> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=7" target="_top" rel="nofollow">portfolio-bounces@...</a>] <b>On Behalf Of </b>Sean Keesler<br>
<b>Sent:</b>Â Friday, November 20, 2009 10:33 AM<br> <b>To:</b>Â hongbo zhang<br> <b>Cc:</b>Â osp<br> <b>Subject:</b>Â Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates</span></p> </div>
</div> <div><p class="MsoNormal">Â </p> </div><p class="MsoNormal" style="margin-bottom: 12pt;">I wonder if this is a 2.6-only issue.<br> Have you tried your template in a 2.6 instance?<br> <br> Sean Keesler<br> 130 Academy Street<br>
Manlius, New York 13104 USA<br> 315-663-7756<br> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=8" target="_top" rel="nofollow">sean.keesler@...</a></p> <div> <div><p class="MsoNormal">On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=9" target="_top" rel="nofollow">hbzhang@...</a>> wrote:</p>
</div> <div> <div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">I just tried using xsl:include. It works great.</span></p> </div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p>
</div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">I attached the sample file.</span></p> </div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p>
</div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it </span><span style="color: black;">          <xsl:call-template</span><span style="color: rgb(51, 51, 51);"> name</span><span style="color: rgb(0, 102, 102);">=</span><span style="color: black;">"Tab1instruction"></xsl:call-template> at line 743.</span></p>
</div> <div><p class="MsoNormal"><span style="color: black;">Â </span></p> </div> <div><p class="MsoNormal"><span style="color: black;">It seems it works fine for me. We run 2.5.4 instance.</span></p> </div> <div><p class="MsoNormal">
<span style="color: black;">Â </span></p> </div> <div><p class="MsoNormal"><span style="color: black;">Hongbo</span></p> </div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p>
</div> <div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Â </span></p> </div> <div style="border-style: solid none none; border-color: windowtext -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<div><p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=10" target="_top" rel="nofollow">portfolio-bounces@...</a> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=11" target="_top" rel="nofollow">portfolio-bounces@...</a>] <b>On Behalf Of </b>Sean Keesler<br>
<b>Sent:</b>Â Thursday, November 19, 2009 3:10 PM<br> <b>To:</b>Â osp<br> <b>Subject:</b>Â [Portfolio] 503 for DTD request in templated portfolios that import other templates</span></p> </div> </div> <div> <div> <div><p class="MsoNormal">
 </p> </div><p class="MsoNormal" style="margin-bottom: 12pt;">Has anyone developed a portfolio template using an xsl file that imports other xsl files?<br> Like this:</p> <div style="margin-left: 24pt;"> <div><p class="MsoNormal">
<?xml version="1.0" encoding="UTF-8"?>Â <br> <xsl:stylesheet xmlns:xsl="<a href="http://www.w3.org/1999/XSL/Transform" target="_blank" rel="nofollow">http://www.w3.org/1999/XSL/Transform</a>" version="1.0">Â <br>
<br> <!-- this needs to be any publicly accessible xsl file -->Â <br> <xsl:import href="<a href="http://yourserver.edu/path/to/your/imported.xsl" target="_blank" rel="nofollow">http://yourserver.edu/path/to/your/imported.xsl</a>"/>Â <br>
<br> Â Â <xsl:template match="/">Â <br> Â Â Â Â <xsl:text>Hey there!</xsl:text>Â <br> Â Â </xsl:template>Â <br> <br> </xsl:stylesheet></p> </div> </div> <div><p class="MsoNormal"><br> <br>
When I do, I get a 503 error in the logs related to DTD issues.<br> <br> I wrote it up as <a href="http://jira.sakaiproject.org/browse/SAK-17423" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-17423</a>.<br> It seems like it is similar to the stack trace that was occurring in free form portfolios in <a href="http://jira.sakaiproject.org/browse/SAK-16536" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-16536</a>.<br>
<br> This is 2-6-x branch r69087.<br> <br> <br> Sean Keesler<br> 130 Academy Street<br> Manlius, New York 13104 USA<br> 315-663-7756<br> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=12" target="_top" rel="nofollow">sean.keesler@...</a></p>
</div> </div> </div> </div> </div> </div> <div><p class="MsoNormal">Â </p> </div> </div> </div> </div><p class="MsoNormal"><span style="font-size: 13.5pt;">_______________________________________________<br> portfolio mailing list<br>
<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=13" target="_top" rel="nofollow">portfolio@...</a><br> <a href="http://collab.sakaiproject.org/mailman/listinfo/portfolio" target="_blank" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/portfolio</a><br>
<br> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=14" target="_top" rel="nofollow">portfolio-unsubscribe@...</a> with a subject of "unsubscribe"</span></p> </div>
</blockquote> </div><p class="MsoNormal">Â </p> </div> </div> </div><p class="MsoNormal">Â </p> </div> </div></div><span><test.JPG></span><span><portfoliotemplate.xsl></span><div class="im"><div style="margin: 0px;">
_______________________________________________</div><div style="margin: 0px;">portfolio mailing list</div><div style="margin: 0px;"><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=15" target="_top" rel="nofollow">portfolio@...</a></div>
<div style="margin: 0px;"><a href="http://collab.sakaiproject.org/mailman/listinfo/portfolio" target="_blank" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/portfolio</a></div><div style="margin: 0px; min-height: 14px;">
<br></div><div style="margin: 0px;">TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=16" target="_top" rel="nofollow">portfolio-unsubscribe@...</a> with a subject of "unsubscribe"</div>
</div></blockquote></div><br></div></div></div></div></blockquote></div><br>
<br />_______________________________________________
<br>portfolio mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=17" target="_top" rel="nofollow">portfolio@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/portfolio" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/portfolio</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457406&i=18" target="_top" rel="nofollow">portfolio-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Portfolio-f18155.html" embed="fixTarget[18155]" target="_top" >Sakai - Portfolio</a></p>tag:old.nabble.com,2006:post-26453295Re: [Building Sakai] Master pom: removing myfaces.zones.apache.org repo reference2009-11-20T18:48:32Z2009-11-20T18:48:32ZRay DavisIn my brisk search earlier today, I didn't spot a recent reference for
<br>non-myfaces parties so, with the scant attention given JSF by Sakai
<br>developers nowadays, I hope the official Apache repos should suffice.
<br>(There was at least one transitional period in 2006 when "myfaces.zones"
<br>was the place to pick up a recently released JAR.)
<br><br>Best,
<br>Ray
<br><br>On 11/20/09 6:16 PM, Steve Swinsburg wrote:
<div class='shrinkable-quote'><br>> +1.
<br>>
<br>> Does anyone know if it's coming back?
<br>>
<br>> cheers,
<br>> Steve
<br>>
<br>>
<br>> On 21/11/2009, at 8:52 AM, Speelmon, Lance Day wrote:
<br>>
<br>>> +1
<br>>> *
<br>>>
<br>>> *
<br>>> *Lance Speelmon*
<br>>> Scholarly Technologist
<br>>>
<br>>> On Nov 20, 2009, at 4:25 PM, Anthony Whyte wrote:
<br>>>
<br>>>> Any objection to commenting out/removing the myfaces.zones.apache.org
<br>>>> <<a href="http://myfaces.zones.apache.org/" target="_top" rel="nofollow">http://myfaces.zones.apache.org/</a>> repo reference in the master pom?
<br>>>> I checked the Apache network and it's nowhere to be seen. Excluding
<br>>>> it should speed up the builds a wee bit.
<br>>>>
<br>>>> Cheers,
<br>>>>
<br>>>> Anth
<br>>>>
<br>>>> <repository>
<br>>>> <id>apache-repo</id>
<br>>>> <name>apache-repo</name>
<br>>>> <layout>default</layout>
<br>>>>
<br>>>> <url><a href="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</a></url>
<br>>>> <snapshots>
<br>>>> <enabled>false</enabled>
<br>>>> </snapshots>
<br>>>> </repository>
<br>>>>
<br>>>>
<br>>>> Forbidden
<br>>>>
<br>>>> You don't have permission to access /dist/maven-repository on this
<br>>>> server.
<br>>>>
<br>>>> Additionally, a 403 Forbidden error was encountered while trying to
<br>>>> use an ErrorDocument to handle the request.
<br>>>>
<br>>>> ------------------------------------------------------------------------
<br>>>> Apache/2.0.63 (Unix) DAV/2 Server at myfaces.zones.apache.org
<br>>>> <<a href="http://myfaces.zones.apache.org/" target="_top" rel="nofollow">http://myfaces.zones.apache.org/</a>> Port 80
<br>>>>
<br>>>>
<br>>>> Begin forwarded message:
<br>>>>
<br>>>>> *From: *Seth Theriault <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=0" target="_top" rel="nofollow">slt@...</a> <mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=1" target="_top" rel="nofollow">slt@...</a>>>
<br>>>>> *Date: *November 19, 2009 2:00:16 AM GMT-05:00
<br>>>>> *To: *Anthony Whyte <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=2" target="_top" rel="nofollow">arwhyte@...</a> <mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=3" target="_top" rel="nofollow">arwhyte@...</a>>>
<br>>>>> *Cc: *Speelman Lance <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=4" target="_top" rel="nofollow">lance@...</a> <mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=5" target="_top" rel="nofollow">lance@...</a>>>,
<br>>>>> Maurer Christopher <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=6" target="_top" rel="nofollow">chmaurer@...</a> <mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=7" target="_top" rel="nofollow">chmaurer@...</a>>>,
<br>>>>> Horwitz David <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=8" target="_top" rel="nofollow">david.horwitz@...</a> <mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=9" target="_top" rel="nofollow">david.horwitz@...</a>>>
<br>>>>> *Subject: **Re: Apache infrastructure machine status*
<br>>>>>
<br>>>>> Anthony Whyte wrote:
<br>>>>>
<br>>>>>> Nothing I see in the Apache network that sheds any light on the status
<br>>>>>> <a href="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</a><br>>>>>
<br>>>>> I think this repo is dead or out of date.
<br>>>>>
<br>>>>> Looking at:
<br>>>>>
<br>>>>> <a href="http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven" target="_top" rel="nofollow">http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven</a><br>>>>>
<br>>>>> I think the libs are served out of the central maven2 repos
<br>>>>> now.
<br>>>>>
<br>>>>> Seth
<br>>>>>
<br>>>>>
<br>>>>
<br>>>> _______________________________________________
<br>>>> sakai-dev mailing list
<br>>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=10" target="_top" rel="nofollow">sakai-dev@...</a>
<br>>>> <mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=11" target="_top" rel="nofollow">sakai-dev@...</a>>
<br>>>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>>>>
<br>>>> TO UNSUBSCRIBE: send email to
<br>>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=12" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of
<br>>>> "unsubscribe"
<br>>>
<br>>> _______________________________________________
<br>>> sakai-dev mailing list
<br>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=13" target="_top" rel="nofollow">sakai-dev@...</a>
<br>>> <mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=14" target="_top" rel="nofollow">sakai-dev@...</a>>
<br>>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>>>
<br>>> TO UNSUBSCRIBE: send email to
<br>>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=15" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of
<br>>> "unsubscribe"
<br>>
<br>>
<br>> ------------------------------------------------------------------------
<br>>
<br>> _______________________________________________
<br>> sakai-dev mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=16" target="_top" rel="nofollow">sakai-dev@...</a>
<br>> <a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br>>
<br>> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=17" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
</div><br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=18" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453295&i=19" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26453117Re: [Building Sakai] Master pom: removing myfaces.zones.apache.org repo reference2009-11-20T18:16:30Z2009-11-20T18:16:30ZSteve Swinsburg-3<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">+1. <div><br></div><div>Does anyone know if it's coming back?</div><div><br></div><div>cheers,</div><div>Steve<br><div><br></div><div><br><div><div>On 21/11/2009, at 8:52 AM, Speelmon, Lance Day wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">+1<br><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: 'Lucida Grande'; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Lucida Grande'; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><b style="font-weight: bold; "><br class="Apple-interchange-newline"><br class="khtml-block-placeholder"></b></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><b style="font-weight: bold; "><span class="Apple-style-span" style="font-weight: bold; "><span class="Apple-style-span" style="font-weight: bold; "><span class="Apple-style-span" style="font-weight: bold; ">Lance Speelmon</span></span></span></b></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 11px; ">Scholarly Technologist</span></font></div></span></div></span></div></span></div></span></div></span></span>
</div>
<br><div><div>On Nov 20, 2009, at 4:25 PM, Anthony Whyte wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Any objection to commenting out/removing the <a href="http://myfaces.zones.apache.org/" target="_top" rel="nofollow">myfaces.zones.apache.org</a> repo reference in the master pom? I checked the Apache network and it's nowhere to be seen. Excluding it should speed up the builds a wee bit.<div><br></div><div>Cheers,</div><div><br></div><div>Anth<br><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; color: rgb(63, 127, 127); "><span style="color: #008080"><</span>repository<span style="color: #008080">></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "> <span style="color: #008080"><</span><span style="color: #3f7f7f">id</span><span style="color: #008080">></span>apache-repo<span style="color: #008080"></</span><span style="color: #3f7f7f">id</span><span style="color: #008080">></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "> <span style="color: #008080"><</span><span style="color: #3f7f7f">name</span><span style="color: #008080">></span>apache-repo<span style="color: #008080"></</span><span style="color: #3f7f7f">name</span><span style="color: #008080">></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "> <span style="color: #008080"><</span><span style="color: #3f7f7f">layout</span><span style="color: #008080">></span>default<span style="color: #008080"></</span><span style="color: #3f7f7f">layout</span><span style="color: #008080">></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "> <span style="color: #008080"><</span><span style="color: #3f7f7f">url</span><span style="color: #008080">></span><a href="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</a><span style="color: #008080"></</span><span style="color: #3f7f7f">url</span><span style="color: #008080">></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "> <span style="color: #008080"><</span><span style="color: #3f7f7f">snapshots</span><span style="color: #008080">></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "> <span style="color: #008080"><</span><span style="color: #3f7f7f">enabled</span><span style="color: #008080">></span>false<span style="color: #008080"></</span><span style="color: #3f7f7f">enabled</span><span style="color: #008080">></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "> <span style="color: #008080"></</span><span style="color: #3f7f7f">snapshots</span><span style="color: #008080">></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; color: rgb(63, 127, 127); "><span style="color: #000000"> </span><span style="color: #008080"></</span>repository<span style="color: #008080">></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; color: rgb(63, 127, 127); "><font class="Apple-style-span" color="#008080"><br></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; color: rgb(63, 127, 127); "><font class="Apple-style-span" color="#008080"><h1>Forbidden</h1><p>You don't have permission to access /dist/maven-repository
on this server.</p><p>Additionally, a 403 Forbidden
error was encountered while trying to use an ErrorDocument to handle the request.</p>
<hr>
<address>Apache/2.0.63 (Unix) DAV/2 Server at <a href="http://myfaces.zones.apache.org/" target="_top" rel="nofollow">myfaces.zones.apache.org</a> Port 80</address></font></div><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>From: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Seth Theriault <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=0" target="_top" rel="nofollow">slt@...</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Date: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">November 19, 2009 2:00:16 AM GMT-05:00</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>To: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Anthony Whyte <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=1" target="_top" rel="nofollow">arwhyte@...</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Cc: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Speelman Lance <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=2" target="_top" rel="nofollow">lance@...</a>>, Maurer Christopher <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=3" target="_top" rel="nofollow">chmaurer@...</a>>, Horwitz David <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=4" target="_top" rel="nofollow">david.horwitz@...</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Subject: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica"><b>Re: Apache infrastructure machine status</b></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div> </div><div>Anthony Whyte wrote:<br><br><blockquote type="cite">Nothing I see in the Apache network that sheds any light on the status<br></blockquote><blockquote type="cite"><a href="http://myfaces.zones.apache.org/dist/maven-repository" target="_top" rel="nofollow">http://myfaces.zones.apache.org/dist/maven-repository</a><br></blockquote><br>I think this repo is dead or out of date.<br><br>Looking at:<br><br><a href="http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven" target="_top" rel="nofollow">http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven</a><br><br>I think the libs are served out of the central maven2 repos <br>now.<br><br>Seth<br><br><br></div></blockquote></div><br></div></div></div>_______________________________________________<br>sakai-dev mailing list<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=5" target="_top" rel="nofollow">sakai-dev@...</a><br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=6" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"</blockquote></div><br></div>_______________________________________________<br>sakai-dev mailing list<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=7" target="_top" rel="nofollow">sakai-dev@...</a><br>http://collab.sakaiproject.org/mailman/listinfo/sakai-dev<br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=8" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"</blockquote></div><br></div></div></body></html><br /> <br />_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=9" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26453117&i=10" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"<div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (5K) <a href="http://old.nabble.com/attachment/26453117/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>tag:old.nabble.com,2006:post-26452204Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates2009-11-20T15:58:36Z2009-11-20T15:58:36ZNoah Botimer<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
In general, the Content Hosting URI resolver should be in place when these XSLs execute. That means that an import on something like '/group/PortfolioAdmin/...xsl' should be valid. This also insulates your XSL from instance/hostname changes and so on. You will want to make sure that anything included/imported is public in Resources.<div><br></div><div>The tricky bit here is that XSL includes and so on that are not fully qualified URLs are not evaluated the same as they would by a browser. They are resolved locally, which, if the CHS glue isn't in place, will be somewhere deep in the app server (essentially useless). If we find that this is the case anywhere, we should fix it.</div><div><br></div><div>Note that this means '/access/content/group/PortfolioAdmin' is incorrect for things like include/import. It is, however, correct for referencing accessible items that the browser would hit (script, images, or stylesheets). There is a different construction for "additional materials" attached to a template, where you would typically pass the path from the XML to sakaifn:getReferenceUrl. (You can also pass your items like script URLs to getReferenceUrl if you remove /access/content.)</div><div><br></div><div>I cannot speak to the http/https behavior or the DTD 503s aside from that we should make sure that the local catalog is registered everywhere as in <a href="http://jira.sakaiproject.org/browse/SAK-16536" target="_top" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-16536</a>. Along with local, internal references to your supplemental materials, this should make sure that your server isn't attempting external requests for what it needs.</div><div><div><br></div><div>Thanks,</div><div>-Noah<br><div><br><div><div>On Nov 20, 2009, at 4:16 PM, hongbo zhang wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <div class="Section1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D">I just tested it with the localhost 2.6.0 instance.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D">If I write <o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:darkgreen"><xsl:include href="<a href="http://localhost:8080/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl" target="_top" rel="nofollow">http://localhost:8080/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl</a>"/><o:p></o:p></span></p><p class="MsoNormal"><span style="color:darkgreen"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:darkgreen">It does not work. It complains the stylesheet can not be complied. <o:p></o:p></span></p><p class="MsoNormal"><span style="color:darkgreen"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:darkgreen">However if I use <o:p></o:p></span></p><p class="MsoNormal"><span style="color:darkgreen"><o:p> </o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="color:black"><xsl:include</span><span style="color:#333333"> href</span><span style="color:#006666">=</span><span style="color:black">"<a href="https://scholar.vt.edu/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl" target="_top" rel="nofollow">https://scholar.vt.edu/access/content/group/PortfolioAdmin/authoring/themeEPATVT/xsl/editingpagehelp.xsl</a>"/> <o:p></o:p></span></p><p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p><p class="MsoNormal"><span style="color:black">It works. <o:p></o:p></span></p><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:black">I attached the worked screen shot as well as the template file for the 2.6.0 test. The texts on the front page comes from a template in another xsl file. <o:p></o:p></span></p><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:black">However, interestingly, both localhost and permanent URL methods work for 2.5.3 instance. <o:p></o:p></span></p><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:black">I guess, the permanent URL is important for 2.6. The URL should not be in the localhost. It should be a good workable URL. Many times, we use localhost for development, which might give some trouble.<o:p></o:p></span></p><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:black">Just a thought.<o:p></o:p></span></p><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:black">Hongbo<o:p></o:p></span></p><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"><o:p> </o:p></span></p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=0" target="_top" rel="nofollow">sean@...</a> [<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=1" target="_top" rel="nofollow">sean@...</a>] <b>On Behalf Of </b>Sean Keesler<br> <b>Sent:</b> Friday, November 20, 2009 12:35 PM<br> <b>To:</b> Maurer, Christopher Wayne<br> <b>Cc:</b> Ackerman, Erica; hongbo zhang; osp<br> <b>Subject:</b> Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates<o:p></o:p></span></p> </div><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal" style="margin-bottom:12.0pt">I'm pretty sure it's importing the 2nd file...if I change the url, I get an error that it can't find the file to import... <br> My 2nd file is dirt simple...a passthrough stylesheet...just to test.<br> <br> Sean Keesler<br> 130 Academy Street<br> Manlius, New York 13104 USA<br> 315-663-7756<br> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=2" target="_top" rel="nofollow">sean.keesler@...</a><br> <br> <o:p></o:p></p> <div><p class="MsoNormal">On Fri, Nov 20, 2009 at 11:56 AM, Maurer, Christopher Wayne <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=3" target="_top" rel="nofollow">chmaurer@...</a>> wrote:<o:p></o:p></p> <div><p class="MsoNormal">The only difference I see is that Sean's import uses a full url to the xsl file while Erica's is just a path to a content resource.<o:p></o:p></p> <div><p class="MsoNormal"><o:p> </o:p></p> </div> <div><p class="MsoNormal">Not sure if that makes a difference or not, but worth noting!<o:p></o:p></p> </div> <div><p class="MsoNormal"><o:p> </o:p></p> </div> <div><p class="MsoNormal">Chris<o:p></o:p></p> </div> <div><p class="MsoNormal"> <o:p></o:p></p> <div> <div> <div> <div><p class="MsoNormal">On Nov 20, 2009, at 11:34 AM, Ackerman, Erica wrote:<o:p></o:p></p> </div><p class="MsoNormal"><o:p> </o:p></p> </div> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <div> <div> <div> <div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D">Sean,</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"> </span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D">We use xsl:import in the Page Composer, and it works in 2.6 and 2.5 both.</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"> </span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D">For example:</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"> </span><o:p></o:p></p> </div> <div><p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:#0064C8"><xsl:stylesheet</span><span style="color:#F5844C"> version</span><span style="color:#FF8040">=</span><span style="color:#993300">"1.0"</span><span style="color:#F5844C"> xmlns</span><span style="color:#FF8040">=</span><span style="color:#993300">"<a href="http://www.w3.org/1999/xhtml" target="_blank" rel="nofollow">http://www.w3.org/1999/xhtml</a>"</span><span style="color:#F5844C"> xmlns:sakaifn</span><span style="color:#FF8040">=</span><span style="color:#993300">"org.sakaiproject.metaobj.utils.xml.XsltFunctions"</span><span style="color:#F5844C"> xmlns:xsl</span><span style="color:#FF8040">=</span><span style="color:#993300">"<a href="http://www.w3.org/1999/XSL/Transform" target="_blank" rel="nofollow">http://www.w3.org/1999/XSL/Transform</a>"</span><span style="color:#F5844C">xmlns:xhtml</span><span style="color:#FF8040">=</span><span style="color:#993300">"<a href="http://www.w3.org/1999/xhtml" target="_blank" rel="nofollow">http://www.w3.org/1999/xhtml</a>"</span><span style="color:#F5844C"> xmlns:osp</span><span style="color:#FF8040">=</span><span style="color:#993300">"<a href="http://www.osportfolio.org/OspML" target="_blank" rel="nofollow">http://www.osportfolio.org/OspML</a>"</span><span style="color:#F5844C"> xmlns:xs</span><span style="color:#FF8040">=</span><span style="color:#993300">"<a href="http://www.w3.org/2001/XMLSchema" target="_blank" rel="nofollow">http://www.w3.org/2001/XMLSchema</a>"</span><span style="color:#000096">></span><span style="color:black"><br> </span><span style="color:#0064C8"><xsl:output</span><span style="color:#F5844C"> method</span><span style="color:#FF8040">=</span><span style="color:#993300">"html"</span><span style="color:#F5844C"> doctype-system</span><span style="color:#FF8040">=</span><span style="color:#993300">"<a href="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" target="_blank" rel="nofollow">http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd</a>"</span><span style="color:#F5844C"> doctype-public</span><span style="color:#FF8040">=</span><span style="color:#993300">"-//W3C//DTD XHTML 1.0 Transitional//EN"</span><span style="color:#000096">/></span><span style="color:black"><br> </span><span style="color:#0064C8"><xsl:import</span><span style="color:#F5844C"> href</span><span style="color:#FF8040">=</span><span style="color:#993300">"/group/PortfolioAdmin/authoring/xsl/formCreate-wysiwyg.xsl"</span><span style="color:#F5844C"> </span><span style="color:#000096">/></span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D">Could there be something wrong with the imported file?</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"> </span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D">Erica</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"> </span><o:p></o:p></p> </div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"> <div><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=4" target="_top" rel="nofollow">portfolio-bounces@...</a> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=5" target="_top" rel="nofollow">portfolio-bounces@...</a>] <b>On Behalf Of </b>Sean Keesler<br> <b>Sent:</b> Friday, November 20, 2009 10:33 AM<br> <b>To:</b> hongbo zhang<br> <b>Cc:</b> osp<br> <b>Subject:</b> Re: [Portfolio] 503 for DTD request in templated portfolios that import other templates</span><o:p></o:p></p> </div> </div> <div><p class="MsoNormal"> <o:p></o:p></p> </div><p class="MsoNormal" style="margin-bottom:12.0pt">I wonder if this is a 2.6-only issue.<br> Have you tried your template in a 2.6 instance?<br> <br> Sean Keesler<br> 130 Academy Street<br> Manlius, New York 13104 USA<br> 315-663-7756<br> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=6" target="_top" rel="nofollow">sean.keesler@...</a><o:p></o:p></p> <div> <div><p class="MsoNormal">On Thu, Nov 19, 2009 at 3:41 PM, hongbo zhang <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=7" target="_top" rel="nofollow">hbzhang@...</a>> wrote:<o:p></o:p></p> </div> <div> <div> <div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I just tried using xsl:include. It works great.</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I attached the sample file.</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">This is the template xsl file used in single form template. I include another xsl file, which has several templates. I just try to call it </span><span style="color:black"> <xsl:call-template</span><span style="color:#333333"> name</span><span style="color:#006666">=</span><span style="color:black">"Tab1instruction"></xsl:call-template> at line 743.</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="color:black">It seems it works fine for me. We run 2.5.4 instance.</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="color:black">Hongbo</span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p> </div> <div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p> </div> <div style="border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in"> <div><p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=8" target="_top" rel="nofollow">portfolio-bounces@...</a> [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=9" target="_top" rel="nofollow">portfolio-bounces@...</a>] <b>On Behalf Of </b>Sean Keesler<br> <b>Sent:</b> Thursday, November 19, 2009 3:10 PM<br> <b>To:</b> osp<br> <b>Subject:</b> [Portfolio] 503 for DTD request in templated portfolios that import other templates</span><o:p></o:p></p> </div> </div> <div> <div> <div><p class="MsoNormal"> <o:p></o:p></p> </div><p class="MsoNormal" style="margin-bottom:12.0pt">Has anyone developed a portfolio template using an xsl file that imports other xsl files?<br> Like this:<o:p></o:p></p> <div style="margin-left:24.0pt"> <div><p class="MsoNormal"><?xml version="1.0" encoding="UTF-8"?> <br> <xsl:stylesheet xmlns:xsl="<a href="http://www.w3.org/1999/XSL/Transform" target="_blank" rel="nofollow">http://www.w3.org/1999/XSL/Transform</a>" version="1.0"> <br> <br> <!-- this needs to be any publicly accessible xsl file --> <br> <xsl:import href="<a href="http://yourserver.edu/path/to/your/imported.xsl" target="_blank" rel="nofollow">http://yourserver.edu/path/to/your/imported.xsl</a>"/> <br> <br> <xsl:template match="/"> <br> <xsl:text>Hey there!</xsl:text> <br> </xsl:template> <br> <br> </xsl:stylesheet><o:p></o:p></p> </div> </div> <div><p class="MsoNormal"><br> <br> When I do, I get a 503 error in the logs related to DTD issues.<br> <br> I wrote it up as <a href="http://jira.sakaiproject.org/browse/SAK-17423" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-17423</a>.<br> It seems like it is similar to the stack trace that was occurring in free form portfolios in <a href="http://jira.sakaiproject.org/browse/SAK-16536" target="_blank" rel="nofollow">http://jira.sakaiproject.org/browse/SAK-16536</a>.<br> <br> This is 2-6-x branch r69087.<br> <br> <br> Sean Keesler<br> 130 Academy Street<br> Manlius, New York 13104 USA<br> 315-663-7756<br> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=10" target="_top" rel="nofollow">sean.keesler@...</a><o:p></o:p></p> </div> </div> </div> </div> </div> </div> <div><p class="MsoNormal"> <o:p></o:p></p> </div> </div> </div> </div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">_______________________________________________<br> portfolio mailing list<br> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=11" target="_top" rel="nofollow">portfolio@...</a><br> <a href="http://collab.sakaiproject.org/mailman/listinfo/portfolio" target="_blank" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/portfolio</a><br> <br> TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=12" target="_top" rel="nofollow">portfolio-unsubscribe@...</a> with a subject of "unsubscribe"<o:p></o:p></span></p> </div> </blockquote> </div><p class="MsoNormal"><o:p> </o:p></p> </div> </div> </div><p class="MsoNormal"><o:p> </o:p></p> </div> <span><test.JPG></span><span><portfoliotemplate.xsl></span><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">portfolio mailing list</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=13" target="_top" rel="nofollow">portfolio@...</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://collab.sakaiproject.org/mailman/listinfo/portfolio" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/portfolio</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=14" target="_top" rel="nofollow">portfolio-unsubscribe@...</a> with a subject of "unsubscribe"</div> </blockquote></div><br></div></div></div></body></html><br />_______________________________________________
<br>portfolio mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=15" target="_top" rel="nofollow">portfolio@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/portfolio" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/portfolio</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26452204&i=16" target="_top" rel="nofollow">portfolio-unsubscribe@...</a> with a subject of "unsubscribe"<p>From forum: <a href="http://old.nabble.com/Sakai---Portfolio-f18155.html" embed="fixTarget[18155]" target="_top" >Sakai - Portfolio</a></p>tag:old.nabble.com,2006:post-26451217[Building Sakai] Trunk: 2.8-SNAPSHOT pom update (Sunday, 22 Nov. 2009)2009-11-20T14:23:45Z2009-11-20T14:23:45ZAnthony WhyteWith the creation of the 2.7.x branch it is time to update all trunk
<br>poms to version 2.8-SNAPSHOT. I plan to perform this update over the
<br>weekend.
<br><br>EXCEPTIONS
<br><br>Indie trunk project poms will not be affected by this update.
<br>Incrementing their versions will be handled on a project-by-project
<br>basis when required. Projects include:
<br><br>common
<br>edu-services
<br>emailtemplateservice
<br>entitybroker
<br>jsf
<br>msgcntr
<br>polls
<br>samigo
<br>search
<br><br>Experimental (-Pexperimental)
<br><br>basicLTI
<br>Profile2
<br>SiteStats
<br>tinyurlservice
<br><br>Note: in case you are wondering the above Indie projects build and
<br>deploy properly to Tomcat.
<br><br>TRUNK DEVELOPER IMPACT
<br><br>1. Perform an svn update.
<br><br>2. Confirm you are running Maven 2.0.10 (at a minimum)
<br><br>mvn -- version
<br><br>3. If not get it here:
<br><br><a href="http://maven.apache.org/download.html" target="_top" rel="nofollow">http://maven.apache.org/download.html</a><br><br>4. Install to populate your local .m2 repo with 2.8-SNAPHSHOT artifacts
<br><br>mvn clean install
<br><br>5. Deploy to Tomcat (a clean Tomcat of course)
<br><br>mvn clean install sakai:deploy
<br>or
<br>mvn -Pexperimental clean install sakai:deploy
<br><br>____________________
<br><br>My localhost footer:
<br><br>Copyright 2003-2008 The Sakai Foundation. All rights reserved.
<br>Portions of Sakai are copyrighted by other parties as described in the
<br>Acknowledgments screen.
<br>LocalSakaiName - TRUNK - Sakai 2.8.0 - Server localhost
<br><br>Cheers,
<br><br>Anth
<br>_______________________________________________
<br>sakai-dev mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26451217&i=0" target="_top" rel="nofollow">sakai-dev@...</a>
<br><a href="http://collab.sakaiproject.org/mailman/listinfo/sakai-dev" target="_top" rel="nofollow">http://collab.sakaiproject.org/mailman/listinfo/sakai-dev</a><br><br>TO UNSUBSCRIBE: send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26451217&i=1" target="_top" rel="nofollow">sakai-dev-unsubscribe@...</a> with a subject of "unsubscribe"
<br><p>From forum: <a href="http://old.nabble.com/Sakai---Development-f18040.html" embed="fixTarget[18040]" target="_top" >Sakai - Development</a></p>