[
https://issues.apache.org/jira/browse/RAVE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182497#comment-13182497
]
Matt Franklin commented on RAVE-392:
------------------------------------
I am still looking for the discussion from last year about why we didn't choose
JPA to initialize the demo portal data. The reasoning (as I remember it) was
that the demo portal is just that, a demo; we didn't want to have a bunch of
initialization code embedded in what people built real products on top of.
IMO, the SQL scripts work, but if you wanted to have actual code that
intiialized the database, I think it should be dynamic (Groovy script, etc) or
a completely separate sub-project that is added as a dependency to the demo
portal only.
As for the second question, rave-commons is intended to be extremely generic
code that could be used in many scenarios, not just Rave. However, I do think
the current organization needs some additional improvement (it was a good first
step) and should change shortly.
> Use JPA instead of SQL statements for data initialization
> ---------------------------------------------------------
>
> Key: RAVE-392
> URL: https://issues.apache.org/jira/browse/RAVE-392
> Project: Rave
> Issue Type: Improvement
> Affects Versions: 0.7-INCUBATING
> Reporter: marijan milicevic
> Attachments: jpa_data_initialization_.patch
>
>
> please see attached patch and test case as an example. I think most of the
> data inserted is same to data inserted by init_data.sql file, except for the
> user layout (all users have same layout)
> Motivation:
> - this should work on any database
> - it is easier to maintain (for most part you have type safety, renaming,
> test cases if needed)
> - it is easier to split/extend/modify by users
> Problem:
> - in current setup it is not easy to use above initializing because data
> initializing/wiring is done in rave-commons and above class depends on
> rave-core. I am not sure why rave-commons is not part of rave-core (as a
> subpackage) because it only contains handful of classes which are mostly used
> within rave-core itself and both of those dependencies are included as
> dependencies of other sub-projects
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
