Menu
▾
▴
bodington-developers — Mailing list for Bodington developers
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: Sean M. <se...@sm...> - 2006-10-18 12:59:28
|
yeah, i'm ++1 on that.
s.
On 18 Oct 2006, at 12:50, Alexis O'Connor wrote:
> Alexis O'Connor wrote:
>> Alistair Young wrote:
>>> got a problem from the 2.8 release
>>>
>>> org.bodington.logbook.server.LogBookSessionImpl::getEntriesInOrder()
>>> ...
>>> Enumeration enum = ...
>>> ...
>>>
>>> enum is a reserved word in 1.5 so bod won't compile under 1.5 any
>>> more
>>>
>>> Alistair
>>>
>>>
>>
>> Yep, some time ago I altered all the variables named 'enum' to
>> 'enumeration'
>> (~800!). These have started to creep back in - who, I don't know
>> as I'm not
>> clever enough to use the 'CVS annotate' function in Eclipse ;-).
>> Unless anyone
>> has a better idea, renaming them according to the above is
>> probably as good a
>> strategy as any.
>>
>> Alexis
>>
>
> (Apologies for replying to my own e-mail).
>
> As a related aside, I think that it's an unwritten rule that we
> should probably
> still be compiling against a v1.4.2 JDK with source and class
> compliance set to
> version 1.4. This way ("Sakai style"!) one can still *run* on JDK
> 1.5 / Tomcat
> 5.5 for performance reasons, whilst still keeping an eye on
> backwards compatability.
>
> Alexis
>
>
> ----------------------------------------------------------------------
> ---
> Using Tomcat but need to do more? Need to support web services,
> security?
> Get stuff done quickly with pre-integrated technology to make your
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
|
|
From: Alexis O'C. <ale...@ou...> - 2006-10-18 11:48:48
|
Alexis O'Connor wrote:
> Alistair Young wrote:
>> got a problem from the 2.8 release
>>
>> org.bodington.logbook.server.LogBookSessionImpl::getEntriesInOrder()
>> ...
>> Enumeration enum = ...
>> ...
>>
>> enum is a reserved word in 1.5 so bod won't compile under 1.5 any more
>>
>> Alistair
>>
>>
>
> Yep, some time ago I altered all the variables named 'enum' to 'enumeration'
> (~800!). These have started to creep back in - who, I don't know as I'm not
> clever enough to use the 'CVS annotate' function in Eclipse ;-). Unless anyone
> has a better idea, renaming them according to the above is probably as good a
> strategy as any.
>
> Alexis
>
(Apologies for replying to my own e-mail).
As a related aside, I think that it's an unwritten rule that we should probably
still be compiling against a v1.4.2 JDK with source and class compliance set to
version 1.4. This way ("Sakai style"!) one can still *run* on JDK 1.5 / Tomcat
5.5 for performance reasons, whilst still keeping an eye on backwards compatability.
Alexis
|
|
From: Alistair Y. <ali...@sm...> - 2006-10-18 11:30:42
|
AFAIK they've never existed before 2.8 as bod normally compiles under 1.5 Alistair On 18 Oct 2006, at 12:25, Peter Crowther wrote: >> From: Alistair Young >> org.bodington.logbook.server.LogBookSessionImpl::getEntriesInOrder() >> ... >> Enumeration enum = ... >> ... >> >> enum is a reserved word in 1.5 so bod won't compile under 1.5 any >> more > > If that's the only instance, I'll be amazed. I've been trying to > remove > them (using 'e') where I come across them. > > - Peter > > ---------------------------------------------------------------------- > --- > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
|
From: Alexis O'C. <ale...@ou...> - 2006-10-18 11:30:42
|
Alistair Young wrote: > got a problem from the 2.8 release > > org.bodington.logbook.server.LogBookSessionImpl::getEntriesInOrder() > ... > Enumeration enum = ... > ... > > enum is a reserved word in 1.5 so bod won't compile under 1.5 any more > > Alistair > > Yep, some time ago I altered all the variables named 'enum' to 'enumeration' (~800!). These have started to creep back in - who, I don't know as I'm not clever enough to use the 'CVS annotate' function in Eclipse ;-). Unless anyone has a better idea, renaming them according to the above is probably as good a strategy as any. Alexis |
|
From: Peter C. <Pet...@me...> - 2006-10-18 11:26:03
|
> From: Alistair Young > org.bodington.logbook.server.LogBookSessionImpl::getEntriesInOrder() > ... > Enumeration enum =3D ... > ... >=20 > enum is a reserved word in 1.5 so bod won't compile under 1.5 any more If that's the only instance, I'll be amazed. I've been trying to remove them (using 'e') where I come across them. - Peter |
|
From: Alistair Y. <ali...@sm...> - 2006-10-18 11:12:41
|
got a problem from the 2.8 release org.bodington.logbook.server.LogBookSessionImpl::getEntriesInOrder() ... Enumeration enum = ... ... enum is a reserved word in 1.5 so bod won't compile under 1.5 any more Alistair |
|
From: Michael F. <mi...@mf...> - 2006-10-17 14:34:40
|
Hello all, I'm interested in finding out how well Bodington's access privileges capabilities would map to uPortal's Person Attributes Group Store (PAGS). Has anybody looked at this? (Please keep your answers simple as I am not a developer.) Thanks in advance. Kindest regards, Michael Feldstein |
|
From: Sean M. <se...@sm...> - 2006-10-12 15:27:29
|
Begin forwarded message: > |
|
From: Colin T. <col...@ou...> - 2006-10-10 15:50:37
|
OSSWatch have put up a page on their wiki about the new Bod release with Apache licence. There is currently a news item on their front page that links to it: http://www.oss-watch.ac.uk/ or if that's no longer there when you read this, the page is at: http://www.oss-watch.ac.uk/resources/bodington-open.xml -- ____________________________________ Colin Tatham VLE Team Oxford University Computing Services http://www.oucs.ox.ac.uk/ltg/vle/ http://bodington.org |
|
From: Alistair Y. <ali...@sm...> - 2006-10-04 10:49:05
|
that makes sense, thanks for that Jon --=20 Alistair Young Senior Software Engineer UHI@Sabhal M=F2r Ostaig Isle of Skye Scotland > Alistair Young wrote: >>> if the group has no owners, how do you control who can amend the >>> group? >>> >> it's an institutionally defined goup. No users will have access to >> modify >> it. It's auto populated from external programs. >> >> If anything, sysadmin may have access though it's conceivable the grou= p >> is >> actually maintained via an external interface. >> >> > You still need access control because you need see access to add the > group to an access control list. > > The easiest thing is to create one resource in a administration area of > the site and attach all the groups to that resource. That way you can > control access to all the groups via a single access control list - i.e= . > the ACL of the resource. The owner of the resource will be owner of th= e > groups. > > Jon > > |
|
From: Jon M. <jo...@te...> - 2006-10-04 10:37:25
|
Alistair Young wrote: >> if the group has no owners, how do you control who can amend the >> group? >> > it's an institutionally defined goup. No users will have access to modify > it. It's auto populated from external programs. > > If anything, sysadmin may have access though it's conceivable the group is > actually maintained via an external interface. > > You still need access control because you need 'see' access to add the group to an access control list. The easiest thing is to create one resource in a administration area of the site and attach all the groups to that resource. That way you can control access to all the groups via a single access control list - i.e. the ACL of the resource. The owner of the resource will be owner of the groups. This is how it works at Leeds. If you have a large number of groups it helps users if you can name them hierarchically in some way so that as you browse the groups it doesn't take so long to compile each list. Jon |
|
From: Alistair Y. <ali...@sm...> - 2006-10-04 10:27:08
|
> if the group has no owners, how do you control who can amend the > group? it's an institutionally defined goup. No users will have access to modify it. It's auto populated from external programs. If anything, sysadmin may have access though it's conceivable the group i= s actually maintained via an external interface. --=20 Alistair Young Senior Software Engineer UHI@Sabhal M=F2r Ostaig Isle of Skye Scotland >> From: Alistair Young >> Is it possible to create a Group on the fly? > > Yes. See the code in the logbook that creates one group for each user > who shares their page. > >> I seem to >> remember Group objects have position, so you have to decide >> who the owner is. > > Yes, you do. > >> Or is it possible to have a sort of branch line, separate from the >> mainline objects where one could create goups that aren't >> that bothered who they're "owned" by? > > Uh... if the group has no owners, how do you control who can amend the > group? > > - Peter > > -----------------------------------------------------------------------= -- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Peter C. <Pet...@me...> - 2006-10-04 10:22:54
|
> From: Alistair Young > Is it possible to create a Group on the fly? Yes. See the code in the logbook that creates one group for each user who shares their page. > I seem to > remember Group objects have position, so you have to decide=20 > who the owner is. Yes, you do. > Or is it possible to have a sort of branch line, separate from the > mainline objects where one could create goups that aren't=20 > that bothered who they're "owned" by? Uh... if the group has no owners, how do you control who can amend the group? - Peter |
|
From: Alistair Y. <ali...@sm...> - 2006-10-04 10:10:42
|
I've been dusting the cobwebs off my Bodington for Dummies but not sure about this. Is it possible to create a Group on the fly? I seem to remember Group objects have position, so you have to decide who the owner is. Or is it possible to have a sort of branch line, separate from the mainline objects where one could create goups that aren't that bothered who they're "owned" by? --=20 Alistair Young Senior Software Engineer UHI@Sabhal M=F2r Ostaig Isle of Skye Scotland |
|
From: Matthew B. <mat...@ou...> - 2006-10-02 16:01:47
|
Sean Mehan wrote: > Uhmm, why reinvent the wheel? Mod_proxy for Apache, in front of your > tomcat? Performance and Transparency. AJP provides a binary connection between your Web Server and your Servlet Container so that you don't end up fully parsing the request twice. It also passed extra info across to the servlet container (URL, SSL stuff) which can get lost when proxying (request.isSecure()). Finally it has persistent connections between the web server and the servlet container so that you don't make a new TCP connection per request. -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
|
From: Sean M. <se...@sm...> - 2006-10-02 15:36:33
|
Uhmm, why reinvent the wheel? Mod_proxy for Apache, in front of your tomcat? s. On 2 Oct 2006, at 14:42, Jon Maber wrote: > Matthew Buckett wrote: >> The primary advantage is that you no longer have to configure >> Bodington >> to get it running. This makes the quickstart just work. It also >> means if >> you decide to change the hostname that Bodington is deployed under >> you >> don't have to perform any reconfiguration other than to your servlet >> container. >> > So how about one or two extra bodington.properties entries for my use? >> Why would you want to serve a Website up under several names? >> I can see this may have been an argument 5 years ago when there where >> clients that didn't support HTTP/1.0 and so didn't work with virtual >> hosts but this is 2006. Hosting a website under multiple domains >> leaves >> you a little exposed to spoofing attacks as users no longer rely on >> looking at the URL bar to determine if they are at the correct site. >> > You may not _want_ to have multiple names but sometimes you don't > get a > choice. My problem is that the server is also 'localhost' which I was > using in my Apache configuration. However the problem for others is > that the official name might change - e.g. Bodington Common at > Leeds was > on www.fldu.leeds.ac.uk but a new name vle.leeds.ac.uk was adopted. > The > old alias is needed to handle links into the VLE from other web sites > but the new name is the official one. The multiple names will also > occur if the physical server has multiple functions, e.g. > mail.uni.ac.uk, www.uni.ac.uk etc. The configured server name forces > the user to access the proper url. >> I can see that this is a valid use of the old setup and hadn't >> though of it. >> >> It should be reasonably easy to support using the >> bodington.properties >> if they are set and if not falling back the request properties. >> > That would also require a change to the setup servlet since setting > the > port numbers and server name seems to be compulsory. >> Have you considered using AJP rather than mod_proxy which will >> preserve >> the orginal URLs (I believe) so you don't hit this problem. >> >> http://tomcat.apache.org/tomcat-5.5-doc/connectors.html >> > I did and I can't remember why I rejected it. Possible because > mod_proxy > is very easy to set up. >> It was previously an undocumented feature ;-) >> > O.K., how about this; change the text of the setup servlet to > indicate > that the server name is only required if the users could access the > server using multiple names. Then the code that constructs absolute > URLs for inclusion in HTML can use the server name in the properties > file but if not set use the server name in the request. Similarly the > port numbers - use the values from the properties file if available. > > There is still a problem with your no-configuration option. When the > user is switched from non-secure to secure for their password how can > you determine the right port number if it isn't configured by the > sysadmin using setup servlet? > > Jon > > > > > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Matthew B. <mat...@ou...> - 2006-10-02 15:00:44
|
Jon Maber wrote: > Matthew Buckett wrote: >> The primary advantage is that you no longer have to configure Bodington >> to get it running. This makes the quickstart just work. It also means if >> you decide to change the hostname that Bodington is deployed under you >> don't have to perform any reconfiguration other than to your servlet >> container. >> > So how about one or two extra bodington.properties entries for my use? Why not just use the ones that were defined before? >> Why would you want to serve a Website up under several names? >> I can see this may have been an argument 5 years ago when there where >> clients that didn't support HTTP/1.0 and so didn't work with virtual >> hosts but this is 2006. Hosting a website under multiple domains leaves >> you a little exposed to spoofing attacks as users no longer rely on >> looking at the URL bar to determine if they are at the correct site. >> > You may not _want_ to have multiple names but sometimes you don't get a > choice. My problem is that the server is also 'localhost' which I was > using in my Apache configuration. However the problem for others is > that the official name might change - e.g. Bodington Common at Leeds was > on www.fldu.leeds.ac.uk but a new name vle.leeds.ac.uk was adopted. Redirects are a much better way of handling this as it prevents people from bookmarking the old hostname. > The > old alias is needed to handle links into the VLE from other web sites > but the new name is the official one. The multiple names will also > occur if the physical server has multiple functions, e.g. > mail.uni.ac.uk, www.uni.ac.uk etc. The configured server name forces > the user to access the proper url. With any half decent web server you have the choice over what content is served up for a particular domain. >> I can see that this is a valid use of the old setup and hadn't though of it. >> >> It should be reasonably easy to support using the bodington.properties >> if they are set and if not falling back the request properties. >> > That would also require a change to the setup servlet since setting the > port numbers and server name seems to be compulsory. That should be a bug then as I was under the impression that they were optional. >> Have you considered using AJP rather than mod_proxy which will preserve >> the orginal URLs (I believe) so you don't hit this problem. >> >> http://tomcat.apache.org/tomcat-5.5-doc/connectors.html >> > I did and I can't remember why I rejected it. Possible because mod_proxy > is very easy to set up. Ok. >> It was previously an undocumented feature ;-) >> > O.K., how about this; change the text of the setup servlet to indicate > that the server name is only required if the users could access the > server using multiple names. Then the code that constructs absolute > URLs for inclusion in HTML can use the server name in the properties > file but if not set use the server name in the request. Similarly the > port numbers - use the values from the properties file if available. Yep. > There is still a problem with your no-configuration option. When the > user is switched from non-secure to secure for their password how can > you determine the right port number if it isn't configured by the > sysadmin using setup servlet? The quickstart doesn't switch to https. -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
|
From: Jon M. <jo...@te...> - 2006-10-02 13:42:59
|
Matthew Buckett wrote: > The primary advantage is that you no longer have to configure Bodington > to get it running. This makes the quickstart just work. It also means if > you decide to change the hostname that Bodington is deployed under you > don't have to perform any reconfiguration other than to your servlet > container. > So how about one or two extra bodington.properties entries for my use? > Why would you want to serve a Website up under several names? > I can see this may have been an argument 5 years ago when there where > clients that didn't support HTTP/1.0 and so didn't work with virtual > hosts but this is 2006. Hosting a website under multiple domains leaves > you a little exposed to spoofing attacks as users no longer rely on > looking at the URL bar to determine if they are at the correct site. > You may not _want_ to have multiple names but sometimes you don't get a choice. My problem is that the server is also 'localhost' which I was using in my Apache configuration. However the problem for others is that the official name might change - e.g. Bodington Common at Leeds was on www.fldu.leeds.ac.uk but a new name vle.leeds.ac.uk was adopted. The old alias is needed to handle links into the VLE from other web sites but the new name is the official one. The multiple names will also occur if the physical server has multiple functions, e.g. mail.uni.ac.uk, www.uni.ac.uk etc. The configured server name forces the user to access the proper url. > I can see that this is a valid use of the old setup and hadn't though of it. > > It should be reasonably easy to support using the bodington.properties > if they are set and if not falling back the request properties. > That would also require a change to the setup servlet since setting the port numbers and server name seems to be compulsory. > Have you considered using AJP rather than mod_proxy which will preserve > the orginal URLs (I believe) so you don't hit this problem. > > http://tomcat.apache.org/tomcat-5.5-doc/connectors.html > I did and I can't remember why I rejected it. Possible because mod_proxy is very easy to set up. > It was previously an undocumented feature ;-) > O.K., how about this; change the text of the setup servlet to indicate that the server name is only required if the users could access the server using multiple names. Then the code that constructs absolute URLs for inclusion in HTML can use the server name in the properties file but if not set use the server name in the request. Similarly the port numbers - use the values from the properties file if available. There is still a problem with your no-configuration option. When the user is switched from non-secure to secure for their password how can you determine the right port number if it isn't configured by the sysadmin using setup servlet? Jon |
|
From: Sean M. <se...@sm...> - 2006-10-02 11:47:20
|
Cheers, Colin! s. On 2 Oct 2006, at 12:42, Colin Tatham wrote: > 2.8.0 has been released. I'll write an item for the SF newsfeed > today. Here are the release notes > and change log (which can still be edited if we need to): > > Bodington version 2.8.0 > ----------------------- > > Released under the OSI certified Apache 2 license. > > Bodington is a free, institutional scale VLE, implemented and > supported by a wide group of > educational institutions, led by Oxford, UHI and Leeds. More > information can be found at > http://bodington.org. > > This release contains the following three files: > > 1. Bodington License: The OSS License (Apache 2) under which you > can use and develop Bodington. > > 2. bodington_war: This is main Bodington application. To use this, > you should copy bodington.war to > your servlet container's webapp root (you may need to either > restart or reload it, depending on your > container's instructions). You must then create and configure a > supported database before you can > use the Bodington application. > > 3. bodington-quickstart_war: This is a preconfigured version of > bodington.war which uses the > lightweight HSQLDB database. It's designed to get you up and > running with Bodington with the least > possible effort. To use this, you should copy bodington- > quickstart.war to your servlet container's > webapp root (you may need to either restart or reload it, depending > on your container's > instructions). You can then login directly to Bodington using the > sysadmin user account with no > further configuration. This version is not recommended for > production use. > > > > New features: > ------------- > * Support for MySQL database added. > > * Newsfeed display: RSS and Atom newsfeeds can be rendered in a > variety of ways. > > * Peer Marker Tool: Although originally developed for student peer > marking, it is equally applicable > to any summative marking task (e.g. tutor marking). It allows marks > to be moderated or disallowed > and will collate marks across multiple groups of students. > > * QuickLinks: provide links to external sites or to locations > within Bodington (in which case the > link will be automatically updated if the target location is moved). > > Improvements to existing tools: > ------------------------------- > * Questionnaires: improved user interaction, additional question > and paper types, and the ability to > export results to a CSV file. > > * Pigeon Holes: all contents can now be downloaded as a zip file > suitable for submission to a > plagiarism detection service, additional blind marking and peer > marking facilities. > > * Log Books: can now accept QTI 2.0 'questions', and can have > multiple sub-sections. > > * Messaging Rooms: individual messages can be moderated. > > Other: > ------ > * Shibboleth Service Provider (SP) capability, compatible with > Shibboleth and Guanxi IdPs. > > * New 'Evaluate' permission added to simplify granting access to > external evaluators. > > * Improvements to IMS Content Package import and export (v1.1.4). > > * Search box now available at the top of each page. > > * The file upload code has been re-written to improve locking and > concurrency problems. > > * Tracking user accesses to a resource is now possible. > > > > > > Sean Mehan wrote: >> ++2 on making top line in release notes >> >> >> * Bodington 2.8 released under the Apache 2 OSI certified license. >> >> >> On 29 Sep 2006, at 11:15, Adam Marshall wrote: >> >>> Hope I 'm not too late. But we should make it VERY obvious that >>> Bods now has >>> the apache 2 licence. >>> >>> Kit would be good also, Colin, to pen a press release which we >>> give to >>> OSSWatch mentioning the new licence. Perhaps Randy could suggest >>> other >>> places to send the press release. >>> >>> adam >>> >>> | -----Original Message----- >>> | From: bod...@li... >>> | [mailto:bod...@li...] On >>> Behalf Of >>> | Colin Tatham >>> | Sent: 26 September 2006 13:04 >>> | To: Bodington developers >>> | Subject: [Bodington-developers] 2.8.0 release >>> | >>> | I'm about to finalise the 2.8.0 release (it's complete, apart >>> from release >>> | notes and change log). >>> | >>> | * I'm not including a source zip (2.6.0 included one) but it seems >>> | unnecessary. >>> | >>> | * Anyone already written a change log? Otherwise it'll have to >>> be a >>> | summary of what's on the wiki >>> | page for 2.8. >>> | >>> | * Are we happy to re-use the release notes from the previous >>> version (with >>> | minor edits): >>> | >>> | "Bodington is a free, institutional scale VLE implemented and >>> supported by >>> | a wide group of educational >>> | institutions, led by Oxford, UHI, Leeds and Manchester. More >>> information >>> | can be found at >>> | http://bodington.org. >>> | >>> | In the package you will find three files: >>> | >>> | 1. Bodington License: The OSS License under which you can use and >>> develop >>> | Bodington. >>> | >>> | 2. bodington_war: This is main Bodington application. To use >>> this, you >>> | should copy bodington.war to >>> | your servlet container's webapp root (you may need to either >>> restart or >>> | reload it, depending on your >>> | container's instructions). You must then create and configure a >>> supported >>> | database before you can >>> | use the Bodington application. >>> | >>> | 3. bodington-quickstart_war: This is a preconfigured version of >>> | bodington.war which uses the >>> | lightweight HSQLDB database. It's designed to get you up and >>> running with >>> | Bodington with the least >>> | possible effort. To use this, you should copy bodington- >>> quickstart.war to >>> | your servlet container's >>> | webapp root (you may need to either restart or reload it, >>> depending on >>> | your container's >>> | instructions). You can then login directly to Bodington using the >>> sysadmin >>> | user account with no >>> | further configuration. This version is not recommended for >>> production >>> | use." >>> | > > -- > ____________________________________ > Colin Tatham > VLE Team > Oxford University Computing Services > > http://www.oucs.ox.ac.uk/ltg/vle/ > http://bodington.org > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Colin T. <col...@ou...> - 2006-10-02 11:42:15
|
2.8.0 has been released. I'll write an item for the SF newsfeed today. Here are the release notes and change log (which can still be edited if we need to): Bodington version 2.8.0 ----------------------- Released under the OSI certified Apache 2 license. Bodington is a free, institutional scale VLE, implemented and supported by a wide group of educational institutions, led by Oxford, UHI and Leeds. More information can be found at http://bodington.org. This release contains the following three files: 1. Bodington License: The OSS License (Apache 2) under which you can use and develop Bodington. 2. bodington_war: This is main Bodington application. To use this, you should copy bodington.war to your servlet container's webapp root (you may need to either restart or reload it, depending on your container's instructions). You must then create and configure a supported database before you can use the Bodington application. 3. bodington-quickstart_war: This is a preconfigured version of bodington.war which uses the lightweight HSQLDB database. It's designed to get you up and running with Bodington with the least possible effort. To use this, you should copy bodington-quickstart.war to your servlet container's webapp root (you may need to either restart or reload it, depending on your container's instructions). You can then login directly to Bodington using the sysadmin user account with no further configuration. This version is not recommended for production use. New features: ------------- * Support for MySQL database added. * Newsfeed display: RSS and Atom newsfeeds can be rendered in a variety of ways. * Peer Marker Tool: Although originally developed for student peer marking, it is equally applicable to any summative marking task (e.g. tutor marking). It allows marks to be moderated or disallowed and will collate marks across multiple groups of students. * QuickLinks: provide links to external sites or to locations within Bodington (in which case the link will be automatically updated if the target location is moved). Improvements to existing tools: ------------------------------- * Questionnaires: improved user interaction, additional question and paper types, and the ability to export results to a CSV file. * Pigeon Holes: all contents can now be downloaded as a zip file suitable for submission to a plagiarism detection service, additional blind marking and peer marking facilities. * Log Books: can now accept QTI 2.0 'questions', and can have multiple sub-sections. * Messaging Rooms: individual messages can be moderated. Other: ------ * Shibboleth Service Provider (SP) capability, compatible with Shibboleth and Guanxi IdPs. * New 'Evaluate' permission added to simplify granting access to external evaluators. * Improvements to IMS Content Package import and export (v1.1.4). * Search box now available at the top of each page. * The file upload code has been re-written to improve locking and concurrency problems. * Tracking user accesses to a resource is now possible. Sean Mehan wrote: > ++2 on making top line in release notes > > > * Bodington 2.8 released under the Apache 2 OSI certified license. > > > On 29 Sep 2006, at 11:15, Adam Marshall wrote: > >> Hope I 'm not too late. But we should make it VERY obvious that >> Bods now has >> the apache 2 licence. >> >> Kit would be good also, Colin, to pen a press release which we give to >> OSSWatch mentioning the new licence. Perhaps Randy could suggest other >> places to send the press release. >> >> adam >> >> | -----Original Message----- >> | From: bod...@li... >> | [mailto:bod...@li...] On >> Behalf Of >> | Colin Tatham >> | Sent: 26 September 2006 13:04 >> | To: Bodington developers >> | Subject: [Bodington-developers] 2.8.0 release >> | >> | I'm about to finalise the 2.8.0 release (it's complete, apart >> from release >> | notes and change log). >> | >> | * I'm not including a source zip (2.6.0 included one) but it seems >> | unnecessary. >> | >> | * Anyone already written a change log? Otherwise it'll have to be a >> | summary of what's on the wiki >> | page for 2.8. >> | >> | * Are we happy to re-use the release notes from the previous >> version (with >> | minor edits): >> | >> | "Bodington is a free, institutional scale VLE implemented and >> supported by >> | a wide group of educational >> | institutions, led by Oxford, UHI, Leeds and Manchester. More >> information >> | can be found at >> | http://bodington.org. >> | >> | In the package you will find three files: >> | >> | 1. Bodington License: The OSS License under which you can use and >> develop >> | Bodington. >> | >> | 2. bodington_war: This is main Bodington application. To use >> this, you >> | should copy bodington.war to >> | your servlet container's webapp root (you may need to either >> restart or >> | reload it, depending on your >> | container's instructions). You must then create and configure a >> supported >> | database before you can >> | use the Bodington application. >> | >> | 3. bodington-quickstart_war: This is a preconfigured version of >> | bodington.war which uses the >> | lightweight HSQLDB database. It's designed to get you up and >> running with >> | Bodington with the least >> | possible effort. To use this, you should copy bodington- >> quickstart.war to >> | your servlet container's >> | webapp root (you may need to either restart or reload it, >> depending on >> | your container's >> | instructions). You can then login directly to Bodington using the >> sysadmin >> | user account with no >> | further configuration. This version is not recommended for >> production >> | use." >> | -- ____________________________________ Colin Tatham VLE Team Oxford University Computing Services http://www.oucs.ox.ac.uk/ltg/vle/ http://bodington.org |
|
From: Matthew B. <mat...@ou...> - 2006-10-02 08:44:45
|
Jon Maber wrote: > I've found a feature in 2.6 which for me is a bug but may be a bug fix > from someone else's point of view! I saw it as a feature but I can see why you miss it. > The login templates need to use absolute URLs at various points and > these are built in methods of Facility. They used to use the server > name and the port numbers in bodington.properties but now they seem to > always use the server name found in the HTTP request and only use the > port numbers for the jump between http and https and back. I don't > really understand what the advantages of all this are but I can see > several disadvantages, one of which is preventing me setting up > Bodington the way I want. The primary advantage is that you no longer have to configure Bodington to get it running. This makes the quickstart just work. It also means if you decide to change the hostname that Bodington is deployed under you don't have to perform any reconfiguration other than to your servlet container. The properties are still used by the EventMailer as it doesn't have a request object to pull the values from. > 1) Many servers have multiple IP name aliases and this is not a problem > with Bodington when non-secure connections are made. However, when a > secure connection is made the server name really needs to match the IP > name in the server's digital certificate to prevent worrying error > messages about the security popping up in the user's browser. This > seems to be broken - the correct port is used but not the correct IP name. Why would you want to serve a Website up under several names? I can see this may have been an argument 5 years ago when there where clients that didn't support HTTP/1.0 and so didn't work with virtual hosts but this is 2006. Hosting a website under multiple domains leaves you a little exposed to spoofing attacks as users no longer rely on looking at the URL bar to determine if they are at the correct site. I can see that you may have your HTTPS connection served under a completly different hostname to your HTTP connections (http://www.server.name/ and https://secure.server.name/) but the old method didn't support this (it only allowed one hostname). > 2) I'm using a single Apache installation to front end multiple > Tomcats. This is done with virtual hosting in Apache, URL rewriting and > proxying. So Apache accepts requests on port 80 and uses the server > name in the request to identify which tomcat installation to use. Each > Tomcat listens on its own network ports on the localhost device only and > Apache operates like a proxy - the URL is transformed by mapping the > server name to localhost and the port number corresponding to the right > Tomcat installation. Apache fetches the page and sends it to the client. I can see that this is a valid use of the old setup and hadn't though of it. It should be reasonably easy to support using the bodington.properties if they are set and if not falling back the request properties. Have you considered using AJP rather than mod_proxy which will preserve the orginal URLs (I believe) so you don't hit this problem. http://tomcat.apache.org/tomcat-5.5-doc/connectors.html > This is now broken by Bodington - you can log in O.K. (because tomcat > and Apache are on the same server) but when you follow the link to the > originally requested URL it's on the wrong port because it is > constructed from the request headers formed by the proxy instead of from > bodington.properties. E.g. the user asks for > http://myserver.com/bodington/site/ but Apache connects to tomcat using > http://myserver.com:8080/bodington/site/ so after logging the later link > is present on the page when it should be the former. > > So, is this a bug or is it a bug fix? It was previously an undocumented feature ;-) -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
|
From: Jon M. <jo...@te...> - 2006-09-29 17:15:44
|
I've found a feature in 2.6 which for me is a bug but may be a bug fix from someone else's point of view! The login templates need to use absolute URLs at various points and these are built in methods of Facility. They used to use the server name and the port numbers in bodington.properties but now they seem to always use the server name found in the HTTP request and only use the port numbers for the jump between http and https and back. I don't really understand what the advantages of all this are but I can see several disadvantages, one of which is preventing me setting up Bodington the way I want. 1) Many servers have multiple IP name aliases and this is not a problem with Bodington when non-secure connections are made. However, when a secure connection is made the server name really needs to match the IP name in the server's digital certificate to prevent worrying error messages about the security popping up in the user's browser. This seems to be broken - the correct port is used but not the correct IP name. 2) I'm using a single Apache installation to front end multiple Tomcats. This is done with virtual hosting in Apache, URL rewriting and proxying. So Apache accepts requests on port 80 and uses the server name in the request to identify which tomcat installation to use. Each Tomcat listens on its own network ports on the localhost device only and Apache operates like a proxy - the URL is transformed by mapping the server name to localhost and the port number corresponding to the right Tomcat installation. Apache fetches the page and sends it to the client. This is now broken by Bodington - you can log in O.K. (because tomcat and Apache are on the same server) but when you follow the link to the originally requested URL it's on the wrong port because it is constructed from the request headers formed by the proxy instead of from bodington.properties. E.g. the user asks for http://myserver.com/bodington/site/ but Apache connects to tomcat using http://myserver.com:8080/bodington/site/ so after logging the later link is present on the page when it should be the former. So, is this a bug or is it a bug fix? Jon |
|
From: Adam M. <ada...@ou...> - 2006-09-29 14:41:04
|
I should check - private archiving would be best/. adam | -----Original Message----- | From: bod...@li... | [mailto:bod...@li...] On Behalf Of | Peter Crowther | Sent: 29 September 2006 14:56 | To: Bodington developers | Subject: Re: [Bodington-developers] new mail list for jisc bids | | > From: Adam Marshall | > Tet...@ji... | > [note NOT lists.sourceforge.net!!!!] | | Ah, so even slower than SF then. | | I assume it's not archived? | | - Peter | | ------------------------------------------------------------------------- | Take Surveys. Earn Cash. Influence the Future of IT | Join SourceForge.net's Techsay panel and you'll get the chance to share | your | opinions on IT & business topics through brief surveys -- and earn cash | http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV | _______________________________________________ | Bodington-developers mailing list | Bod...@li... | https://lists.sourceforge.net/lists/listinfo/bodington-developers |
|
From: Peter C. <Pet...@me...> - 2006-09-29 13:56:05
|
> From: Adam Marshall > Tet...@ji... > [note NOT lists.sourceforge.net!!!!] Ah, so even slower than SF then. I assume it's not archived? - Peter |
|
From: Adam M. <ada...@ou...> - 2006-09-29 13:31:34
|
I have set up a list for the discussion of 'Tetra' jisc (et al) bids. The list is private and all subs go through me (or colin or sean or ian b). Tet...@ji... [note NOT lists.sourceforge.net!!!!] I have taken the liberty of adding most of the attendees from this week. If you have been subscribed then you should have received a note. If anybody else wishes to join then please go to http://www.jiscmail.ac.uk/lists/tetraelf-private.html and do the necessaries. Please pass this along to anybody you think should be interested. Adam Members: ia...@CA... Ian Boston mat...@OU... Matthew Buckett An...@SM... Antony Corfield pet...@ME... Peter Crowther pau...@OU... Paul Davis I.D...@HU... Ian Dolphin Alu...@UH... Alun Hughes se...@PH... Selwyn Lloyd jo...@TE... Jon Maber ada...@OU... Adam Marshall se...@SM... Sean Mehan how...@OU... Howard Noble jo...@CA... John Norman ale...@OU... Alexis O'Connor cs...@UM... Charles Severance ali...@SM... Alistair Young |
19 messages has been excluded from this view by a project administrator.
