-
1. Re: ObjectStoreDir location
The xml bit was trancated:
<property name="com.arjuna.ats.arjuna.objectstore.objectStoreDir" value="PutObjectStoreDirHere"/>
-
2. Re: ObjectStoreDir location
can we also change the location of this jbossjta-properties.xml file?
-
3. Re: ObjectStoreDir location
"dimitris@jboss.org" wrote:
JBOSS_HOME/bin/PutObjectStoreDirHere
This is an entry that is supposed to be changed during installation.
JBossTS has no direct knowledge of the app server nor of any app server specific processing used in the config. Having said that it should be possible to modify the integration code to use the data directory as a default.
Kev -
4. Re: ObjectStoreDir location
"bill.burke@jboss.com" wrote:
can we also change the location of this jbossjta-properties.xml file?
Our only requirement at present is that it should be found on the classpath. Where would you prefer it to be picked up from? Why is conf inappropriate?
Kev -
-
6. Re: ObjectStoreDir location
I would like to be able to configure the classpath resource it is found from. The reason for this is that I'm implementing JBoss Embedded at them moment and I need a configurable, base resource path so that it is easy, for instance, to install embedded JBoss onto Tomcat.
Why not just extend the MBean that is used and override settings from there?
Then again....
Are all the properties in jbossjta-properties.xml overrideable from System properties? -
-
8. Re: ObjectStoreDir location
...adding to this...
Can the classpath resource of jbossjta-properties.xml be configurable as a System Property? Or even the file or URL location of it?
THanks -
9. Re: ObjectStoreDir location
"dimitris@jboss.org" wrote:
I've notice JBossTS when used in JBossAS, by default, uses:
JBOSS_HOME/bin/PutObjectStoreDirHere
to store tx recovery info.
We don't store data in the bin dir. Actually, I would expect the correct location to be inside every particular server config directory, because you can use the same bin to run multiple server configurations, so use something like:
JBOSS_HOME/server/default/data/object-store
I see this entry in conf/jbossjta-properties.xml:
<property name="com.arjuna.ats.arjuna.objectstore.objectStoreDir" value="PutObjectStoreDirHere"/>
In jboss xml config files we would normally use a syntax like
... ${jboss.server.data.dir}/object-store
Can we do something similar with the jbossjta-properties.xml configuration? Do it substitute system properties?
We've always encouraged users to change that setting when installing into JBoss. Putting it within the JBossAS install wasn't always guaranteed to work because, certainly back in the 3.2.x days, people would often install JBossAS into read-only directories. The object store dir must be writeable.
Do we assume that the JBossAS directory is always writeable? -
10. Re: ObjectStoreDir location
"dimitris@jboss.org" wrote:
If you can just introduce property substitution that would be great.
JBossTS is a standalone transaction manager and does not currently support this. Overriding the default value in the integration layer would, however, allow you to configure it via the mbean and therefore take advantage of the substitution support in the app server.
Kev -
11. Re: ObjectStoreDir location
"bill.burke@jboss.com" wrote:
...adding to this...
Can the classpath resource of jbossjta-properties.xml be configurable as a System Property? Or even the file or URL location of it?
THanks
Yes, you can always specify the location of the property file explicitly via System. If it's not located there, then it starts to search the classpath and other places (e.g., cwd). -
12. Re: ObjectStoreDir location
"mark.little@jboss.com" wrote:
Do we assume that the JBossAS directory is always writeable?
The data directory is :-)
Kev -
13. Re: ObjectStoreDir location
And the config file location System Property is? (Thanks for being my manual)
-
14. Re: ObjectStoreDir location
"Kevin.Conner@jboss.com" wrote:
"mark.little@jboss.com" wrote:
Do we assume that the JBossAS directory is always writeable?
The data directory is :-)
Kev
Good ;-)