[
https://issues.apache.org/jira/browse/LABS-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Gianni resolved LABS-162.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: Future)
Current
> If database-jpa-web is not installed, all saves will fail with no warning
> -------------------------------------------------------------------------
>
> Key: LABS-162
> URL: https://issues.apache.org/jira/browse/LABS-162
> Project: Labs
> Issue Type: Improvement
> Components: Magma
> Affects Versions: Current
> Reporter: Simone Gianni
> Assignee: Simone Gianni
> Fix For: Current
>
>
> If in a web project database-jpa-web is not present, everything will work
> apparently correct, except that transactions will never be closed by anyone,
> so data will not be persisted and instead it will be stored in memory.
> So the user will see no error but nothing will be written to the database.
> This is unacceptable.
> Probably the simplest solution is to merge database-jpa-web directly inside
> database-jpa, still making database-jpa not dependant on foundation-website,
> using AspectJ loosely typed approach to have a working system both if
> foundation-website is present or not.
> If foundation-website was not providing so much functionalities, but only
> declaring interfaces or basic apis, it would not be a problem to have
> database-jpa depend on it (see LABS-152)
> Probably inthe future it could be possible to merge the JPA "close the
> session" problem together with the handler reset problem in LABS-156 in a
> single API that resets a thread (thus committing here, cleaning there etc..).
--
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]
