Planet Opencast > News Feeds
News Feeds
Patching to 1.1
Matterhorn Mailing List - Thu, Sep 2, 2010 10:19am GMT
I just closed a ticket that was on our local install that also effects
1.1: http://opencast.jira.com/browse/MH-5306
I committed the change to our local msub. My question is, do I just
copy the changes over to 1.1, redo the testing with the head of 1.1
branch, and recommit the fix? Or do I assign this to a release manager
and point to the fix I made in our msub of 1.0?
Chris
--
Christopher Brooks, BSc, MSc
ARIES Laboratory, University of Saskatchewan
Web: http://www.cs.usask.ca/~cab938
Phone: 1.306.966.1442
Mail: Advanced Research in Intelligent Educational Systems Laboratory
Department of Computer Science
University of Saskatchewan
176 Thorvaldson Building
110 Science Place
Saskatoon, SK
S7N 5C9
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
Jira Iteration Changes #proposal
Matterhorn Mailing List - Thu, Sep 2, 2010 10:00am GMT
We need a better way to manage what the heck we're doing on an
iteration to iteration basis in Jira. I made some changes that I think
will make jira a better working environment for 1.1, and will prevent us
from getting ahead of ourselves.
I changed all of the "fixed for version 1.1" issues to product backlog
and tagged them as "frmrly_1dot1". Why? Because there were 300 issues
listed, so it was basically impossible to understand the scope of 1.1
and what we're currently doing. You can still access the former list
here http://bit.ly/frmr_1-1
I will send a subsequent proposal detailing prioritization process
changes that will better define how issues make it into an upcoming
iteration.
No more "what iteration number are we on?" or "what is in this
iteration?" Now if you click on fix version 1.1 you'll only find a much
smaller list of issues designated for the current iteration. This list
will become more detailed as we approach an upcoming iteration and will
ultimately be finalized out after the new iteration's Tuesday team
meeting. A nice bonus for this approach is that we don't have to
pollute Jira with "iteration versions", since our future work may or may
not involve iterations. Iterations are strictly an artifact of our
current "project mode". If the community wants to know what our road
map looks like for 1.1, they would go to http://bit.ly/1-1release to
find all of the opened/resolved/closed stories/tasks/bugs for 1.1.
I would also like to unassign any existing assignments. Many of the
tasks assigned to people are historical and have no bearing on 1.1. By
wiping the slate clean, it will help resources as well as the community
gage the "real workload" for a given iteration. If this is cool with
everyone (which I hope it is), when I unassign tasks I'll make sure not
to touch anything "in progress". Stories will sign be assigned to the
proper product owners.
I hope you didn't find this too convoluted. I think it will really
help us with managing 1.1 work!
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
Code Review Comments (Capture Agent)
Matterhorn Mailing List - Thu, Sep 2, 2010 7:20am GMT
Hi all,
A couple of months ago I reviewed the capture agent codebase and have
just gotten around to posting things on to Jira tickets now. There are
some broad comments that I think might be helpful for all developers though:
1. Don't use magic numbers. If you are multiplying by one thousand to
change seconds into ms create a constant at the top of the file called
static final int MILLISECONDS = 1000 or something similar. Note, this
isn't just for number, it's for magic strings or objects too. So if you
always convert to one date format, make the date formatter a member
variable and static final or something similar.
2. Comments are not just for headers of methods, but also tricky bits
inside of the method. Headers usually have blackbox comments ("X does
Y") and inline comments are usually whitebox comments ("Y is done by Z1,
then Z2, then Z3).
3. Log4j and it's many facades can take a throwable as a parameter,
which gives nice flexibility as appenders can decide what to do with
stack traces. So don't do logger.debug("my message", e.getMessage()),
instead, do logger.debug("my message", e).
4. Don't rely on clone() to do a deep copy, it rarely does! Instead,
the pattern for this is to serialize the object using object
serialization to a byte array (or similar) in memory then deserialize it
from memory. This will deep clone. The CA was incorrectly cloning
property files with properties.clone() in many places.
5. If you are doing a bunch of things only in debug mode do something like:
if ( logger.debugEnabled() ){
//all my debug code here
}
This is used in various places in the CA where trace level debugging
does something else (like provide memory counts of gstreamer objects).
If the item is dangerous (as is the case with the CA, since it seems to
break things once and awhile) or really slow, do it in the
logger.traceEnabled/debugEnabled blocks. If you're just logging one
line, don't bother, since .debug() calls is debugEnabled anyways.
Regards,
Chris
--
Christopher Brooks, BSc, MSc
ARIES Laboratory, University of Saskatchewan
Web: http://www.cs.usask.ca/~cab938
Phone: 1.306.966.1442
Mail: Advanced Research in Intelligent Educational Systems Laboratory
Department of Computer Science
University of Saskatchewan
176 Thorvaldson Building
110 Science Place
Saskatoon, SK
S7N 5C9
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-4843) Recordings-All should show Failed status in same way as Recordings-Failed
Matterhorn Mailing List - Thu, Sep 2, 2010 4:36am GMT
[ http://opencast.jira.com/browse/MH-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20972#action_20972 ]
Judy Stern commented on MH-4843:
--------------------------------
Yes, still a problem. The word "Failed" is still missing on the All tab. So if you look at the status column, you can't see that it's failed. It just says, for example "Inspecting the Media Package".
> Recordings-All should show Failed status in same way as Recordings-Failed
> -------------------------------------------------------------------------
>
> Key: MH-4843
> URL: http://opencast.jira.com/browse/MH-4843
> Project: Matterhorn Project
> Issue Type: Task
> Components: Administrative Tools
> Affects Versions: 1.0.0
> Reporter: Judy Stern
> Assignee: Benjamin Wulff
> Fix For: 1.1 , Product Backlog
>
>
> right now, e.g. failed status on All for one recording is "failed : Cleaning up after failure", whereas the same recording on Failed tab has status "Error: Inspecting the media package"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-5273) In the CA scripts, if the build fails, the whole installation have to be resumed
Matterhorn Mailing List - Thu, Sep 2, 2010 2:26am GMT
[ http://opencast.jira.com/browse/MH-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20971#action_20971 ]
Christopher Brooks commented on MH-5273:
----------------------------------------
Seems pretty reasonable to me!
> In the CA scripts, if the build fails, the whole installation have to be resumed
> --------------------------------------------------------------------------------
>
> Key: MH-5273
> URL: http://opencast.jira.com/browse/MH-5273
> Project: Matterhorn Project
> Issue Type: Task
> Components: Capture (Devices and Software)
> Affects Versions: 1.0.x (branch)
> Reporter: Rubén Pérez Vázquez
> Assignee: Rubén Pérez Vázquez
> Priority: Minor
> Fix For: 1.0.x (branch), 1.1
>
>
> We'd certainly could use of a feature in the capture install scripts to restart the build in case if fails, instead of resuming all the installation. In our Atom box, it's painful since it takes a lot to re-run the whole process.
> It doesn't take so much to include a question "Do you wish to retry?" after a failed build for the user to decide if they want to try again (because, for instance, a temporary failure in the internet connection prevented maven from downloading necessary sources). As the compilation is done in install.sh (and not in one of the subsidiary scripts), we could even go back to where the source is downloaded, so that the user could choose other url and re-download the code again.
> How does that sound to you?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-2737) As a learner, I want to create a custom atom/rss feed so that I can view media that matters to me.
Matterhorn Mailing List - Thu, Sep 2, 2010 2:12am GMT
[ http://opencast.jira.com/browse/MH-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20970#action_20970 ]
Tona Monjo commented on MH-2737:
--------------------------------
I've begun working in some mockups that contain proposals for the main requirements of this task:
- The user should be able to subscribe to the search results
- Related videos (by series, professor, topics or author) should be easily available.
The mockups (in progress) are available here: http://opencast.jira.com/wiki/display/MH/Custom+Atom_RSS+Feed+%28A%29
They are an evolving document, because I'll continue working on them the next days. All comments will be welcome!
> As a learner, I want to create a custom atom/rss feed so that I can view media that matters to me.
> --------------------------------------------------------------------------------------------------
>
> Key: MH-2737
> URL: http://opencast.jira.com/browse/MH-2737
> Project: Matterhorn Project
> Issue Type: Story Card
> Components: Distribution
> Reporter: Adam Hochman
> Assignee: Tona Monjo
> Fix For: 1.1 , Product Backlog
>
>
> -Latest Episodes (of all distributed media entries)
> -Latest episodes of one Series (series rss associated with each distributed media entry)
> -A custom selection of episodes (full text search)
> see http://opencast.jira.com/wiki/display/MH/Atom+and+RSS+Feeds
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[Opencast] Lecture capture: rich and strange, or a dark art?
Community Mailing List - Thu, Sep 2, 2010 2:02am GMT
Some interesting analysis:
http://eprints.lse.ac.uk/29184/
Secker, Jane and Bond, Steve and Grussendorf, Sonja (2010) Lecture capture:
rich and strange, or a dark art? In: ALT-C 2010, 6-9 September 2010,
University of Nottingham. (Unpublished)
Tim
_______________________________________________
Community mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/community
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-5289) Test deployment using a bridged http service
Matterhorn Mailing List - Thu, Sep 2, 2010 12:42am GMT
[ http://opencast.jira.com/browse/MH-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20969#action_20969 ]
Josh Holtzman commented on MH-5289:
-----------------------------------
See http://felix.apache.org/site/apache-felix-http-service.html#ApacheFelixHTTPService-UsingtheServletBridge
> Test deployment using a bridged http service
> --------------------------------------------
>
> Key: MH-5289
> URL: http://opencast.jira.com/browse/MH-5289
> Project: Matterhorn Project
> Issue Type: Sub-Task
> Components: Architecture & Services Design/Impl
> Affects Versions: 1.1
> Reporter: Josh Holtzman
> Fix For: 1.1
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-5202) A command line workflow handler to exec to third party programs would be helpful for migration/integration
Matterhorn Mailing List - Thu, Sep 2, 2010 12:12am GMT
[ http://opencast.jira.com/browse/MH-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20968#action_20968 ]
Adam Hochman commented on MH-5202:
----------------------------------
is this done?
> A command line workflow handler to exec to third party programs would be helpful for migration/integration
> ----------------------------------------------------------------------------------------------------------
>
> Key: MH-5202
> URL: http://opencast.jira.com/browse/MH-5202
> Project: Matterhorn Project
> Issue Type: Community Feature Request
> Components: Architecture & Services Design/Impl
> Affects Versions: 1.0.0
> Reporter: Christopher Brooks
> Assignee: Josh Holtzman
> Fix For: 1.1
>
> Attachments: MH5202.diff
>
>
> This is particularly useful in that declarative workflows could be made for some simple tasks (copying files, etc.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
Reminder Team Meeting Canceled Today
Matterhorn Mailing List - Thu, Sep 2, 2010 12:08am GMT
The product owner's will use this time for 1.1 planning. We'll kick
off our first iteration at Tuesday's meeting.
~Adam
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-4998) Add new CC button for off status
Matterhorn Mailing List - Thu, Sep 2, 2010 12:04am GMT
[ http://opencast.jira.com/browse/MH-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20966#action_20966 ]
Arantxa Hernandez commented on MH-4998:
---------------------------------------
Another idea:
icon does not appear if you have no title, I think this is a great solution, but it is also possible to add a symbol "x" next to the letters "CC", for example, in gray. This solution is very similar to that adopted in Youtube to turn off the sound, see the symbol "x" in red ...
Added a quick example: "CC_Unavailable.png"
> Add new CC button for off status
> --------------------------------
>
> Key: MH-4998
> URL: http://opencast.jira.com/browse/MH-4998
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Engage Tools
> Affects Versions: 1.0.0
> Reporter: Clemens Gruber
> Assignee: Arantxa Hernandez
> Fix For: 1.1 , Product Backlog
>
> Attachments: Color_Specs.png, OC_CC_Available.png, OC_CC_Blue.png, OC_CC_Depressed.png
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
Thank you!
Matterhorn Mailing List - Wed, Sep 1, 2010 9:33pm GMT
Hi Matterhornies!
Since September 1st I am no longer employed at the University of
Osnabrueck. This means also that the time I will and can spend in
Matterhorn and Opencast will be reduced to an amount of scanning some
parts but no more active working.
So I like to say sincere thank you! For all that creative input, for the
inspiring discussions, the professional work and organization and--of
cause not least, this it one of the things I really love the last
year--the heartily ambience in the project! It was a great pleasure to
work with you all!
Thank you so much!
Kind regards
Clemens
P.S.: If you have questions about my work in Matterhorn please contact
in the future Markus <[hidden email]> or Ruediger <[hidden email]>
--
Clemens Gruber (Dipl.-Psychologe)
Zentrum fuer Informationsmanagement
und virtuelle Lehre der Universitaet Osnabrueck (virtUOS)
Heger-Tor-Wall 12, Raum 42/209, D-49074 Osnabrueck
E-Mail: [hidden email]
URL: http://www.virtuos.uni-osnabrueck.de
Telefon: (05 41) 969-6505 oder
(05 41) 969-6501 (Sekretariat)
Fax: (05 41) 969-16505
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-5288) Setting frame rates to a value of 20 result in failed captures
Matterhorn Mailing List - Wed, Sep 1, 2010 10:06am GMT
[ http://opencast.jira.com/browse/MH-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20964#action_20964 ]
Brian Bolt commented on MH-5288:
--------------------------------
Hi Chris,
Yes, I can reproduce the condition reliably.
Brian
Brian Bolt
Office of Information Technology
Boise State University
208.426.6835
[hidden email]
On Wed, Sep 1, 2010 at 5:52 PM, Christopher Brooks (JIRA) <
> Setting frame rates to a value of 20 result in failed captures
> --------------------------------------------------------------
>
> Key: MH-5288
> URL: http://opencast.jira.com/browse/MH-5288
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Capture (Devices and Software)
> Affects Versions: 1.0.0
> Reporter: Brian Bolt
> Assignee: Christopher Brooks
> Priority: Minor
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-5263) [Distributed Deployment] The "view info" screen in the admin UI shows blank fields
Matterhorn Mailing List - Wed, Sep 1, 2010 9:42am GMT
[ http://opencast.jira.com/browse/MH-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20962#action_20962 ]
Josh Holtzman commented on MH-5263:
-----------------------------------
This is caused by the same problem described in MH-5280 (302 redirect caused by misconfigured storage URL).
> [Distributed Deployment] The "view info" screen in the admin UI shows blank fields
> ----------------------------------------------------------------------------------
>
> Key: MH-5263
> URL: http://opencast.jira.com/browse/MH-5263
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Administrative Tools
> Affects Versions: 1.0.0
> Reporter: Rubén Pérez Vázquez
> Assignee: Adam Hochman
> Fix For: 1.0.x (branch)
>
> Attachments: Captura-de-pantalla.png, headers4.png
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-5280) [Distributed Deployment] Can't preview recordings "on hold"
Matterhorn Mailing List - Wed, Sep 1, 2010 9:40am GMT
[ http://opencast.jira.com/browse/MH-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20961#action_20961 ]
Josh Holtzman commented on MH-5280:
-----------------------------------
The HTTP return codes indicate that your requests are being redirected (302) because you are not logged in. This is because not all of your servers have the same "org.opencastproject.file.repo.url" configuration value.
In config.properties, you'll see this comment:
# The base URL of the file server. When using a shared filesystem between servers, set all servers to use the same URL.
#org.opencastproject.file.repo.url=${org.opencastproject.server.url}
Ensure that you uncomment that line and set it to a constant on all of your servers. This way, URLs will always point to a "main" file server, even though the other servers have direct access to the filesystems.
> [Distributed Deployment] Can't preview recordings "on hold"
> -----------------------------------------------------------
>
> Key: MH-5280
> URL: http://opencast.jira.com/browse/MH-5280
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Architecture & Services Design/Impl
> Affects Versions: 1.0.x (branch)
> Reporter: Rubén Pérez Vázquez
> Assignee: Josh Holtzman
> Fix For: 1.0.x (branch)
>
> Attachments: headers1.png, headers2.png, headers3.png, javascript_error.png, player_error.png
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
[JIRA Studio] Commented: (MH-5261) Form Components Need to Register Themselves in Scheduler UI
Matterhorn Mailing List - Wed, Sep 1, 2010 4:02am GMT
[ http://opencast.jira.com/browse/MH-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20960#action_20960 ]
Micah Sutton commented on MH-5261:
----------------------------------
r8802 and 8803 should solve this issue. Please see code review.
> Form Components Need to Register Themselves in Scheduler UI
> -----------------------------------------------------------
>
> Key: MH-5261
> URL: http://opencast.jira.com/browse/MH-5261
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Administrative Tools
> Affects Versions: 1.0.x (branch)
> Reporter: Adam Hochman
> Assignee: Micah Sutton
> Priority: Critical
> Fix For: 1.0.x (branch)
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opencast.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
Team Meeting Agenda for September 7th
Matterhorn Mailing List - Wed, Sep 1, 2010 3:05am GMT
Hi,
Here is an agenda item for the September 7th team meeting (next
tuesday). Just for a little experiment, please consider replying to
this thread to add more agenda items then it should be easy for us to
build agenda's.
Chris (10 mins): Requirements for engage visual/non-visual plugins (see
http://opencast.jira.com/wiki/display/MH/Engage+Player-Side+API )
Chris
--
Christopher Brooks, BSc, MSc
ARIES Laboratory, University of Saskatchewan
Web: http://www.cs.usask.ca/~cab938
Phone: 1.306.966.1442
Mail: Advanced Research in Intelligent Educational Systems Laboratory
Department of Computer Science
University of Saskatchewan
176 Thorvaldson Building
110 Science Place
Saskatoon, SK
S7N 5C9
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
User details in the UI
Matterhorn Mailing List - Wed, Sep 1, 2010 1:17am GMT
The security system In Matterhorn 1.0 works well for restricting access
to URLs, but it turns out that it's incapable of displaying information
about the current user. This has to do with the way that we integrated
OSGI's standard web security mechanism, HttpContext.handleSecurity(request,
response), with spring security, which clears the ThreadLocal
containing the user details by the time our servlet code is invoked.
To fix this problem, I had to make some slight changes in the way we
register UIs. I will update the relevant docs in the wiki over the
next few days to include these chages:
* UIs registered via declarative services are now published as 'javax.servlet.Servlet's rather than 'org.opencastproject.http.StaticResource's. This aligns better with how most OSGI-based apps function. <provide interface="org.opencastproject.http.StaticResource" /> becomes <provide interface="javax.servlet.Servlet" />
* UIs must include the ID of the shared http context. This is done by adding the following to your service registration:
<property name="contextId" value="opencast.httpcontext" />
*
UIs may also be registered manually, too, and we are no longer required
to obtain a reference to the HttpService and HttpContext. This is
significantly simpler than the previous technique.
// Register a UI (TODO: move the details into a utility method)
Dictionary<String, String> props = new Hashtable<String, String>();
props.put("contextId", SharedHttpContext.HTTP_CONTEXT_ID);
props.put("alias", "/my/servlet/url");
ServiceRegistration reg = bundleContext.registerService(Servlet.class.getName(), new MyServlet(), props);
// Unregister the UI
reg.unregister();
What
do we get out of these changes? See the attached screenshots, which
show the current username in the logout link, and the contents of the
/info/rest/me.json operation.
A few more notes for developers working on the trunk:
* Please update your config.properties and security.xml files
* Please clear your entire felix cache
*
Please take note that the /info.json servlet has been removed. Its
functionality is available via the /info/rest/components.json endpoint
Please share your questions, concerns, and comments here, or line-by-line in the Crucible code review at http://opencast.jira.com/source/cru/CR-MH-26
Thanks!
Josh
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
log_out.png (42K) Download Attachment
me.json.png (101K) Download Attachment
Dev Meeting Tomorrow: 8:30
Matterhorn Mailing List - Tue, Aug 31, 2010 4:54pm GMT
Hi all,
Since our meetings times are still a bit in flux and the PO is still
working through 1.1 details, tomorrow's meeting may end up being a bit
disorganized/unproductive. We can always cut out early, but I imagine
there is plenty to discuss regarding experience with local
installations, and outstanding maintenance issue. I don't have any
agenda items off hand, but please add some in thread. By next week,
we'll have a defined iteration and be ready to go.
~Adam
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
Kristofor and Greg
Matterhorn Mailing List - Tue, Aug 31, 2010 7:54am GMT
Hi all,
Today is the last full time day for Kristofor and Greg on our local
team. Kris is going back to full time study though I hope will continue
to contribute, and Greg is dropping to part time work on the capture
agent and technical support side of things for 1.1.
Both have done an amazing job, please join me in thanking them for the
hard work and quality contributions to Matterhorn!
Chris
--
Christopher Brooks, BSc, MSc
ARIES Laboratory, University of Saskatchewan
Web: http://www.cs.usask.ca/~cab938
Phone: 1.306.966.1442
Mail: Advanced Research in Intelligent Educational Systems Laboratory
Department of Computer Science
University of Saskatchewan
176 Thorvaldson Building
110 Science Place
Saskatoon, SK
S7N 5C9
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[hidden email]
_______________________________________________
