Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: modeshape-2.2.…
Commits on Aug 23, 2010
  1. @rhauch
Commits on Aug 22, 2010
  1. @rhauch

    Corrected several compiler warnings.

    rhauch authored
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2192 76366958-4244-0410-ad5e-bbfabb93f86b
  2. @rhauch

    MODE-31 MODE-680 Updated the documentation with information about the…

    rhauch authored
    … two Teiid sequencers. Also removed the unused 'utils/modeshape-jboss' project.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2191 76366958-4244-0410-ad5e-bbfabb93f86b
  3. @rhauch

    MODE-681 Cleaned up code that was printing stack traces to System.err…

    rhauch authored
    … or System.out, and changed several JDBC logging statements to be FINE JDK logging level rather than INFO. Also corrected the output of querying all tables (since we added the new 'mode:hashed' built-in node type).
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2190 76366958-4244-0410-ad5e-bbfabb93f86b
  4. @rhauch

    MODE-31 Added new integration tests that sequence VDBs, load the sequ…

    rhauch authored
    …enced output into a JCR Session (validating the node types and mixin types are correct and valid), and query the results. While doing this, several issues were found with the node type definitions, so these were corrected. Also changed the sequencing configuration in the JBoss AS service so that the VDB and model file name are not used in the sequenced output path (as the sequencer would create an 'nt:unstructured' node to represent that level, named with the file name, but then this node contained the 'vdb:virtualDatabase' or 'xmi:model' node named the same as the file (without the extension or version). Thus, this filename node seemed superfluous.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2189 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Aug 21, 2010
  1. @rhauch

    MODE-31 MODE-680 Completed the initial implementation of the Teiid mo…

    rhauch authored
    …del and VDB sequencers. Additional testing needs to be completed, but at this point both sequencers appear to be operating very well against a variety of test files.
    
    The ModelSequencer can be used to extract the structural information contained with a Teiid relational XMI model, including the catalogs, schemas, tables, views, columns, primary keys, foreign keys, indexes, procedures, procedure paramters, procedure results, logical relationships, and the JDBC source from which the model was imported. A series of node types and mixin types were defined to prescribe this structure, though all are extremely adaptable and tolerant of additional properties (as all non-mixin node types extend nt:unstructured). References within the model being sequenced are always resolved (resulting in the WEAKREFERENCE properties being set), although references to objects in other models are captured with the hrefs and/or UUIDs as defined in the model, allowing them to be resolved at another time but still enabling them to be used in queries. Descriptions, tags, and transformation mappings are all projected onto the main relational object, making it much easier to access, query, and use this information. The SHA-1 hash of the XMI file is also captured.
    
    The VdbSequencer is used to extract the structural information contained within the Teiid relational XMI models embedded within the VDB. Although VDB files use the ZIP archive format, VDB archives contain a number of other files (e.g., runtime indexes) that are not needed, and thus the VdbSequencer does **not** simply extract the model files. Instead, when the VdbSequencer sequences a VDB archive, the virtual database's manifest is processed to identify the set of models (along with information used by the Teiid server, such as the JNDI name of the source used by the connector, the translator name, etc.), the model dependencies, and extra metadata (e.g., descriptions, problem markers, etc.). The VdbSequencer then sequences each of the embedded relational XMI models to extract the relational schema defined in the models. The output of the sequencer, then, is a single subgraph that has:
     - a root node representing the virtual database (named according to the VDB archive, minus the version information and the .vdb extension), with properties for the SHA-1 hash of the VDB archive file, version information, description, and other manifest information;
     - the placed under the VDB node the sequenced output for each relational model, including any error/warning/info problem markers that were in the VDB.
    
    Note that the VdbSequencer resolves all (valid) references between all models within the VDB, meaning the sequenced representations of all models within the VDBs are are consistent, immediately usable, and independent of all other content in the repository (outside of the VDB subgraph).
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2188 76366958-4244-0410-ad5e-bbfabb93f86b
  2. @rhauch

    MODE-31 Added the 'modeshape-sequencer-teiid' project to the parent P…

    rhauch authored
    …OM and to the JBoss AS service deployment. Also extracted the compone that is resolving references, so that it could be reused by the VDB sequencer (yet to be written). All unit and integration tests pass.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2187 76366958-4244-0410-ad5e-bbfabb93f86b
  3. @rhauch

    MODE-31 Updated the teiid.cnd file used in the CndImporterTest to mat…

    rhauch authored
    …ch that of the original in the sequencer.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2186 76366958-4244-0410-ad5e-bbfabb93f86b
  4. @rhauch

    MODE-31 Changed the model sequencer to set default property values if…

    rhauch authored
    … they're missing. This is because the search engine indexing logic uses the graph layer, so the graph layer needs to have the default values for properties (otherwise these properties will have no values). The default values are read off of the 'teiid.cnd' file using a custom utility.
    
    Also added several integration tests to verify the 'teiid.cnd' file (which is merely an aggregation of the other CND files). This led to the discovery of several problems with the node type definitions, including the fact that node types can only define children with expected primary types, so in order to constraint node types on children we need to make our node types non-mixins.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2185 76366958-4244-0410-ad5e-bbfabb93f86b
  5. @rhauch

    MODE-31 Changed the behavior when using XMI UUIDs as JCR UUIDs to sti…

    rhauch authored
    …ll use the 'xmi:referenceable' mixin and the 'xmi:uuid' property, even though the XMI UUID is the same as the JCR UUID. We have to do this since the relational node type mixins always extend 'xmi:referenceable' and 'xmi:uuid' is a mandatory property on 'xmi:referenceable'.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2184 76366958-4244-0410-ad5e-bbfabb93f86b
  6. @rhauch

    MODE-31 Restricted this sequencer to operate only against relational …

    rhauch authored
    …models. Other models work fairly well, but they will require some customization and complete CND definitions. Those will have to wait for a later release.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2183 76366958-4244-0410-ad5e-bbfabb93f86b
  7. @rhauch

    MODE-31 Added another relational test case that includes some model o…

    rhauch authored
    …bjects not typically created during JDBC import (including descriptions, catalogs, schemas, logical relationships, and some empty objects). This exposed a couple of minor issues (e.g., not using the 'xsi:type' value) that were easily fixed.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2182 76366958-4244-0410-ad5e-bbfabb93f86b
  8. @rhauch

    MODE-31 Minor tweaks to the handling of XMI UUIDs and mixin types for…

    rhauch authored
    … 'mix:referenceable' and 'xmi:referenceable'
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2181 76366958-4244-0410-ad5e-bbfabb93f86b
  9. @rhauch

    MODE-31 Added a (static) flag that controls whether the XMI UUIDs are…

    rhauch authored
    … used for the JCR UUIDs. If so, then simple weak reference properties are used for all model references, but this limits a model from being sequenced in a repository only once (or rather the last model uploaded overwrites all previous sequencing results).
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2180 76366958-4244-0410-ad5e-bbfabb93f86b
  10. @rhauch

    MODE-31 More progress on the model sequencer. Physical and virtual re…

    rhauch authored
    …lational models seem to be working pretty well, though other types of models haven't been done yet.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2179 76366958-4244-0410-ad5e-bbfabb93f86b
  11. @rhauch

    MODE-31 Additional progress on the model sequencer, with more fixes t…

    rhauch authored
    …o the transformation and annotation handling. Still more work to be done.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2178 76366958-4244-0410-ad5e-bbfabb93f86b
  12. @rhauch

    MODE-31 Additional progresson the model sequencer. At this point, muc…

    rhauch authored
    …h of the sequencing logic is in place, although there remains much more testing and debugging.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2177 76366958-4244-0410-ad5e-bbfabb93f86b
  13. @rhauch

    MODE-31 Added more implementation and testing of the model sequencer.…

    rhauch authored
    … It is still incomplete, but it is coming along fairly nicely.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2176 76366958-4244-0410-ad5e-bbfabb93f86b
  14. @rhauch

    MODE-31 Created an initial (incomplete) version of a sequencer module…

    rhauch authored
    … for Teiid model and VDB sequencers. This initial version doesn't yet contain the sequencers, but does contain the beginnings of a utility that will create a CND file representing one or more ECore models (aka, the EMF models that define a metamodel) plus some very simple test cases for that utility. Most of the ECore files used in Teiid Designer are added as test resources.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2175 76366958-4244-0410-ad5e-bbfabb93f86b
  15. @tejones

    MODE-637 - Added method to iterate over superclasses of a class looki…

    tejones authored
    …ng for a field
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2174 76366958-4244-0410-ad5e-bbfabb93f86b
  16. @tejones
  17. @tejones

    MODE-637 - Remove isRunning operation for connectors, clean up unused…

    tejones authored
    … imports, remove unused Ping operation from MangedConnector, change getProperties() to use all properties when when all are inferred.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2172 76366958-4244-0410-ad5e-bbfabb93f86b
  18. @tejones

    MODE-637 - Add constants for Connector metrics

    tejones authored
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2171 76366958-4244-0410-ad5e-bbfabb93f86b
  19. @rhauch

    MODE-637 Temporary fix to correct the build.

    rhauch authored
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2170 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Aug 20, 2010
  1. @rhauch

    MODE-681 Corrected failing test by making a slightly cheaper check of…

    rhauch authored
    … whether the LocalRepositoryDelegate has a session when 'close()' is called. The previous version actually caused 'close()' to open a session if it didn't have one.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2169 76366958-4244-0410-ad5e-bbfabb93f86b
  2. @tejones

    MODE-854 - Fix for connection leak

    tejones authored
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2168 76366958-4244-0410-ad5e-bbfabb93f86b
  3. @vhalbert

    MODE-681 - changed to username connection property name to be "user",…

    vhalbert authored
    … in line with the jdbc standard name.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2167 76366958-4244-0410-ad5e-bbfabb93f86b
  4. @rhauch

    MODE-854 After some debugging, we think the problem is that the Refle…

    rhauch authored
    …ction.getAllProperties(...) method (or similar methods) is getting the JavaBean property value when it creates the Reflection.Property instance. When this is done for the RepositorySource implementations, getting the value for the "connection" property results in calling "getConnection()", and this RepositoryConnection does not get closed (or returned into the pool), meaning we have a connection leak. Even though the JOPR plugin is not using this property (it only uses properties that are not inferred; e.g., they have annotations), it is nevertheless being called **before** the plugin determines it can disregard it.
    
    The fix is to remove the value from the Reflection.Property and move it to Reflection, and then change the corresponding places where it's used.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2166 76366958-4244-0410-ad5e-bbfabb93f86b
  5. @rhauch

    MODE-859 Changed several assembly descriptors to no longer build the …

    rhauch authored
    …"with-dependency" JAR artifacts and instead to build "jar-with-dependency" artifacts, and for these archives to be unpacked (to contain the unpacked JAR files rather than the JAR files themselves). The patch also changes the "modeshape-graph" module to create a "modeshape-graph-{version}-jar-with-dependencies.jar" file, so this can be used with a sequencer outside of the ModeShape environment.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2165 76366958-4244-0410-ad5e-bbfabb93f86b
  6. @tejones

    MODE-637 - Correct connector description

    tejones authored
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2164 76366958-4244-0410-ad5e-bbfabb93f86b
  7. @tejones

    MODE-637 - Correct connector description

    tejones authored
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2163 76366958-4244-0410-ad5e-bbfabb93f86b
  8. @rhauch

    MODE-843 The '-with-dependencies' specifications in the 'deploy/jboss…

    rhauch authored
    …as/modeshape-jbossas-service/src/assembly/kit.xml' assembly descriptor only work for Maven 2.2 (or later), and we're stuck on Maven 2.0.9 (the lower common denominator). So, we need to continue to explicitly include dependencies of the MS Office sequencer, and even all of the ModeShape artifacts, too. I changed the assembly descriptor to have these dependencies.
    
    Also, I added the 'modeshape-mimetype-detector-aperture' artifact (and its two dependencies) to the assembly descriptor, so that it can be enabled in the configuration file without having to find/download the necessary JARs.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2162 76366958-4244-0410-ad5e-bbfabb93f86b
  9. @tejones
  10. @rhauch

    MODE-858 Changed one of the test cases that seems to be periodically …

    rhauch authored
    …failing due to timing issues/delays. The fix was to pause for a half second before registering some listeners in one test method in ClusteringTest.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2160 76366958-4244-0410-ad5e-bbfabb93f86b
  11. @tejones
Something went wrong with that request. Please try again.