Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Changed version to SNAPSHOT following release

  1. … 74 more files in changeset.
Changed the '2.8-SNAPSHOT' artifact version to '2.8.1.GA' for use in the product.

  1. … 74 more files in changeset.
MODE-1307 Added Content-Type HTTP header to REST examples

The examples in the RESTful Service chapter did not show including the "Content-Type" HTTP

header. The service will correctly return JSON if this header or "Content-Type" header is

supplied in the request. However, an error will result if a different content-Type header

is provided.

This change only affects the Reference Guide.

MODE-1368 Removed all legacy modules no longer needed in 3.x

ModeShape 3.x will not need a number of the 2.x modules. In particular:

- since 3.x will only have an AS7 kit, the AS5 or AS6 artifacts were removed

- all the connectors were removed, since they're no longer used

- the connector benchmark tests module was removed, replaced by our new

performance test suite

- the JPA DDL generator utility has been removed

- the 'modeshape-graph', 'modeshape-repository', 'modeshape-search-lucene'

and 'modeshape-clustering' modules have all been removed, since the new

'modeshape-jcr' module no longer uses them

- the DocBook modules were removed and are replaced by the Confluence space

- the two JDBC modules were moved out of the 'utils' directory to top-level modules

The build still works, but not all components have been included in the build.

This is because the query functionality doesn't yet work, so quite a few web

and JDBC driver modules all depend on this.

The assembly profile has not yet been changed or corrected.

  1. … 3650 more files in changeset.
Changed version to 2.8-SNAPSHOT after releasing 2.7.0.Final

  1. … 73 more files in changeset.
'Release: update versions for modeshape-2.7.0.Final'

  1. … 76 more files in changeset.
MODE-1328 Minor changes to the custom NodeTypeManager methods

The methods of the org.modeshape.jcr.api.nodetype.NodeTypeManager were renamed

to 'registerNodeTypes' to mirror the standard methods in the

javax.jcr.nodetype.NodeTypeManager methods.

  1. … 5 more files in changeset.
MODE-1328 Added to public API methods to register the node types defined in CND & XML files

Added the 'org.modeshape.jcr.api.nodetype.NodeTypeManager' interface that extends the 'javax.jcr.nodetype.NodeTypeManager' interface with new 'registerNodeTypeDefinitions(...)' methods that accept File, URL, or InputStream objects.

A new test class was added to verify the behavior. Also, the 'CndNodeTypeReader' and 'JackrabbitXmlNodeTypeReader' classes have been deprecated.

All unit and integration tests pass.

  1. … 12 more files in changeset.
MODE-1328 Added to public API methods to register the node types defined in CND & XML files

Added the 'org.modeshape.jcr.api.nodetype.NodeTypeManager' interface that extends the 'javax.jcr.nodetype.NodeTypeManager' interface with new 'registerNodeTypeDefinitions(...)' methods that accept File, URL, or InputStream objects.

A new test class was added to verify the behavior. Also, the 'CndNodeTypeReader' and 'JackrabbitXmlNodeTypeReader' classes have been deprecated.

All unit and integration tests pass.

  1. … 6 more files in changeset.
Changed versions to prepare for 2.7-SNAPSHOT development

  1. … 77 more files in changeset.
Changed version to 2.5.2.GA, in preparation for release.

  1. … 73 more files in changeset.
MODE-1273 Added built-in authentication using Seam Security

Added a built-in authentication/authorization provider to be enabled if and only if the "org.jboss.seam.security.Identity" class is on the classpath. The provider works when no Credentials are passed in, and creates an authenticated session based upon the current Identity instance if that Identity instance is already logged in.

All unit and integration tests pass with these changes, although none of our tests actually run with Seam Security. Therefore, additional testing will have to be done with system-level tests.

  1. … 5 more files in changeset.
MODE-1273 Added built-in authentication using Seam Security

Added a built-in authentication/authorization provider to be enabled if and only if the "org.jboss.seam.security.Identity" class is on the classpath. The provider works when no Credentials are passed in, and creates an authenticated session based upon the current Identity instance if that Identity instance is already logged in.

All unit and integration tests pass with these changes, although none of our tests actually run with Seam Security. Therefore, additional testing will have to be done with system-level tests.

  1. … 5 more files in changeset.
MODE-1150 Correct dependencies and documentation for SLF4J

Found some SLF4J dependencies that were still using the older version, plus the documentation

should have been updated.

  1. … 2 more files in changeset.
MODE-1150 Correct dependencies and documentation for SLF4J

Found some SLF4J dependencies that were still using the older version, plus the documentation

should have been updated.

  1. … 2 more files in changeset.
MODE-1264 Upgraded webdav-servlet to 2.0.1

Also updated the documentation to reference the new version.

  1. … 2 more files in changeset.
MODE-1243 Minor correction to Reference Guide.

MODE-1243 Minor correction to Reference Guide.

MODE-1243 JndiRepositoryFactory should support registering engine in JNDI

The JndiRepositoryFactory implementation should support registering the ModeShape engine into JNDI if the repository name is empty or not provided. This change would allow using the factory to configure Glassfish or Tomcat by registering the engine in JNDI so that JCR-2.0-style lookup are possible.

See also MODE-1242 for the change to make RepositoryFactory recognize JNDI URLs to Repository instances, not just ModeShape engine instances.

All unit and integration tests pass with this change.

  1. … 2 more files in changeset.
MODE-1243 JndiRepositoryFactory should support registering engine in JNDI

The JndiRepositoryFactory implementation should support registering the ModeShape engine into JNDI if the repository name is empty or not provided. This change would allow using the factory to configure Glassfish or Tomcat by registering the engine in JNDI so that JCR-2.0-style lookup are possible.

