You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by da...@apache.org on 2005/07/06 18:40:34 UTC
svn commit: r209477 - in /cocoon/whiteboard/osgi: README configuration/
configuration/config.ini legal/eclipse-licence.html
org.eclipse.osgi_3.1.0.jar
Author: danielf
Date: Wed Jul 6 09:40:32 2005
New Revision: 209477
URL: http://svn.apache.org/viewcvs?rev=209477&view=rev
Log:
Trying to run the bundles under Eclipse OSGi but the cocoon_servlet bundle doesn't start and I hav not found out how to be able to see any error messages :/, see the end of the README for details
Added:
cocoon/whiteboard/osgi/configuration/
cocoon/whiteboard/osgi/configuration/config.ini
cocoon/whiteboard/osgi/legal/eclipse-licence.html (with props)
cocoon/whiteboard/osgi/org.eclipse.osgi_3.1.0.jar (with props)
Modified:
cocoon/whiteboard/osgi/README
Modified: cocoon/whiteboard/osgi/README
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/osgi/README?rev=209477&r1=209476&r2=209477&view=diff
==============================================================================
--- cocoon/whiteboard/osgi/README (original)
+++ cocoon/whiteboard/osgi/README Wed Jul 6 09:40:32 2005
@@ -82,3 +82,25 @@
cocoon_testcase - creates the BlocksManager testcase and register it
in the junit service.
+Using the Eclipse OSGi framework
+================================
+
+The Eclipse OSGi is started with:
+
+$ java -Djava.endorsed.dirs=../trunk/lib/endorsed/ -jar org.eclipse.osgi_3.1.0.jar -clean -configuration file:configuration -console
+
+it loads everything as it is supposed to but fails with starting the
+cocoon_servlet bundle. And this far I haven't found any way to get any
+log messages :/
+
+Part of the problem is that the Knopflerfish log and http service
+bundles that I use are designed to be interacted with through
+Knopflerfish's console service. But I have not succeeded in using
+Knopflerfish's console service together with Eclipse. If I use it
+whithout "-console", the framework loads everything and exits, and
+with "-console", the Eclipse OSGi console and the Knopflerfish console
+are running at the same time which is highly confusing.
+
+Runtime options for Eclipse OSGi ca be found in
+http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html.
+
Added: cocoon/whiteboard/osgi/configuration/config.ini
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/osgi/configuration/config.ini?rev=209477&view=auto
==============================================================================
--- cocoon/whiteboard/osgi/configuration/config.ini (added)
+++ cocoon/whiteboard/osgi/configuration/config.ini Wed Jul 6 09:40:32 2005
@@ -0,0 +1,61 @@
+# Eclipse runtime configuration file
+# This file contains a number of key/value pairs that are merged into the
+# System properties on system startup. The values control the way the
+# runtime is structured and runs.
+
+# Note: Only platform:/base/ and file: URLs are supported. In general the
+# URLs given may include a version number (e.g., .../location_1.2.3).
+# If a version is not specified, the system binds
+# to the location which matches exactly or to the versioned location with the
+# latest version number. If a version number is given then only exact matches
+# are considered.
+
+# The URL for the runtime entry point. The default value is
+# platform:/base/plugins/org.eclipse.osgi
+#osgi.framework=platform:/base/plugins/org.eclipse.osgi
+
+# The classpath for the framework found at the osgi.framework location. This
+# comma-separated list contains either URLs or simple element names. Simple
+# names are assumed to be relative to the framework's install directory.
+# Typically this value need not be set as it is initialized by the framework itself.
+# Version match searching is not done for URLs listed here.
+#osgi.frameworkClassPath =
+
+# The comma-separated list of locations to search for the splash screen file (splash.bmp).
+# For each list element a subdirectory structure based on the pattern nl/<locale> is searched.
+# The system binds to the first matching file. There is no default value.
+#osgi.splashPath=
+
+# The location of the splash screen file. If this value is set at system startup it is used
+# in favour of the osgi.splashPath searching outlined above. If the value is not set
+# the searching is done and this key is bound to the result of the search.
+#osgi.splashLocation =
+
+# The comma-separated list of bundles which are automatically installed and optionally started
+# once the system is up and running. Each entry if of the form
+# <URL | simple bundle location>[@ [<startlevel>] [":start"]]
+# If the startlevel is omitted then the framework will use the default start level for the bundle.
+# If the "start" tag is added then the bundle will be marked as started after being installed.
+# Simple bundle locations are interepreted as relative to the framework's parent directory.
+# The startlevel indicates the OSGi start level at which the bundle should run.
+# If this value is not set, the system computes an appropriate default.
+osgi.bundles=http://www.knopflerfish.org/releases/1.3.3/jars/log/log_all-1.0.0.jar@1:start,http://www.knopflerfish.org/releases/1.3.3/jars/cm/cm_api-1.0.0.jar@1,http://www.knopflerfish.org/releases/1.3.3/jars/console/console_api-1.0.0.jar@1,file:jars/cocoon/cocoon_all-1.0.0.jar@2,http://www.knopflerfish.org/releases/1.3.3/jars/http/http_all-1.1.0.jar@4:start,file:jars/cocoon_webapp/cocoon_webapp-1.0.0.jar@7,file:jars/cocoon_servlet/cocoon_servlet-1.0.0.jar@8:start
+
+# The product to run. A given Eclipse configuration may contain many products.
+# The product identified will supply the branding (window icons, title bar text) etc
+# as well as define the default application to run.
+#eclipse.product=
+
+# The application to run. The value specified here is the id of the application extension
+# the runtime will find, instantiate and execute once the system is up. Note that typically
+# the identified eclipse.product defines the default application to run.
+#eclipse.application=
+
+# The build identifier
+eclipse.buildId=I20050627-1435
+
+# HTTP Service properties
+org.osgi.service.http.port=8816
+
+# End of file marker - must be here
+eof=eof
Added: cocoon/whiteboard/osgi/legal/eclipse-licence.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/osgi/legal/eclipse-licence.html?rev=209477&view=auto
==============================================================================
--- cocoon/whiteboard/osgi/legal/eclipse-licence.html (added)
+++ cocoon/whiteboard/osgi/legal/eclipse-licence.html Wed Jul 6 09:40:32 2005
@@ -0,0 +1,79 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
+<title>Eclipse.org Software User Agreement</title>
+</head>
+
+<body lang="EN-US" link=blue vlink=purple>
+<h2>Eclipse Foundation Software User Agreement</h2>
+<p>March 17, 2005</p>
+
+<h3>Usage Of Content</h3>
+
+<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
+ (COLLECTIVELY "CONTENT"). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
+ CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE
+ OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
+ NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
+ CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
+
+<h3>Applicable Licenses</h3>
+
+<p>Unless otherwise indicated, all Content made available by the Eclipse Foundation is provided to you under the terms and conditions of the Eclipse Public License Version 1.0
+ ("EPL"). A copy of the EPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+ For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse.org CVS repository ("Repository") in CVS
+ modules ("Modules") and made available as downloadable archives ("Downloads").</p>
+
+<ul>
+ <li>Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"), plug-in fragments ("Fragments"), and features ("Features").</li>
+ <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java™ ARchive) in a directory named "plugins".</li>
+ <li>A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Each Feature may be packaged as a sub-directory in a directory named "features". Within a Feature, files named "feature.xml" may contain a list of the names and version numbers of the Plug-ins
+ and/or Fragments associated with that Feature.</li>
+ <li>Features may also include other Features ("Included Features"). Within a Feature, files named "feature.xml" may contain a list of the names and version numbers of Included Features.</li>
+</ul>
+
+<p>The terms and conditions governing Plug-ins and Fragments should be contained in files named "about.html" ("Abouts"). The terms and conditions governing Features and
+Included Features should be contained in files named "license.html" ("Feature Licenses"). Abouts and Feature Licenses may be located in any directory of a Download or Module
+including, but not limited to the following locations:</p>
+
+<ul>
+ <li>The top-level (root) directory</li>
+ <li>Plug-in and Fragment directories</li>
+ <li>Inside Plug-ins and Fragments packaged as JARs</li>
+ <li>Sub-directories of the directory named "src" of certain Plug-ins</li>
+ <li>Feature directories</li>
+</ul>
+
+<p>Note: if a Feature made available by the Eclipse Foundation is installed using the Eclipse Update Manager, you must agree to a license ("Feature Update License") during the
+installation process. If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or
+inform you where you can locate them. Feature Update Licenses may be found in the "license" property of files named "feature.properties" found within a Feature.
+Such Abouts, Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in
+that directory.</p>
+
+<p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
+OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
+
+<ul>
+ <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li>
+ <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
+ <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li>
+ <li>IBM Public License 1.0 (available at <a href="http://oss.software.ibm.com/developerworks/opensource/license10.html">http://oss.software.ibm.com/developerworks/opensource/license10.html</a>)</li>
+ <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li>
+ <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li>
+</ul>
+
+<p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License is provided, please
+contact the Eclipse Foundation to determine what terms and conditions govern that particular Content.</p>
+
+<h3>Cryptography</h3>
+
+<p>Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to
+ another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
+ possession, or use, and re-export of encryption software, to see if this is permitted.</p>
+
+<small>Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.</small>
+</body>
+</html>
Propchange: cocoon/whiteboard/osgi/legal/eclipse-licence.html
------------------------------------------------------------------------------
svn:keywords = Id
Added: cocoon/whiteboard/osgi/org.eclipse.osgi_3.1.0.jar
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/osgi/org.eclipse.osgi_3.1.0.jar?rev=209477&view=auto
==============================================================================
Binary file - no diff available.
Propchange: cocoon/whiteboard/osgi/org.eclipse.osgi_3.1.0.jar
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream