gmane.comp.cms.sakai.devel

Re: Public entries

Aaron Zeckoski — 2008-11-22T12:52:06

A few of the contrib tools have actual public access for certain data with no logins required (blogwow, evaluations - like resources/access as mentioned) but in general "public" means a member of sakai and not a member of the specific site. I would agree that this is confusing and would be better termed as "authenticated" (vs. "anonymous"). -AZ On Fri, Nov 21, 2008 at 12:30 PM, Daniel Merino unavarra.es> wrote:

Re: Changing user type for external (JLDAP) users

John F. Hall — 2008-11-22T02:42:42

Thanks to both of you -- I'll see if the patch will work for us first. -John ========================================== John F. Hall IT Consultant III University of Delaware User Services ---- Original message ---- ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: Development (a.k.a. sakai-dev) site. You can modify how you receive notifications at My Workspace > Preferences.

Re: Eclipse Syncing

Zach A. Thomas — 2008-11-21T23:26:17

On Nov 21, 2008, at 12:42 PM, Steven Githens wrote: This fits the bill. It allows you to set up as many Eclipse profiles as you want and then launch those profiles from any machine. It will automatically download any software and/or configuration that isn't already available locally. You can share your profiles with others so everyone on a team can be working from the same Eclipse baseline. It's not free*, but it's cheap: http://www.poweredbypulse.com/ cheers, Zach * They do have something free of charge called "Community Edition," but it's so crippled as to be really nothing but baitware. ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: Development (a.k.a. sakai-dev) site. You can modify how you receive notifications at My Workspace > Preferences.

Re: Changing user type for external (JLDAP) users

Daniel McCallum — 2008-11-21T23:23:32

John, You might also be interested in the patch attached to this ticket: http://bugs.sakaiproject.org/jira/browse/SAK-14648 Robert is right that EntryAttributeToUserTypeMapper can be tricked into returning hard-coded attributes. SAK-14648 is just a more direct solution. Let me know if you still can't get it to work. I'm willing to have a look at your bean defs if that would help. - Dan Robert Taylor wrote: ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: Development (a.k.a. sakai-dev) site. You can modify how you receive notifications at My Workspace > Preferences.

Re: Changing user type for external (JLDAP) users

Robert Taylor — 2008-11-21T23:00:30

John, We ran into the same issue today with our new installation of Sakai. I found references to other people with same problem on the confluence sakai bug site, so it doesn't seem like an uncommon problem. We managed to hard code the default type to be "registered" by changing the jldap-beans.xml file to enable the edu.amc.sakai.user.EntryAttributeToUserTypeMapper (the default config in jldap-beans.xml is EmptyStringUserTypeMapper) Then we changed the bean definition as follows for the EntryAttributeTypeMapper to define the defaultSakaiUserType to be "registered" if the groupMembership attribute returns false (which it will every time because the attribute doesn't exist in our LDAP config): groupMembership false

Changing user type for external (JLDAP) users

John F. Hall — 2008-11-21T21:57:28

We're authenticating our users externally using the (modified) JLDAP user provider, which is working fine, but there seems to be no way for us to change the user types once an account has been created on initial login. Changing the LDAP attribute the user type is based on does not get picked by Sakai up for existing users, even after rebooting the Sakai server. The web admin interface also doesn't seem to have a way to do change the user type for external users. Is this a general issue, or specific to our implementation? Has anyone faced this and come up with a fix or workaround? Thanks, John (BTW, we're running Sakai 2.5.3, Oracle 10)

Re: Agora installation

Robert Long — 2008-11-21T21:04:28

Am, You need to download Wicket and build / deploy it. Wicket is in contrib: https://source.sakaiproject.org/contrib/wicket/sakai-wicket/branches/sakai_2-5-x/ --Bob --- Robert E. Long, MA Open Source Programmer / Analyst Mathematics Instructor M.A. Instructional Technology Saginaw Valley State University http://www.svsu.edu/~relong relong< at >svsu.edu office: 989.964.2245 I am trying to install agora with my sakai 2.5.2 and running in to the following issue: Missing: ------------- 1) org.sakaiproject:sakai-wicket:jar:M2 How do I resolve this? Thanks and regards Am Khan ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: Development (a.k.a. sakai-dev) site. You can modify how you receive notifications at My Workspace > Preferences.

Agora installation

Am Khan — 2008-11-21T20:54:55

I am trying to install agora with my sakai 2.5.2 and running in to the following issue: Missing: ------------- 1) org.sakaiproject:sakai-wicket:jar:M2 How do I resolve this? Thanks and regards Am Khan ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: Development (a.k.a. sakai-dev) site. You can modify how you receive notifications at My Workspace > Preferences.

Re: Crash with trunk version of Kernel

Beth Kirschner — 2008-11-21T14:43:08

