[dna-commits] DNA SVN: r994 - trunk/docs/reference/src/main/docbook/en-US/content.

Author: bcarothers Date: 2009-06-07 20:52:09 -0400 (Sun, 07 Jun 2009) New Revision: 994 Modified: trunk/docs/reference/src/main/docbook/en-US/content/environment.xml trunk/docs/reference/src/main/docbook/en-US/content/introduction.xml Log: Added in references to REST subprojects and cleaned up some security info/examples Modified: trunk/docs/reference/src/main/docbook/en-US/content/environment.xml =================================================================== --- trunk/docs/reference/src/main/docbook/en-US/content/environment.xml 2009-06-08 00:18:10 UTC (rev 993) +++ trunk/docs/reference/src/main/docbook/en-US/content/environment.xml 2009-06-08 00:52:09 UTC (rev 994) @@ -125,15 +125,16 @@ </para> <programlisting> &ExecutionContext; context1 = new &ExecutionContext;(); +String jaasRealm = ...; -// Create a context for a user, authenticating using JAAS ... -&LoginContext; loginContext = new LoginContext("username",callbackHandler); -&ExecutionContext; context2 = context1.with(new LoginContext("username")); +// Create a context for a user, authenticating using a JAAS LoginContext... +char[] password = "password".toCharArray(); +&SecurityContext; securityContext = new JaasSecurityContext(jaasRealm, "username", password); +&ExecutionContext; context2 = context1.with(securityContext); // Create a context for the same user, authenticating using JAAS, and using a different callback handler ... &CallbackHandler; callbackHandler = ... -&LoginContext; loginContext = new LoginContext("username",callbackHandler); -&ExecutionContext; context3 = context1.with(loginContext); +&ExecutionContext; context3 = context1.with(new JaasSecurityContext(jaasRealm, callbackHandler); // Create a context that uses a provided &SecurityContext; (see the <link linkend="security">next section</link>)... &SecurityContext; mySecurityContext = ... @@ -185,7 +186,7 @@ </para> <para> There are quite a few JAAS providers available, but one of the best and most powerful providers is - <ulink url="http://www.jboss.org/jbosssecurity/">JBoss Security</ulink>, which is the open source + <ulink url="http://www.jboss.org/jbosssecurity/">JBoss Security</ulink>, the open source security framework used by JBoss. JBoss Security offers a number of JAAS login modules, including: <itemizedlist> <listitem> Modified: trunk/docs/reference/src/main/docbook/en-US/content/introduction.xml =================================================================== --- trunk/docs/reference/src/main/docbook/en-US/content/introduction.xml 2009-06-08 00:18:10 UTC (rev 993) +++ trunk/docs/reference/src/main/docbook/en-US/content/introduction.xml 2009-06-08 00:52:09 UTC (rev 994) @@ -457,6 +457,22 @@ library to determine the best MIME type from the filename and file contents. </para> </listitem> + <listitem> + <para> + <emphasis role="strong">dna-web-jcr-rest</emphasis> + provides a set of JSR-311 (JAX-RS) objects that form the basis of a RESTful server for Java Content Repositories. This project + provides integration with DNA's JCR implementation (of course) but also contains a service provider interface (SPI) that can be + used to integrate other JCR implementations with these RESTful services in the future. For ease of packaging, these classes are + provided as a JAR that can be placed in the WEB-INF/lib of a deployed RESTful server WAR. + </para> + </listitem> + <listitem> + <para> + <emphasis role="strong">dna-web-jcr-rest-war</emphasis> + wraps the RESTful services from the dna-web-jcr-rest JAR into a WAR and provides in-container integration tests. This project + can be consulted as a template for how to deploy the RESTful services in a custom implementation. + </para> + </listitem> </itemizedlist> There are also documentation modules (located in the source under the <code>docs/</code>