Hi Folks,

I have a fix for the YouTube Distribution problem. It involves using an OSGI Bundle that contains both the javax.mail and java.activation (JAF) jars. It also appears to be necessary to embed that bundle in the YouTubeDistribution bundle.

The critical insight for this fix came from Felix Meschberger's response to an email I sent to the Apache Felix Users' list. After that, I found Carl Hall's OSGI bundle that embodies the fix - see below.

Ironically, that exact combined jar that we need was built three years ago for the Sakai Nakamura project that I just came off of to work on Matterhorn. Took a lot of Googling to find it though.

See Carl Hall's blog: http://thecarlhall.wordpress.com/2009/10/27/javamail-in-osgi/

For this to work I think we need to remove the geronimo-mail and geronimo-activation bundles and use the combined bundle in their place. This would happen in:
1) the system.properties file
2) the matterhorn-runtime-dependencies pom
3) the matterhorn-kernel bundle
4) the matterhorn-distribution-service-youtube bundle
5) likely the matterhorn-conductor bundle although this one still uses the org.apache.servicemix.bundles.javax.mail bundle. Not sure why - historical reasons perhaps?

Several issues arise with this fix that I, as a new developer, would like some feedback on: 1) Can this fix go into the 1.4 release? UC Berkeley would like to see it in the release as YouTube is one of our main distribution points. 2) Related to #1, regression testing - I am not sure that I know the app well enough to do that comprehensively. I do know it fixes the YouTube problem and seems low risk. 3) Handling and use of the combined Bundle itself. Here is a pom.xml entry for it:
    <dependency>
      <groupId>org.sakaiproject.nakamura</groupId>
      <artifactId>javax.activation-mail</artifactId>
      <version>1.1.1.1.4.2-1.3.0</version>
    </dependency>

   The options I see for use of it are:

     * Install the bundle in the Matterhorn maven repository - my
       preferred option
     * Add the Sakai repository to our list of maven repositories and
       pull it from there
     * Build a new bundle from scratch that will be a matterhorn bundle

   I did chat with Carl Hall, the developer who built it and is a
   former colleague of mine from the Sakai Nakamura project.  He said
   that licensing will permit option 1 and he agreed with me that
   having control over it, e.g. installing it in the Mattehorn repo, is
   probably the best option.

4) What to do about the matterhorn-composer use of the service-mix mail bundle?

There may likely be other issues I am overlooking so please address any you see.

Thanks in advance for feedback.

--
John King
Applications Programmer
Learning Systems Group
Educational Technology Services
9 Dwinelle Hall - Mail
117 Dwinelle Hall - Office
University of California
Berkeley, CA 94720-2535
Phone: 510-529-5074
Email: [email protected]

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to