[
https://issues.apache.org/jira/browse/ISIS-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-367.
------------------------------
Resolution: Won't Fix
After a rethink, we've decided not to implement this at this time. Instead,
we've developed a JDO implementation of the PublishingService that saves to the
local database in the same transaction as changes to the domain object model
(ISIS-377)
> Refactor to support JTA transactions
> ------------------------------------
>
> Key: ISIS-367
> URL: https://issues.apache.org/jira/browse/ISIS-367
> Project: Isis
> Issue Type: New Feature
> Components: Core, Objectstore: JDO, Viewer: RestfulObjects, Viewer:
> Wicket
> Affects Versions: viewer-restfulobjects-1.0.0, viewer-wicket-1.1.0,
> objectstore-jdo-1.0.0, core-1.1.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-restfulobjects-2.0.0, viewer-wicket-1.2.0,
> objectstore-jdo-1.1.0, core-1.2.0
>
>
> This is a pretty big refactoring, and touch most of the released modules, if
> not all.
> In particular, the responsibility for creating the transaction manager must
> move out of the object store, and instead be a standalone component (with its
> own Installer impl etc).
> It might make sense to rename the existing IsisTransactionManager to
> IsisSimpleTranasctionManager or equivalent, and to have a JTA-specific
> implementation that delegates as much as possible to the underlying JEE
> runtime.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
