Portlet Data Plans

Owned by Eric Dalquist
Oct 08, 2012
1 min read

Design ideas for reusing the uP4 data import/export tools, the tool would have several parts:

  1. Maven Plugin to do data i/e/d for a project
    1. Defines DataImportExport interface
      1. Has import, export, delete, list types, & list data methods
      2. void import(DataType, Object)
      3. Object export(DataType, String id)
      4. void delete(DataType, String id)
      5. Iterable<DataType> listDataTypes()
      6. Iterable<String> listData(DataType)
    2. Plugin places the whole project and deps on the classpath and uses the Java SPI loader to find the DataImportExport implementation
  2. JAXB Based import/export utility library
    1. Extract the JAXB import/export code from uPortal
    2. Dependency issues
      1. This is HEAVILY spring based right now, is that ok for the data migration plugin?
      2. Will it cause versioning issues with portlets that use Spring?
      3. Can the project's classpath be loaded in a child classloader?