Where does the bootstrapping begin (in Aggregate)?

C_Howell · April 3, 2017, 9:11pm

Hello,

Where is the entry point to the code that sets off the creation of a
minimal set of database tables and an admin user when Aggregate begins for
the first time?

Thanks,

Caden

Mitch_S · April 4, 2017, 5:23pm

ODK Aggregate makes extensive use of the Spring Framework, and, in
particular Spring Security.

The definition for the beans used in configuring the security apparatus are
in:

https://github.com/opendatakit/aggregate/blob/master/war-base/WEB-INF/applicationContext-security.xml

In general, database tables are constructed on a first-reference basis.
This is done via the calls to assertRelation on the Datastore interface.
at

github.com

getodk/aggregate/blob/master/src/main/java/org/opendatakit/common/persistence/Datastore.java#L51


      
          
          
  boolean hasRelation(String schema, String tableName, User user) throws ODKDatastoreException;
          
          
  <T extends CommonFieldsBase> T createEntityUsingRelation(T relation, User user);
          
          
  <T extends CommonFieldsBase> T getEntity(T relation, String uri, User user) throws ODKDatastoreException;
          
          
  Query createQuery(CommonFieldsBase table, String loggingContextTag, User user);
          
          
  void putEntity(CommonFieldsBase entity, User user) throws ODKEntityPersistException, ODKOverQuotaException;
          
          
  void putEntities(Collection<? extends CommonFieldsBase> entities, User user) throws ODKEntityPersistException, ODKOverQuotaException;
          
          
  void deleteEntity(EntityKey key, User user) throws ODKDatastoreException;
          
          
  void deleteEntities(Collection<EntityKey> keys, User user) throws ODKDatastoreException;
          
          
  TaskLock createTaskLock(User user);
          }

The kick-off to table creation and population begins in the loading of the
Spring beans defined in the above xml file.

Some of these beans have an afterPropertiesSet() method that verifies or
configures data tables.

I think of the RoleHierarchyImpl class as the first class to go through
this processing.

github.com

getodk/aggregate/blob/master/src/main/java/org/opendatakit/common/security/spring/RoleHierarchyImpl.java#L123


      
            return passwordEncoder;
          }
          
          
public void setPasswordEncoder(MessageDigestPasswordEncoder passwordEncoder) {
            this.passwordEncoder = passwordEncoder;
          }
          
          
public WebStartup getStartupAction() {
            return startupAction;
          }
          
          
public void setStartupAction(WebStartup startupAction) {
            this.startupAction = startupAction;
          }
          
          
@Override
          public void afterPropertiesSet() throws Exception {
            if (datastore == null) {
              throw new IllegalStateException("datastore cannot be unspecified");
            }
            if (userService == null) {

That class configures the superuser and sanitizes the granted authority
hierarchy. And, in the course of doing that, creates the task lock table,
etc.

Because Spring manages the order of bean construction, something else might
do something first, but this is the class that does the most significant
security-layer initialization actions.

···

On Mon, Apr 3, 2017 at 2:11 PM, C. Howell wrote:

Hello,

Where is the entry point to the code that sets off the creation of a
minimal set of database tables and an admin user when Aggregate begins for
the first time?

Thanks,

Caden

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com