The existing import-entity-type.crn XML imports to the database, but doesn't add to the EntityTypes collection in memory. Consequently, if something else in the same import/export operation uses EntityTypes in the Java code, they won't be there and the operation will fail. Nothing in the current uP3 default configuration has this problem as it stands, but introducing custom components (such as GaP and PersonAttribute implementations) can trigger this issue.

A patch will be attached. The patch is especially attractive because it moves import/export toward using uPortal Java APIs to do its work instead of simply writing to the database.