Thanks for your time -- a clean install of tomcat and clean rebuild of sakai did the trick for me as well. - Beth On Nov 21, 2008, at 9:18 AM, Anthony Whyte wrote: ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: Development (a.k.a. sakai-dev) site. You can modify how you receive notifications at My Workspace > Preferences.

Re: Crash with trunk version of Kernel

Anthony Whyte — 2008-11-21T14:18:28

Sakai trunk/kernel trunk combo builds and starts for me in Tomcat and obligingly let me create a project site. I did the following steps: 1. Refreshed Tomcat 2. dropped/created new sakai db 3. svn update /kernel/trunk (r54542) 4. svn update /sakai/trunk 5. mvn clean install kernel 6. mvn clean install -Dmaven.test.skip=true -Dmaven.tomcat.home=true sakai:deploy 7. log in to Sakai, create a project site (with blogger, assignments, site info, home). Looking at catalina.out I find no unusual WARN messages beyond the usual suspects. I did find an RTE with the blogger but it's blogger- specific (will Jira it). Cheers, Anth On Nov 20, 2008, at 2:05 PM, Beth Kirschner wrote: [see attachment: "smime.p7s", size: 2417 bytes] Attachments: smime.p7s https://collab.sakaiproject.org//access/content/attachment/beda5441-d93e-4a97-be74-620928e08222/smime.p7s ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG:

RE: Public entries

Adam Marshall — 2008-11-21T13:10:23

Funnily enough we just had a chat about this issue. In Resources you can denote an item as being publicly visible, this means non-logged in users can see the item. This is the same for a public wiki page I think. To make a site visible to non-logged in users, ie, the general public you add the .anon role to your site (and set the permissions accordingly). But then when you create a site you are asked whether it should be shown in public listing you can say yes and that means the general public can see its there (via Find Sites) but they cant access it because its not actually public (doesnt necc. have the .anon role)! We think this is confusing. Adam _____ From: Daniel Merino [mailto:daniel.merino< at >unavarra.es] Sent: 21 November 2008 12:31 To: sakai-dev Subject: Public entries Hi, everybody. It seems that the "public" term in Sakai (in the blog, the wiki, etc) refers to all the validated users of Sakai, but not the rest of the world. Is this true? Is the

Public entries

Daniel Merino — 2008-11-21T12:30:37

Hi, everybody. It seems that the "public" term in Sakai (in the blog, the wiki, etc) refers to all the validated users of Sakai, but not the rest of the world. Is this true? Is there any way to make the public entries of these tools readables for non validated users? Thanks in advance.

Problem with FeedTool Installation

Juan Jesús Cremades Monserrat — 2008-11-21T11:55:26

