[
https://issues.jboss.org/browse/JBTM-852?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson commented on JBTM-852:
------------------------------------
Thanks Mike, I presume you have confirmed nothing is created on disk in that scenario?
Perhaps your resolution could be to update the documentation in the ArjunaCore programmers
guide (or wherever it is we document ObjectStores) in the github (head/trunk/master
whatever you want to call it) version. Note, do not add it to the documentation under
docs/ as that is platform docs and this ObjectStore feature is not supported in EAP
Setting SettingVolatile store still creates an ObjectStore directory
on the disk
---------------------------------------------------------------------------------
Key: JBTM-852
URL:
https://issues.jboss.org/browse/JBTM-852
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.15.0
Reporter: Mircea Markus
Assignee: Michael Musgrove
Priority: Minor
Fix For: 5.0.0.M2
Even when configuring {code:java}
arjPropertyManager.getObjectStoreEnvironmentBean().setObjectStoreType(VolatileStore.class.getName())
{code} an "ObjectStore" directory is created on the disk. After discussing with
JTM team this doesn't cause any real problem in the sense that nothing is written to
the disk, but this is annoying and might create confusion between the users.
A workaround would be to add the following configuration together with the previously
mentioned one:
{code:java} BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class,
"communicationStore").setObjectStoreType(VolatileStore.class.getName()) {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira