Anonymous avatar Anonymous committed 575eb6b

Comments (0)

Files changed (8)

+<html>
+
+<head>
+
+<title>PropertySet Overview</title>
+
+</head>
+
+<body>
+
+<p><b><strong>PropertySet</strong> </b>is a persistence-agnostic module that can
+
+  be used to fulfill storage requirements in applications that can change constantly.
+
+  An example of this might be a &quot;User Preferences&quot; storage device. It
+
+  may be impossible to know what the user can store at any given time in your
+
+  application's lifecycle, so employing a PropertySet can help. Backed by XML,
+
+  EJB, Ofbiz, JDBC, Castor JDO, or any other persistence mechanism, you can provide
+
+  a complete <strong>typed</strong> key-value pair implementation.</p>
+
+<ul>
+
+  <li><a href="usage.jsp">Usage and Configuration</a></li>
+
+  <li><a href="tips.jsp">Database Tips</a></li>
+
+  <li><a href="api/index.html">JavaDocs API</a></li>
+
+</ul>
+
+<p>To report any bugs or feature requests, please go to <a href="http://jira.opensymphony.com">http://jira.opensymphony.com</a>
+
+  and open a case.</p>
+
+</body>
+
+</html>

docs/index.html

-<html>
-<head>
-<title>OSCore Documentation</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="oscore.css" type="text/css">
-<link rel="stylesheet" href="main.css" type="text/css">
-</head>
-
-<body bgcolor="#FFFFFF" text="#000000">
-<h1>PropertySet Documentation</h1>
-<p><b><strong>PropertySet</strong> </b>is a persistence-agnostic module that can
-  be used to fulfill storage requirements in applications that can change constantly.
-  An example of this might be a &quot;User Preferences&quot; storage device. It
-  may be impossible to know what the user can store at any given time in your
-  application's lifecycle, so employing a PropertySet can help. Backed by XML,
-  EJB, Ofbiz, JDBC, Castor JDO, or any other persistence mechanism, you can provide
-  a complete <strong>typed</strong> key-value pair implementation.</p>
-<ul>
-  <li><a href="usage.html">Usage and Configuration</a></li>
-  <li><a href="tips.html">Database Tips</a></li>
-  <li><a href="api/index.html">JavaDocs API</a></li>
-  <li><a href="http://jira.opensymphony.com/secure/BrowseProject.jspa?id=10002&report=changelog">Change
-    Log</a></li>
-</ul>
-<p>To report any bugs or feature requests, please go to <a href="http://jira.opensymphony.com">http://jira.opensymphony.com</a>
-  and open a case.</p>
-</body>
-
-<content tag="sidebar">
-    <p>
-    <h3>Services</h3>
-    <b>JIRA</b><br>
-    - <a href="http://jira.opensymphony.com/secure/BrowseProject.jspa?id=10040">Issue Overview</a><br>
-    - <a href="http://jira.opensymphony.com/secure/BrowseProject.jspa?id=10040&report=roadmap">Roadmap</a><br>
-    - <a href="http://jira.opensymphony.com/secure/BrowseProject.jspa?id=10040&report=changelog">Changelog</a><br>
-    </p>
-
-</content>
-</html>

docs/main.css

-li, br, div, p {
-	font-family : Verdana,Arial,Helvetica,"MS Sans Serif";
-}
-
-i, b, em, strong {
-	color: #164a7d;
-}
-
-pre,code {
-	color: #164a7d;
-	font-size : 12px;
-}
-
-h1, h2, h3, h4, h5, h6 {
-	color: #164a7d;
-	text-align: left;
-}
-
-a, a:visited{
-	color: #164a7d;
-}
-
-li {
-	padding-bottom: 2pt;
-}
-
-a { }a:visited { }b { }body { 
-	font-family : Verdana, Arial, Helvetica, sans-serif;
-; font-size: 12px } td { 
-	font-family : Verdana, Arial, Helvetica, sans-serif;
-; font-size: 10px } 

docs/navpanel.jsp

+<content tag="sidebar">
+
+    <p>
+    <h3>About</h3>
+    <a href="<%= request.getContextPath() %>/propertyset/">Overview</a><br>
+    <a href="http://sourceforge.net/project/showfiles.php?group_id=9890">Download</a><br>
+    </p>
+
+    <p>
+    <h3>Documentation</h3>
+    <a href="<%= request.getContextPath() %>/propertyset/usage.jsp">Usage and Configuration</a><br>
+    <a href="<%= request.getContextPath() %>/propertyset/tips.jsp">Database Tips</a><br>
+    <a href="<%= request.getContextPath() %>/sitemesh/api/">API Reference</a><br>
+    </p>
+
+    <p>
+    <h3>Services</h3>
+    <b>JIRA</b><br>
+    - <a href="http://jira.opensymphony.com/secure/BrowseProject.jspa?id=10040">Issue Overview</a><br>
+    - <a href="http://jira.opensymphony.com/secure/BrowseProject.jspa?id=10040&report=roadmap">Roadmap</a><br>
+    - <a href="http://jira.opensymphony.com/secure/BrowseProject.jspa?id=10040&report=changelog">Changelog</a><br>
+    <b>Wiki</b><br>
+    - <a href="http://wiki.opensymphony.com/space/PropertySet">PropertySet Page</a>
+    </p>
+
+</content>
+

docs/tips.html

-<html>
-<head>
-<title>OSCore Database Tips</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="main.css" type="text/css">
-</head>
-
-<body bgcolor="#FFFFFF" text="#000000">
-<h1>PropertySet Database Tips </h1>
-<p>Most PropertySet implementations persist data in a relational database. Because 
-  the PropertySet module stores a wide variety of data that is unknown at development 
-  time, the resulting tables are not entirely in optimized (Boyce-Codd) normal 
-  form. Since the schema design is not &quot;optimized&quot; to any sorta of specific 
-  data structures, querying on these tables can be very slow if the database isn't 
-  aware of any functional dependecies. We recommend that you create the following 
-  indices on the OS_PROPERTYENTRY table, which will speed up queries by up to 
-  a factor of 20:</p>
-<pre>	CREATE UNIQUE INDEX os_PropertyEntry_keyidx ON os_PropertyEntry( entityName, entityId, keyValue )
-	CREATE UNIQUE INDEX os_PropertyEntry_allidx ON os_PropertyEntry( entityName, entityId )
-</pre>
-<p><i>Please note that these two SQL calls may or may not work with your database 
-  vendor and you may be required to modify them accordingly. They may or may not 
-  be specific to the propertyset implementation you are using. These indices provide 
-  only a general idea of how you can speed up queries on your PropertySet tables.</i></p>
-<p>Besides indices, another speed optimization to take in to account is the key 
-  names that you choose when writing your application. If all your keys all look 
-  like <i>com.acme.foo</i>, <i>com.acme.bar</i>, and <i>com.acme.baz</i>, your 
-  database may not be able to properly partition data in the OS_PROPERTYENTRY 
-  table accurately. It is recommended that your key values be chosen such that 
-  they are evenly distributed, either by picking names such as <i>foo</i>, <i>bar</i>, 
-  and <i>baz</i> (essentially removing the common prefix), or my using a reverse 
-  key naming convention: <i>oof.emca.moc</i>, <i>rab.emca.moc</i>, and <i>zab.emca.moc</i>. 
-  By properly distributing your keys, your database should be able to have much 
-  faster access to ProperySets.<br>
-</p>
-</body>
-</html>
+<html>
+
+<head>
+
+<title>PropertySet Database Tips</title>
+
+</head>
+
+
+
+<body bgcolor="#FFFFFF" text="#000000">
+
+<p>Most PropertySet implementations persist data in a relational database. Because
+
+  the PropertySet module stores a wide variety of data that is unknown at development
+
+  time, the resulting tables are not entirely in optimized (Boyce-Codd) normal
+
+  form. Since the schema design is not &quot;optimized&quot; to any sorta of specific
+
+  data structures, querying on these tables can be very slow if the database isn't
+
+  aware of any functional dependecies. We recommend that you create the following
+
+  indices on the OS_PROPERTYENTRY table, which will speed up queries by up to
+
+  a factor of 20:</p>
+
+<pre><code>CREATE UNIQUE INDEX os_PropertyEntry_keyidx ON os_PropertyEntry( entityName, entityId, keyValue )
+CREATE UNIQUE INDEX os_PropertyEntry_allidx ON os_PropertyEntry( entityName, entityId )</code></pre>
+
+<p><i>Please note that these two SQL calls may or may not work with your database
+
+  vendor and you may be required to modify them accordingly. They may or may not
+
+  be specific to the propertyset implementation you are using. These indices provide
+
+  only a general idea of how you can speed up queries on your PropertySet tables.</i></p>
+
+<p>Besides indices, another speed optimization to take in to account is the key
+
+  names that you choose when writing your application. If all your keys all look
+
+  like <i>com.acme.foo</i>, <i>com.acme.bar</i>, and <i>com.acme.baz</i>, your
+
+  database may not be able to properly partition data in the OS_PROPERTYENTRY
+
+  table accurately. It is recommended that your key values be chosen such that
+
+  they are evenly distributed, either by picking names such as <i>foo</i>, <i>bar</i>,
+
+  and <i>baz</i> (essentially removing the common prefix), or my using a reverse
+
+  key naming convention: <i>oof.emca.moc</i>, <i>rab.emca.moc</i>, and <i>zab.emca.moc</i>.
+
+  By properly distributing your keys, your database should be able to have much
+
+  faster access to ProperySets.<br>
+
+</p>
+
+  <%@ include file="navpanel.jsp" %>
+
+</body>
+
+</html>