Hi, I'm installing the FeedTool Add, but I'm obtainign this error: [INFO] Compiling 2 source files to /home/Sakai/desarrollo/feedtool/tool/m2-target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /home/Sakai/desarrollo/feedtool/tool/src/java/org/sakaiproject/feed/tool/entity/FeedEntityProvider.java:[15,7] org.sakaiproject.feed.tool.entity.FeedEntityProvider is not abstract and does not override abstract method createEntity(org.sakaiproject.entitybroker.EntityReference,java.lang.Object,java.util.Map) in org.sakaiproject.entitybroker.entityprovider.capabilities.Createable /home/Sakai/desarrollo/feedtool/tool/src/java/org/sakaiproject/feed/tool/entity/FeedEntityProvider.java:[15,7] org.sakaiproject.feed.tool.entity.FeedEntityProvider is not abstract and does not override abstract method createEntity(org.

Agora client error with sakai

Soumya_Ranjan — 2008-11-21T08:10:01

Hi, Can u please post the same in agora forums along with files attached I have integrated agora with Sakai2-5-x. I am also able to access agora-client on the server when I click on test meeting. But when I try to do the same from a client machine(all the 5 UDP and TCP ports are enabled), I get a null pointer exception telling 'Unable to launch Agora'. Plz help... Please find the exception and launch file details attached Thanks!!! Regards, Soumya Ranjan Das |HCU-JAVA| |BHR-Bangalore|India| |mob:+91-9739847784| |Email:soumya_ranjan< at >satyam.com| [cid:image001.jpg< at >01C94BDE.A714F040] "Business Transformation Together" P Please do not print this email unless it is absolutely necessary. Save the trees, spread the greenery!! ________________________________ DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwar

Re: Requesting information about Linktool

Stephen Marquard — 2008-11-21T06:37:33

Hi, Have a look at: https://source.sakaiproject.org/svn/linktool/branches/sakai_2-5-x/linktool.txt for further documentation about the LinkTool. You're getting a SOAP error in the callback because your serverUrl is set to localhost, so the remote linktool application cannot contact your Sakai instance to verify the parameters passed to it. Make sure you have serverName and serverUrl set in your sakai.properties, e.g. serverName = qa1-za.sakaiproject.org serverUrl = http://qa1-za.sakaiproject.org You can call any web application from LinkTool. Some sample apps are in: https://source.sakaiproject.org/svn/linktool/trunk/samples/ Regards Stephen Hi, I am currently working on Sakai 2.5.x. I have enabled link tool by setting following properties in sakai.properties file. webservices.allowlogin=true linktool.enabled=true The following are the screen shots showing a linktool by name "MY_LINKTOOL" which is installed as a tool. [cid:image001.png< at >01C94BC4.AD15F3A0] [cid:image002.png< at >01C94BC4.AD15F3A0] T

Requesting information about Linktool

Priyadarshini_Krishnamurthy — 2008-11-21T05:04:05

Hi, I am currently working on Sakai 2.5.x. I have enabled link tool by setting following properties in sakai.properties file. webservices.allowlogin=true linktool.enabled=true The following are the screen shots showing a linktool by name "MY_LINKTOOL" which is installed as a tool. [cid:image001.png< at >01C94BC4.AD15F3A0] [cid:image002.png< at >01C94BC4.AD15F3A0] The following screen shot shows the setup screen: [cid:image003.png< at >01C94BC4.AD15F3A0] So I would request you to help me by providing following details about linktool: 1.Is this the correct way of enabling linktool and installing it as a tool? 2. Why am I getting a SOAP error in Server callback (as shown in 2nd screenshot)? 3. How to use the Generated Signed Object? 4. What are the external applications that can be called using LinkTool in Sakai2.5? If possible, request you to provide few examples. Please suggest me, if there are any useful links, where in I can find more information about LinkTool. I would kindly request you to acknowledge as soon as pos

Re: BasicSQLService error on 2.6 rc2

Zhen Qian — 2008-11-20T19:26:30

Sean, Could you please document this as a JIRA ticket and assign it to me? Thanks, - Zhen On Nov 20, 2008, at 1:48 PM, Sean Keesler wrote: ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: Development (a.k.a. sakai-dev) site. You can modify how you receive notifications at My Workspace > Preferences.

Crash with trunk version of Kernel

Beth Kirschner — 2008-11-20T19:05:42

I'm attempting to test a kernel-patch but can't get the trunk version of the kernel to start up -- are there new configuration settings that I've been blissfully unaware of? Part of the traceback is copied below

Re: Hibernate and UNION

Roland Groen — 2008-11-20T18:36:58

As far as I can see you have two options: Use a native SQL query and and map the columns on your entity using the return alias. Use (or abuse) the concept of union-subclass to map to empty subclasses of your entity on different tables. <hibernate-mapping> <class name="A" abstract="true"> <union-subclass name="EmptyA1" table="TABLE1"> </union-subclass> <union-subclass name="EmptyA2" table="TABLE2"> </union-subclass> .. The first option will work for sure, but you'll loose many advantages of hibernate. The second is a long shot, please let me know if it works. Steve Swinsburg-2 wrote:

Site Setup links broken (was Re: Getting the Portal URL in 2.5.2)

2008-11-20T18:21:20

Hi all, Just a follow up. This issue occurs in an OOTB version of Sakai 2.5.2 that I've installed. It's affecting the site links in the Workspace's "Worksite Setup" tool (sakai.sitesetup), as well as gives a bad redirect when you use the SU tool. Also, custom tools I write that use ServerConfigurationService.getPortalUrl() receive "/sakai-portal-tool" from this method as well. I managed to find the following JIRA which shed some brief light: http://bugs.sakaiproject.org/jira/browse/SAK-8397 . When I tested it out, however, the debugger shows that the value is being set properly on the RequestFilter's init() method, however the next time I make a request to the tool, m_contextId has been reset to /sakai-portal-tool, which gets set into "threadLocalManager.(CURRENT_PORTAL_PATH)". Have I misconfigured anything? I don't think I have access to try and verify this on any of the community QA servers. Thanks, ------------------------------------------ Branden Visser LMS Application Programmer - Infor

2.5.3 -> Search / Resources Conversion (attn:Ian Boston)

Dave Ross — 2008-11-20T17:42:59

We have encountered two issues with a 2.4.x -> 2.5.3 upgrade we are testing. This is a snapshot of our prod database and filestorage, the schema conversion scripts have run and 2.5.3 starts up without issue. We have approximately 90k resources totalling 200gb. Problems are: 1) The Resources conversion (text->blob xml entities) is not happening "on demand". While we haven't tested the utility, the server is not converting resources "as they are accessed" as described in the readme. Is there a specific property that turns this on? 2) When we do in get around to running the resources conversion utility as part of our migration, does it have to be run from a "development" machine that is pointed at the prod database (e.g. has M2, Sakai source, etc installed)? Seems like the answer is yes, but it's not clear from the documentation. 3) We are trying to get search working as a POC (and we have some historical search needs - which can be done against our snapshot) - the following is in sakai.properties: search.