See also MODE-1242 for the change to make RepositoryFactory recognize JNDI URLs to Repository instances, not just ModeShape engine instances.

All unit and integration tests pass with this change.

  1. … 2 more files in changeset.
MODE-1150 Upgraded to SLF4J 1.6.1

Changed the SLF4J dependency from 1.5.11 to 1.6.1, including all of the documentation and the various web and jboss related modules.

Note that 1.6.x has changed its API slightly, and this breaks some libraries. Therefore, 1.6.x has to be used for all SLF4J-related libraries; one critical issue proved to be the "org.slf4j:jcl-over-slf4j" artifact that apparently is no longer needed (or at least needs to be the same version, and because RESTEasy had an explicit dependency on the then there was some work in excluding it from the web- and jboss- related ModeShape modules.

All unit and integration tests pass with these changes.

  1. … 12 more files in changeset.
Corrected DocBook error in query examples section.

Corrected DocBook error in query examples section.

Slightly improved the query examples section.

Slightly improved the query examples section.

MODE-1107, MODE-1205 Added support for pluggable authorization and authentication

Changed how the ModeShape JCR repository authentication and authorizes clients to no longer be entirely self-contained. Now, it is possible to configure each Repository instance with one or more customized authentication providers that are added to several built-in authentication providers for JAAS, anonymous (if configured), and HTTP Servlet. When Repository.login(...) is called, these providers are consulted in serial to authenticate the supplied credentials, and a Session is created if any provider successfully authenticates.

The ExecutionContext's SecurityContext is used to perform any authorization. Since the already-existing SecurityContext could only perform role-based permissions, a new AuthorizingSecurityContext interface was added to do path-based authorization, and is now used first if the ExecutionContext's security context is an AuthorizingSecurityContext implementation.

Therefore, each authenticator is responsible for creating an ExecutionContext that represents the user, including an appropriate (Authorizing)SecurityContext instance.

The AuthorizationProvider.authorize(...) method takes a Map<String,Object> parameter, allowing providers to add name-value pairs to this map when the supplied credentials are authenticated. ModeShape takes this map (populated only by the provider that successfully authenticates) and uses it as the Session's attributes. Thus, this technique allows each provider to place their own information in the Session attributes. Also updated the new Reference Guide section that talks about the AuthorizationProvider framework.

JcrRepository can be configured such that any user failing authentication will be authenticated as an anonymous user. The way JcrRepository was tracking this option was not clear, so it was changed to set up an AnonymousCredentials in these situations, and if the user fails authentication with their the AnonymousCredentials then we try to authenticate them anonymously (using the AnonymousCredentials). This was merely an implementation change, so no documentation changes were necessary.

Finally, it is possible to disable the JAAS AuthenticationProvider by specifying a zero-length value for the 'jaasLoginConfigName' option. This was also documented in the associated Reference Guide sections.

Again, out-of-the-box ModeShape works as it did before, except that SecurityContextCredentials are deprecated and authentication with them is DISABLED by default.

  1. … 45 more files in changeset.
MODE-1107, MODE-1205 Added support for pluggable authorization and authentication

Changed how the ModeShape JCR repository authentication and authorizes clients to no longer be entirely self-contained. Now, it is possible to configure each Repository instance with one or more customized authentication providers that are added to several built-in authentication providers for JAAS, anonymous (if configured), and HTTP Servlet. When Repository.login(...) is called, these providers are consulted in serial to authenticate the supplied credentials, and a Session is created if any provider successfully authenticates.

The ExecutionContext's SecurityContext is used to perform any authorization. Since the already-existing SecurityContext could only perform role-based permissions, a new AuthorizingSecurityContext interface was added to do path-based authorization, and is now used first if the ExecutionContext's security context is an AuthorizingSecurityContext implementation.

Therefore, each authenticator is responsible for creating an ExecutionContext that represents the user, including an appropriate (Authorizing)SecurityContext instance.

The AuthorizationProvider.authorize(...) method takes a Map<String,Object> parameter, allowing providers to add name-value pairs to this map when the supplied credentials are authenticated. ModeShape takes this map (populated only by the provider that successfully authenticates) and uses it as the Session's attributes. Thus, this technique allows each provider to place their own information in the Session attributes. Also updated the new Reference Guide section that talks about the AuthorizationProvider framework.

JcrRepository can be configured such that any user failing authentication will be authenticated as an anonymous user. The way JcrRepository was tracking this option was not clear, so it was changed to set up an AnonymousCredentials in these situations, and if the user fails authentication with their the AnonymousCredentials then we try to authenticate them anonymously (using the AnonymousCredentials). This was merely an implementation change, so no documentation changes were necessary.

Finally, it is possible to disable the JAAS AuthenticationProvider by specifying a zero-length value for the 'jaasLoginConfigName' option. This was also documented in the associated Reference Guide sections.

Again, out-of-the-box ModeShape works as it did before, except that SecurityContextCredentials are deprecated and authentication with them is DISABLED by default.

  1. … 45 more files in changeset.
Web Configuration Examples in Reference Guide Use Bad JCR Config URL

Corrected the URLs in the Ref. Guide, as well as the factory class.

MODE-1097 Updated Reference Guide to refer to new JcrRepository.Options that control index rebuilding

MODE-1076 Change all 'JOPR' references in documentation and code to 'RHQ'

The attached patch removes JOPR from the documentation and changes the properties named *jopr* in the POMs to *rhq*. After running these scripts:

find . -name *.xml -exec grep -iH JOPR {} \;

find . -name *.java -exec grep -iH JOPR {} \;

find . -name *.properties -exec grep -iH JOPR {} \;

The only remaining references to JOPR are the Maven dependencies. I can't find the RHQ version of these (if one even exists yet), but if anyone can point me to that, I'll be happy to make that change as well.

  1. … 4 more files in changeset.