docs/usage.html

-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>PropertySet Usage and Configuration</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link href="main.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>PropertySet Usage and Configuration</h1>
-<p>The PropertSet module is configured by a file that is to be located somewhere 
-  in the classpath of your application. It looks for the folloring files, in this 
-  order:</p>
-<ol>
-  <li>/propertyset.xml</li>
-  <li>/META-INF/propertyset.xml</li>
-  <li>/META-INF/propertyset-default.xml</li>
-</ol>
-<p>The <strong>propertyset-default.xml</strong> file will always be found, as 
-  it is included in <strong>propertyset.jar</strong>. You can override these configurations 
-  by writing your own propertyset.xml file and placing it in one of the above 
-  locations in the classpath. The configuration file must look like this:</p>
-<pre>&lt;propertysets&gt;
-	&lt;propertset name=&quot;baz&quot; class=&quot;com.foo.bar.BazPropertySet&quot;&gt;
-		&lt;arg name=&quot;some&quot; value=&quot;thing&quot;/&gt;
-		...
-	&lt;/propertyset&gt;
-	...
-&lt;/propertysets&gt;
-</pre>
-<p>The code to use the above PropertySet would be:</p>
-<pre>import com.opensymphony.module.propertyset.*;
-...
-
-
-HashMap args = new HashMap();
-// add parameters to the args map
-PropertySet ps = PropertySetManager.getIntance(&quot;baz&quot;, args);
-</pre>
-<p>The values that are placed in the <b>args</b> map is specific to the PropertySet 
-  implementation. We recommend reading the javadocs for the implementation you 
-  plan to use to discover the required and optional configuration arguments in 
-  <b>propertyset.xml</b> as well as the runtime arguments passed in via the <b>args 
-  Map</b> above.<br>
-</p>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+
+<html>
+
+<head>
+
+<title>PropertySet Usage and Configuration</title>
+
+</head>
+
+
+<body>
+
+<p>The PropertSet module is configured by a file that is to be located somewhere
+
+  in the classpath of your application. It looks for the folloring files, in this
+
+  order:</p>
+
+<ol>
+  <li>/propertyset.xml</li>
+  <li>/META-INF/propertyset.xml</li>
+  <li>/META-INF/propertyset-default.xml</li>
+</ol>
+
+<p>The <strong>propertyset-default.xml</strong> file will always be found, as
+
+  it is included in <strong>propertyset.jar</strong>. You can override these configurations
+
+  by writing your own propertyset.xml file and placing it in one of the above
+
+  locations in the classpath. The configuration file must look like this:</p>
+
+<pre><code>&lt;propertysets&gt;
+	&lt;propertset name=&quot;baz&quot; class=&quot;com.foo.bar.BazPropertySet&quot;&gt;
+		&lt;arg name=&quot;some&quot; value=&quot;thing&quot;/&gt;
+		...
+	&lt;/propertyset&gt;
+	...
+&lt;/propertysets&gt;</code></pre>
+
+<p>The code to use the above PropertySet would be:</p>
+
+<pre><code>import com.opensymphony.module.propertyset.*;
+...
+
+HashMap args = new HashMap();
+
+// add parameters to the args map
+
+PropertySet ps = PropertySetManager.getIntance(&quot;baz&quot;, args);
+</code></pre>
+
+<p>The values that are placed in the <b>args</b> map is specific to the PropertySet
+
+  implementation. We recommend reading the javadocs for the implementation you
+
+  plan to use to discover the required and optional configuration arguments in
+
+  <b>propertyset.xml</b> as well as the runtime arguments passed in via the <b>args
+
+  Map</b> above.<br>
+
+</p>
+
+  <%@ include file="navpanel.jsp" %>
+
+</body>
+
+</html>
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.