You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
(41) |
May
(353) |
Jun
(133) |
Jul
(534) |
Aug
(401) |
Sep
(219) |
Oct
(86) |
Nov
(144) |
Dec
(61) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(200) |
Feb
(130) |
Mar
(345) |
Apr
(153) |
May
(247) |
Jun
(338) |
Jul
(222) |
Aug
(70) |
Sep
(39) |
Oct
(27) |
Nov
(76) |
Dec
(30) |
2007 |
Jan
(81) |
Feb
(44) |
Mar
(9) |
Apr
|
May
(3) |
Jun
(2) |
Jul
(34) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
(6) |
2008 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Adam M. <ada...@co...> - 2005-06-30 14:37:37
|
Bernard We have had Bodington working with Oracle although non of the main developers actually work against it; we use the open source postgres or MS sqlserver. I assume you are using v2.4.3? Hopefully somebody will reply soon with a solution to your problem. In the meantime - why not look at http://www.weblearn.ox.ac.uk/bodington/site/ - click on the 'login as visitor' button. You will get access to the open part of the VLE, areas requiring authentication and authorisation will not be visible. Obviously you will not be able to get access to the administration facilities as you must have special rights. happy browsing. adam In message <EBC...@sc...> bod...@li... writes: > I get the following exception during setup, I am running Tomcat 5.5.7 > with Oracle 9i and the latest Oracle JDBC drivers... > > SEVERE: Exception initialising BuildingServer: > org.bodington.server.BuildingServerException: > org.bodington.server.BuildingServerException: Exception getting Class > for database > types.org.bodington.server.JobResultorg.bodington.server.BuildingServerE > xception: Unsupported SQL Type. Table = job_results Field = > execution_time > org.bodington.server.BuildingServerException: > org.bodington.server.BuildingServerException: Exception getting Class > for database > types.org.bodington.server.JobResultorg.bodington.server.BuildingServerE > xception: Unsupported SQL Type. Table = job_results Field = > execution_time > at > org.bodington.server.BuildingServer.initDatabase(BuildingServer.java:470 > ) > at > org.bodington.server.BuildingServer.init(BuildingServer.java:328) > at > org.bodington.server.BuildingServer.createInstance(BuildingServer.java:1 > 80) > at > org.bodington.servlet.SetupServlet.doDBSetup(SetupServlet.java:2028) > at > org.bodington.servlet.SetupServlet.doPost(SetupServlet.java:426) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > ...I'm very anxious to evaluate Bodington for a possible solution to our > need for an LMS to serve New York state universities. Is there a demo > site somewhere that I can use for evaluation? Thanks... > > Bernard Durfee > Lead Programmer/Analyst > SUNY Systems Administration > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > -- -- Dr AC Marshall (Bodington developer) OUCS, 13, Banbury Rd. Oxford. OX2 6NN Cheese of the month: Smoked Wensleydale |
From: Durfee, B. <Ber...@su...> - 2005-06-30 14:17:01
|
I get the following exception during setup, I am running Tomcat 5.5.7 with Oracle 9i and the latest Oracle JDBC drivers... SEVERE: Exception initialising BuildingServer: org.bodington.server.BuildingServerException: org.bodington.server.BuildingServerException: Exception getting Class for database types.org.bodington.server.JobResultorg.bodington.server.BuildingServerE xception: Unsupported SQL Type. Table =3D job_results Field =3D execution_time org.bodington.server.BuildingServerException: org.bodington.server.BuildingServerException: Exception getting Class for database types.org.bodington.server.JobResultorg.bodington.server.BuildingServerE xception: Unsupported SQL Type. Table =3D job_results Field =3D execution_time at org.bodington.server.BuildingServer.initDatabase(BuildingServer.java:470 ) at org.bodington.server.BuildingServer.init(BuildingServer.java:328) at org.bodington.server.BuildingServer.createInstance(BuildingServer.java:1 80) at org.bodington.servlet.SetupServlet.doDBSetup(SetupServlet.java:2028) at org.bodington.servlet.SetupServlet.doPost(SetupServlet.java:426) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) ...I'm very anxious to evaluate Bodington for a possible solution to our need for an LMS to serve New York state universities. Is there a demo site somewhere that I can use for evaluation? Thanks... Bernard Durfee Lead Programmer/Analyst SUNY Systems Administration |
From: Alexis O'C. <ale...@co...> - 2005-06-29 13:59:22
|
Has writing to this list gone out of fashion? -- + - - - - - - - - - - - - - - - - - - - - - - - - - - - + | Alexis O'Connor, VLE Developer (http://bodington.org) | | OUCS, 13 Banbury Road, Oxford, OX2 6NN, UK. | | Tel. +44 (0)1865 283661 | + - - - - - - - - - - - - - - - - - - - - - - - - - - - + |
From: Alexis O'C. <ale...@co...> - 2005-06-29 09:52:34
|
I have been doing some work on Questionnaires. There was *no* javadoc before I started. Maybe I don't actually want future generations to associate me with them in anyway after all [ ;-) ], but I was going to put 'Jon Maber' down as the primary author. Does anyone know different!?! -- + - - - - - - - - - - - - - - - - - - - - - - - - - - - + | Alexis O'Connor, VLE Developer (http://bodington.org) | | OUCS, 13 Banbury Road, Oxford, OX2 6NN, UK. | | Tel. +44 (0)1865 283661 | + - - - - - - - - - - - - - - - - - - - - - - - - - - - + |
From: Sean M. <se...@sm...> - 2005-06-28 11:45:35
|
Zuper und danke. s On 28 Jun 2005, at 12:32, Atif Suleman wrote: > Hi > > >> Atif, are you out there? >> > > Apologies for responding late. Be on my annual leave. Skipton was > great in the sun. > > > >> Aggie may still be around, but we had discussed getting shibadd >> out of the codebase for 2.5, and we thought that you would be >> best placed to remove it and any hooks about from the tree. Are >> you able to pull out the shears and snip away? >> > > No probelm. The shears are out ....... > > Thanks. > Atif. > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > > |
From: Atif S. <BM...@bm...> - 2005-06-28 11:25:45
|
Hi > Atif, are you out there? Apologies for responding late. Be on my annual leave. Skipton was great in the sun. > Aggie may still be around, but we had discussed getting shibadd out > of the codebase for 2.5, and we thought that you would be best placed > to remove it and any hooks about from the tree. Are you able to pull > out the shears and snip away? No probelm. The shears are out ....... Thanks. Atif. |
From: Sean M. <se...@sm...> - 2005-06-24 17:17:50
|
Boys, tagged HEAD at bodington_2_5_2 to mark before template add. I hear that it will happen imminently. best s |
From: Sean M. <se...@sm...> - 2005-06-24 17:00:33
|
Atif, are you out there? Aggie may still be around, but we had discussed getting shibadd out of the codebase for 2.5, and we thought that you would be best placed to remove it and any hooks about from the tree. Are you able to pull out the shears and snip away? best s |
From: Sean M. <se...@sm...> - 2005-06-24 15:54:55
|
Guanxi is a Java application which supports federated authentication and authorization services [AAS]. It includes OS implementations of the SAML specification and the Shibboleth extended profile specification for the IdP, as well as other functions which support Shibboleth in applications which require local accounts to function. Guanxi has been funded as part of the JISC Core Middleware Programme. Guanxi has extended the Bodington VLE to enable Shibboleth IdP functionality out of the box with Bodington. This release, 1.2.0, is a significant upgrade and stable and includes new features in all three Guanxi components, including the IdP, the WAYF and Common. Also included in the update are gx_lib, a package of supporting libs, and SAMUEL. SAMUEL stands for [SAM]l [U]sed in [EL]earning and is a partial implementation of the OASIS SAML 1.1 specification. It's a standalone module, developed as part of the Guanxi project and is used to SAML enable applications. It's self contained in that is also includes XML utilities. More information on some of the related items can be found at the following urls: https://guanxi.sourceforge.net/ http://guanxi.uhi.ac.uk/xwiki/bin/view/v1/2 (includes a complete changelog) http://www.jisc.ac.uk/index.cfm?name=programme_middleware http://shibboleth.internet2.edu/ https://sourceforge.net/projects/bodington/ You can contact the developers and many implementors through the gua...@li... mailing list. Sean Mehan Guanxi Project Manager |
From: Matthew B. <mat...@co...> - 2005-06-24 12:46:12
|
Andrew Booth wrote: > It may not have been a bug. I remember he set up a system whereby he > copied the algorithm used by our computing service for generating > students' initial passwords from date of birth etc. He used plaintext > passwords to check that it gave the same result as the computing > service. I think this may have been the point at which it didn't get put > back. But it's some time ago... Thanks Aggie. -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Antony C. <an...@sm...> - 2005-06-22 13:24:31
|
How about! logException( PrintWriter out, String sourceClassName, String sourceMethodName, String message, Throwable th, Level level ) logException( String sourceClassName, String sourceMethodName, String message, Throwable th, Level level ) logException( PrintWriter out, String sourceClassName, String sourceMethodName, String message, Throwable th)- level=Severe logException( String sourceClassName, String sourceMethodName, String message, Throwable th) - level=Severe userException( PrintWriter out, Throwable th ) - where message is freindly text On 22 Jun 2005, at 13:17, Matthew Buckett wrote: > Antony Corfield wrote: >>> > Good idea, user exceptions should >>> >>>> contain user-friendly message and could be used to report back to >>>> user (could still be logged at a finer level). Can't see that "You >>>> don't have access rights allowing you to delete sections here." is >>>> output to user in LogBookFacility!? >>> >>> >>> Here: >> Ok, I see you are using it to output message but I was referring to >> original LogBookFacility which I doesn't. > > logException actually outputs the message to the user. Maybe the > method should be renamed to logAndDisplayException()? > > -- > +--Matthew Buckett-----------------------------------------+ > | VLE Developer, Learning Technologies Group | > | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | > +------------Computing Services, University of Oxford------+ > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Andrew B. <a.g...@le...> - 2005-06-22 13:08:49
|
It may not have been a bug. I remember he set up a system whereby he copied the algorithm used by our computing service for generating students' initial passwords from date of birth etc. He used plaintext passwords to check that it gave the same result as the computing service. I think this may have been the point at which it didn't get put back. But it's some time ago... Aggie -----Original Message----- From: bod...@li... [mailto:bod...@li...] On Behalf Of Matthew Buckett Sent: 22 June 2005 13:15 To: bod...@li... Subject: [Bodington-developers] Re: Encrypted Bodington Passwords (was Re: [Bodington-developers] Bodington with SP and IdP - SSO and v2.6) Andrew Booth wrote: > PassPhrase.encrypt is there because the passwords were originally > encrypted. Jon found a bug and used unencrypted passwords while he fixed > it. It never got put back. Do you know what the bug was? -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Bodington-developers mailing list Bod...@li... https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Matthew B. <mat...@co...> - 2005-06-22 12:17:10
|
Antony Corfield wrote: >> > Good idea, user exceptions should >> >>> contain user-friendly message and could be used to report back to >>> user (could still be logged at a finer level). Can't see that "You >>> don't have access rights allowing you to delete sections here." is >>> output to user in LogBookFacility!? >> >> >> Here: > > Ok, I see you are using it to output message but I was referring to > original LogBookFacility which I doesn't. logException actually outputs the message to the user. Maybe the method should be renamed to logAndDisplayException()? -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Matthew B. <mat...@co...> - 2005-06-22 12:14:52
|
Andrew Booth wrote: > PassPhrase.encrypt is there because the passwords were originally > encrypted. Jon found a bug and used unencrypted passwords while he fixed > it. It never got put back. Do you know what the bug was? -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Antony C. <an...@sm...> - 2005-06-22 12:06:24
|
> > Good idea, user exceptions should >> contain user-friendly message and could be used to report back to >> user (could still be logged at a finer level). Can't see that "You >> don't have access rights allowing you to delete sections here." is >> output to user in LogBookFacility!? > > Here: Ok, I see you are using it to output message but I was referring to original LogBookFacility which I doesn't. |
From: Andrew B. <a.g...@le...> - 2005-06-22 12:05:28
|
PassPhrase.encrypt is there because the passwords were originally encrypted. Jon found a bug and used unencrypted passwords while he fixed it. It never got put back. Aggie -----Original Message----- From: bod...@li... [mailto:bod...@li...] On Behalf Of Matthew Buckett Sent: 22 June 2005 12:42 To: bod...@li... Subject: Encrypted Bodington Passwords (was Re: [Bodington-developers] Bodington with SP and IdP - SSO and v2.6) Alistair Young wrote: > Now we're on the subject I think it's time bod stopped storing passwords > in plain text. Attached is a slightly cleaned up version of my patch. The current solution isn't very beautiful, but I think it works. Part of the problem is that password changing is done is several ways and different parts of the codebase do it differently, cleaning that up is a much more complicated and tricky job. My patch makes encrypted passwords enforced (for new passwords and changes to existing ones) although old unencrypted passwords continue to work for login purposes. NB: It looked like John had started work on this but never completed it. PassPhrase.encrypt() was already in the codebase. -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Matthew B. <mat...@co...> - 2005-06-22 11:51:01
|
Antony Corfield wrote: > Good idea, user exceptions should > contain user-friendly message and could be used to report back to user > (could still be logged at a finer level). Can't see that "You don't > have access rights allowing you to delete sections here." is output to > user in LogBookFacility!? Here: >> +++ src/org/bodington/logbook/servlet/LogBookFacility.java 21 Jun >> 2005 15:55:31 -0000 >> @@ -66,6 +66,7 @@ >> import org.bodington.logbook.server.*; >> import org.bodington.database.PrimaryKey; >> import org.bodington.server.BuildingContext; >> +import org.bodington.server.BuildingServerUserException; >> import org.bodington.server.BuildingSession; >> import org.bodington.server.BuildingSessionManagerImpl; >> import org.bodington.server.BuildingServerException; >> @@ -1554,6 +1555,11 @@ >> { >> lb_session.deleteSection( section_id ); >> } >> + catch (BuildingServerUserException bsue) >> + { >> + out.write(bsue.getMessage()); >> + return; >> + } >> catch ( BuildingServerException bsex ) >> { >> logException( out, "LogBookFacility", "deleteSection", > ps. after your Skye visit, can we now refer to you as (Matthew) The Bucket! After my close inspection I must say you have very nice toilets installed in your student halls ;-) -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Matthew B. <mat...@co...> - 2005-06-22 11:42:17
|
Alistair Young wrote: > Now we're on the subject I think it's time bod stopped storing passwords > in plain text. Attached is a slightly cleaned up version of my patch. The current solution isn't very beautiful, but I think it works. Part of the problem is that password changing is done is several ways and different parts of the codebase do it differently, cleaning that up is a much more complicated and tricky job. My patch makes encrypted passwords enforced (for new passwords and changes to existing ones) although old unencrypted passwords continue to work for login purposes. NB: It looked like John had started work on this but never completed it. PassPhrase.encrypt() was already in the codebase. -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Antony C. <an...@sm...> - 2005-06-22 10:45:41
|
Matthew, you are a true code digger! Good idea, user exceptions should contain user-friendly message and could be used to report back to user (could still be logged at a finer level). Can't see that "You don't have access rights allowing you to delete sections here." is output to user in LogBookFacility!? Antony ps. after your Skye visit, can we now refer to you as (Matthew) The Bucket! On 21 Jun 2005, at 17:05, Matthew Buckett wrote: > At the moment whenever an exception gets thrown from a method in > BuildingSession (or subclass) the calling code (normally a facility) > logs the exception. > > The problem is that some of these errors are just users doing silly > things and don't need to be logged. One example of this is when a user > tries to remove a section from a logbook that contains questions a > BuildingServerException is thrown from the > LogBookSessionImpl.deleteSection() method. > > Now the LogBookSession.deleteSection() method may throw a > BuildingServerException for a much more serious error as well (not > being able to fing the logbook associated with the session). > > To allow us to still log the serious errors but ignore (but still > display to the user) the others I create a new exception > BuildingServerUserException that subclasses BuildingServerException > and then a special catch clause can be added in places where it is > needed. > > As an example attached is the patch that shows the changes to > LogBookSessionImpl. > > Comments? > > -- > +--Matthew Buckett-----------------------------------------+ > | VLE Developer, Learning Technologies Group | > | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | > +------------Computing Services, University of Oxford------+ > Index: src/org/bodington/logbook/server/LogBookSessionImpl.java > =================================================================== > RCS file: > /usr/cvs/src/master/bodington/src/org/bodington/logbook/server/ > LogBookSessionImpl.java,v > retrieving revision 1.6 > diff -u -r1.6 LogBookSessionImpl.java > --- src/org/bodington/logbook/server/LogBookSessionImpl.java 27 May > 2005 14:40:12 -0000 1.6 > +++ src/org/bodington/logbook/server/LogBookSessionImpl.java 21 Jun > 2005 15:55:31 -0000 > @@ -462,14 +462,17 @@ > * Deletes a specific section. > * > * @exception java.rmi.RemoteException > - * @exception BuildingServerException > + * @exception BuildingServerException Something went seriously wrong. > + * @exception BuildingServerUserException Something went wrong that > should > + * be reported to the user but probably doesn't need to be logged. > + * > */ > public void deleteSection( PrimaryKey section_id ) > throws RemoteException, BuildingServerException > { > LogBook lb = getLogBook(); > if ( !lb.checkPermission( Permission.EDIT ) ) > - throw new BuildingServerException( "You don't have access rights > allowing you to delete sections here." ); > + throw new BuildingServerUserException( "You don't have access > rights allowing you to delete sections here." ); > > invalidateCsvQuestionFile(); > > @@ -479,7 +482,7 @@ > LogBookQuestion[] questions = this.getQuestionsInOrder( > section.getLogBookSectionId() ); > > if ( questions!=null && questions.length>0 ) > - throw new BuildingServerException( "Can't delete sections that > contain questions." ); > + throw new BuildingServerUserException( "Can't delete sections that > contain questions." ); > > // delete it > section.delete(); > Index: src/org/bodington/logbook/servlet/LogBookFacility.java > =================================================================== > RCS file: > /usr/cvs/src/master/bodington/src/org/bodington/logbook/servlet/ > LogBookFacility.java,v > retrieving revision 1.7 > diff -u -r1.7 LogBookFacility.java > --- src/org/bodington/logbook/servlet/LogBookFacility.java 27 May 2005 > 14:40:12 -0000 1.7 > +++ src/org/bodington/logbook/servlet/LogBookFacility.java 21 Jun 2005 > 15:55:31 -0000 > @@ -66,6 +66,7 @@ > import org.bodington.logbook.server.*; > import org.bodington.database.PrimaryKey; > import org.bodington.server.BuildingContext; > +import org.bodington.server.BuildingServerUserException; > import org.bodington.server.BuildingSession; > import org.bodington.server.BuildingSessionManagerImpl; > import org.bodington.server.BuildingServerException; > @@ -1554,6 +1555,11 @@ > { > lb_session.deleteSection( section_id ); > } > + catch (BuildingServerUserException bsue) > + { > + out.write(bsue.getMessage()); > + return; > + } > catch ( BuildingServerException bsex ) > { > logException( out, "LogBookFacility", "deleteSection", > /* > ====================================================================== > The Bodington System Software License, Version 1.0 > > Copyright (c) 2001 The University of Leeds. All rights reserved. > > Redistribution and use in source and binary forms, with or without > modification, are permitted provided that the following conditions are > met: > > 1. Redistributions of source code must retain the above copyright > notice, > this list of conditions and the following disclaimer. > > 2. Redistributions in binary form must reproduce the above copyright > notice, this list of conditions and the following disclaimer in the > documentation and/or other materials provided with the distribution. > > 3. The end-user documentation included with the redistribution, if > any, > must include the following acknowledgement: "This product includes > software developed by the University of Leeds > (http://www.bodington.org/)." Alternately, this acknowledgement may > appear in the software itself, if and wherever such third-party > acknowledgements normally appear. > > 4. The names "Bodington", "Nathan Bodington", "Bodington System", > "Bodington Open Source Project", and "The University of Leeds" must > not be > used to endorse or promote products derived from this software without > prior written permission. For written permission, please contact > d.g...@le.... > > 5. The name "Bodington" may not appear in the name of products derived > from this software without prior written permission of the University > of > Leeds. > > THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED > WARRANTIES, INCLUDING, BUT NOT LIMITED TO, TITLE, THE IMPLIED > WARRANTIES > OF QUALITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO > EVENT SHALL THE UNIVERSITY OF LEEDS OR ITS CONTRIBUTORS BE LIABLE FOR > ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL > DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE > GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS > INTERRUPTION) > HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, > STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING > IN > ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE > POSSIBILITY OF SUCH DAMAGE. > ========================================================= > > This software was originally created by the University of Leeds and > may contain voluntary > contributions from others. For more information on the Bodington Open > Source Project, please > see http://bodington.org/ > > ====================================================================== > */ > > package org.bodington.server; > > import org.bodington.pool.ObjectPoolException; > > /** > * Class that should be thrown when an error is encountered that > should be show > * to the user but probably doesn't need to be logged. > * @author buckett > */ > public class BuildingServerUserException extends > BuildingServerException > { > > /** > * Create a new BuildingServerUserException. > * @param s The error message that will probably be show to the > user. > */ > public BuildingServerUserException(String s) > { > super(s); > } > > > } |
From: Matthew B. <mat...@co...> - 2005-06-21 19:33:26
|
At the moment whenever an exception gets thrown from a method in BuildingSession (or subclass) the calling code (normally a facility) logs the exception. The problem is that some of these errors are just users doing silly things and don't need to be logged. One example of this is when a user tries to remove a section from a logbook that contains questions a BuildingServerException is thrown from the LogBookSessionImpl.deleteSection() method. Now the LogBookSession.deleteSection() method may throw a BuildingServerException for a much more serious error as well (not being able to fing the logbook associated with the session). To allow us to still log the serious errors but ignore (but still display to the user) the others I create a new exception BuildingServerUserException that subclasses BuildingServerException and then a special catch clause can be added in places where it is needed. As an example attached is the patch that shows the changes to LogBookSessionImpl. Comments? -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Adam M. <ada...@co...> - 2005-06-21 18:21:48
|
I think Peter Crowther would be interested in this. He may have done a little something in this area. The consensus is no. adam -- Adam Marshall: OUCS, 13, Banbury Rd. Oxford OX2 6NN. Shameless plug: Use the Bodington VLE http://bodington.org Blog: http://ramble.oucs.ox.ac.uk/blog/adamm/ Cheese of the month: Cheshire (not to be underestimated) | | [alexw - Fri May 13 16:18:58 2005]: | | > 2005-05-13 12:46:15,636 [TP-Processor12] ERROR | > org.bodington.servlet.facilities.Facility - Can't delete sections | > that contain questions. | | Should a user be able to delete a LogBook section that contains | questions? If not then I'll just change the way this is logged and close | it. | | -- | +--Matthew Buckett-----------------------------------------+ | | VLE Developer, Learning Technologies Group | | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | | +------------Computing Services, University of Oxford------+ |
From: Adam M. <ada...@co...> - 2005-06-21 17:33:03
|
Space separated lists in XML attributes are more normal. I think you should support this form as well. Adam Trubblecauser -- Adam Marshall: OUCS, 13, Banbury Rd. Oxford OX2 6NN. Shameless plug: Use the Bodington VLE http://bodington.org Blog: http://ramble.oucs.ox.ac.uk/blog/adamm/ Cheese of the month: Cheshire (not to be underestimated) | -----Original Message----- | From: bod...@li... [mailto:bodington- | dev...@li...] On Behalf Of Alistair Young | Sent: 20 June 2005 11:51 | To: Bodington Developers | Subject: [Bodington-developers] Template localisation : the numbers | | Had a quick look and it would seem there are only 60 new style | templates and 459 old style ones. Therefore the localisation will be | much quicker as only new style are supported. | | Below is the list of templates requiring localisation. | | I'll offer to the do the ones in default. Any takers for the rest? | Note there are a few scraps at the start if someone has a spare 10mins. | | We'll start when Ant puts the new templates in head. | | How to localise : http://www.weblogs.uhi.ac.uk/sm00ay/?p=90 | | | | | building/main.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | directory/consentconfirm.html:<template | facilityclass="org.bodington.servlet.facilities.UserDirectoryFacility"> | directory/consentform.html:<template | facilityclass="org.bodington.servlet.facilities.UserDirectoryFacility"> | | floor/main.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | mediadocument/menu.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | password/x509check.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | room/main.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | site/main.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | suite/main.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | default/applettop.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/error403.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/graphic.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/graphic_calc.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/index.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/login.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/login_anon.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/login_basic.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/login_logout_confirm.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/login_step1.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/login_step2.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/login_step3.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/login_step4.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/logout.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/logout_confirm.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/menu.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/properties.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/styletest.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/top.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/useroption1.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | default/useroptions.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | mcq/abouttool.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqdebrief.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqdebrieftech.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqhelp.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqhelp1.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqhelp2.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqhelp3.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqhelp4.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqhelp5.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqhelp6.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | mcq/mcqtutorial.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | messagingroom/flatcontents1.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | messagingroom/flatcontents2.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | messagingroom/flatcontents3.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | messagingroom/index.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | messagingroom/messagetext.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newcontents.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | messagingroom/newparticipants1.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newparticipants2.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newparticipants3.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newparticipants4.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newparticipants5.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newparticipants6.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newparticipantsm.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newreaders.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newreaders2.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/newreaders3.html:<template | facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> | messagingroom/useroption2.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | messagingroom/useroptions.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | messagingroom/useroptiontest.html:<template | facilityclass="org.bodington.servlet.facilities.Facility"> | | Alistair | | | | ------------------------------------------------------- | SF.Net email is sponsored by: Discover Easy Linux Migration Strategies | from IBM. Find simple to follow Roadmaps, straightforward articles, | informative Webcasts and more! Get everything you need to get up to | speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click | _______________________________________________ | Bodington-developers mailing list | Bod...@li... | https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Adam M. <ada...@co...> - 2005-06-21 17:18:06
|
Jane You may find this useful. If Bodington can address the five issues raised here then we stand a greater chance of success: http://www.firstmonday.org/issues/issue9_4/levesque/ "the five most important flaws with Open Source software development to be as follows: 1. User interface design 2. Documentation 3. Feature-centric development 4. Programming for the self 5. Religious blindness" Perhaps you should put together guidelines for us developers and then give us some electric shock treatment when we don't follow the rules! It's the sort of thing that could be part of the "Bodington Developer Philosophy"? Adam |
From: Alistair Y. <ali...@sm...> - 2005-06-20 11:18:33
|
Had a quick look and it would seem there are only 60 new style templates and 459 old style ones. Therefore the localisation will be much quicker as only new style are supported. Below is the list of templates requiring localisation. I'll offer to the do the ones in default. Any takers for the rest? Note there are a few scraps at the start if someone has a spare 10mins. We'll start when Ant puts the new templates in head. How to localise : http://www.weblogs.uhi.ac.uk/sm00ay/?p=90 building/main.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> directory/consentconfirm.html:<template facilityclass="org.bodington.servlet.facilities.UserDirectoryFacility"> directory/consentform.html:<template facilityclass="org.bodington.servlet.facilities.UserDirectoryFacility"> floor/main.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mediadocument/menu.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> password/x509check.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> room/main.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> site/main.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> suite/main.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/applettop.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/error403.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/graphic.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/graphic_calc.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/index.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/login.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/login_anon.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/login_basic.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/login_logout_confirm.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/login_step1.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/login_step2.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/login_step3.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/login_step4.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/logout.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/logout_confirm.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/menu.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/properties.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/styletest.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/top.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/useroption1.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> default/useroptions.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/abouttool.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqdebrief.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqdebrieftech.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqhelp.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqhelp1.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqhelp2.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqhelp3.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqhelp4.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqhelp5.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqhelp6.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> mcq/mcqtutorial.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> messagingroom/flatcontents1.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> messagingroom/flatcontents2.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> messagingroom/flatcontents3.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> messagingroom/index.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> messagingroom/messagetext.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newcontents.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> messagingroom/newparticipants1.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newparticipants2.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newparticipants3.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newparticipants4.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newparticipants5.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newparticipants6.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newparticipantsm.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newreaders.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newreaders2.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/newreaders3.html:<template facilityclass="org.bodington.servlet.facilities.MessagingRoomFacility"> messagingroom/useroption2.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> messagingroom/useroptions.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> messagingroom/useroptiontest.html:<template facilityclass="org.bodington.servlet.facilities.Facility"> Alistair |
From: Antony C. <an...@sm...> - 2005-06-17 15:18:58
|
yes we could get Italian Catalan and possibly French Finnish Romanian Sean has further European contacts On 17 Jun 2005, at 16:10, Adam Marshall wrote: > Was there not talk of some of your CABLE partners doing stuff? > > adam > > -- > Adam Marshall: OUCS, 13, Banbury Rd. Oxford OX2 6NN. > Shameless plug: Use the Bodington VLE http://bodington.org > Blog: http://ramble.oucs.ox.ac.uk/blog/adamm/ > Cheese of the month: Cheshire (not to be underestimated) > > | -----Original Message----- > | From: bod...@li... > [mailto:bodington- > | dev...@li...] On Behalf Of Alistair Young > | Sent: 17 June 2005 16:08 > | To: bod...@li... > | Subject: Re: [Bodington-developers] Foreign language translation of > | bodington - what support? > | > | > What languages will UHI be adding to Bodington? > | Gaelic - though I may do a Weegie one in my spare time! > | > | > And what are the timescales? > | dunno - Sean? > | > | > How much work do we envisage it being to do a basic translation > | dunno - won't know until the template localisation is done. Then > | we'll see how many duplicates we can put into generic bundles > | > | Alistair > | > | > | > | On 17 Jun 2005, at 15:52, Adam Marshall wrote: > | > | > What languages will UHI be adding to Bodington? And what are the > | > timescales? > | > > | > How much work do we envisage it being to do a basic translation - I > | > guess - > | > how many words are we looking at? > | > > | > Stuart seems to think we could get some grad students here to do > some > | > translations (for suitable remuneration). > | > > | > I guess we need to draw up a target list: > | > > | > - Spanish > | > - portugese > | > - Italian > | > - german > | > - french > | > - polish > | > - Finnish > | > - Swedish > | > - Norwegian > | > - danish > | > - Chinese, what dialects? <- Ning Ning- a chance to earn some > | > extra money!? > | > - gaelic > | > - welsh (Alun said he'd look into this) > | > - Indian languages ?? > | > > | > Adam > | > > | > -- > | > Adam Marshall: OUCS, 13, Banbury Rd. Oxford OX2 6NN. > | > Shameless plug: Use the Bodington VLE http://bodington.org > | > Blog: http://ramble.oucs.ox.ac.uk/blog/adamm/ > | > Cheese of the month: Cheshire (not to be underestimated) > | > > | > > | > > | > > | > ------------------------------------------------------- > | > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > | > from IBM. Find simple to follow Roadmaps, straightforward articles, > | > informative Webcasts and more! Get everything you need to get up to > | > speed, fast. > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > | > _______________________________________________ > | > Bodington-developers mailing list > | > Bod...@li... > | > https://lists.sourceforge.net/lists/listinfo/bodington-developers > | > > | > | > | > | ------------------------------------------------------- > | SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > | from IBM. Find simple to follow Roadmaps, straightforward articles, > | informative Webcasts and more! Get everything you need to get up to > | speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > | _______________________________________________ > | Bodington-developers mailing list > | Bod...@li... > | https://lists.sourceforge.net/lists/listinfo/bodington-developers > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |