[
https://issues.apache.org/jira/browse/LABS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Gianni resolved LABS-454.
--------------------------------
Resolution: Fixed
package fragment-init addresses this issue, it has been implemented in existing
fragments.
> [database] Provide application database startup
> -----------------------------------------------
>
> Key: LABS-454
> URL: https://issues.apache.org/jira/browse/LABS-454
> Project: Labs
> Issue Type: New Feature
> Components: Magma
> Affects Versions: Current
> Reporter: Simone Gianni
> Assignee: Simone Gianni
> Fix For: Current
>
>
> Magma is composed of fragments. The current application is one of the
> fragments.
> Fragments declare beans that are eventually persisted on the database. Quite
> often, fragments will need to have some of these beans on the database, or at
> least it would be handy to initialize a few entites.
> For example, the user fragment could create a default user, admin, with
> privileges and a default password.
> The current application will probably want to initialize some entities as
> well, for example create default content sections needed for proper page
> display, or create more users with different roles.
> It's critical that these entites are created only once : nobody wants to
> ALWAYS have and admin user with a default password.
> Magma already offer a Startup class that executes its (potentially inferred)
> startup* methods. Dependency between startup methods is achieved simply
> calling the needed startup method.
> What's needed is a set of simple database related tools to ease the entity
> setup process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
