12:36 p.m.
Shouldn't the profileservice attachments go under:
${jboss.server.data.dir}/profile-service
The server data dir is supposed to hold persistent server data.
Also the saved attachments could use a corresponding .xml suffix (if they are actually
xml).
Cheers
/Dimitris
12:40 p.m.
I wanted it under a unique location to differentiate it from other
services. Its configurable.
If the attachment is xml, it should use an xml extension.
Dimitris Andreadis wrote:
Shouldn't the profileservice attachments go under:
${jboss.server.data.dir}/profile-service
The server data dir is supposed to hold persistent server data.
Also the saved attachments could use a corresponding .xml suffix (if
they are actually xml).
Cheers
/Dimitris
12:39 p.m.
Scott Stark wrote:
I wanted it under a unique location to differentiate it from other
services.
Unless there is some other technical reason I still think
${jboss.server.data.dir}/profile-service is the right location, along with other server
data
that can be backed up together, if necessary:
data
├───hypersonic
├───tx-object-store
└───xmbean-attrs
The only glitch is we don't create this directory by default so you need to create the
parent ${jboss.server.data.dir}, if not there.
Its configurable.
Or hardcoded? ;)
profile-repository.xml:
<bean name="AttachmentsSerializer"
class="org.jboss.system.server.profileservice.repository.JAXBAttachmentSerializer">
<!-- TODO This is getting set in the DeploymentRepository.load, to make sure that we
use
the same directory.
<property
name="attachmentsStoreDir">${jboss.server.home.dir}attachments</property>
-->
</bean
If the attachment is xml, it should use an xml extension.
Dimitris Andreadis wrote:
> Shouldn't the profileservice attachments go under:
>
> ${jboss.server.data.dir}/profile-service
>
> The server data dir is supposed to hold persistent server data.
>
> Also the saved attachments could use a corresponding .xml suffix (if
> they are actually xml).
>
> Cheers
> /Dimitris
>
2:24 p.m.
I thought it was configurable, but its just the profileRoot/attachments.
I'll make it configuration as I finish pulling out the profileservice-spi.
https://jira.jboss.org/jira/browse/JBAS-6223
Dimitris Andreadis wrote:
Scott Stark wrote:
> I wanted it under a unique location to differentiate it from other
> services.
Unless there is some other technical reason I still think
${jboss.server.data.dir}/profile-service is the right location, along
with other server data that can be backed up together, if necessary:
data
├───hypersonic
├───tx-object-store
└───xmbean-attrs
The only glitch is we don't create this directory by default so you
need to create the parent ${jboss.server.data.dir}, if not there.
> Its configurable.
Or hardcoded? ;)
profile-repository.xml:
<bean name="AttachmentsSerializer"
class="org.jboss.system.server.profileservice.repository.JAXBAttachmentSerializer">
<!-- TODO This is getting set in the DeploymentRepository.load, to
make sure that we use the same directory.
<property
name="attachmentsStoreDir">${jboss.server.home.dir}attachments</property>
-->
</bean
3:47 p.m.
Scott Stark wrote:
I thought it was configurable, but its just the
profileRoot/attachments.
I'll make it configuration as I finish pulling out the profileservice-spi.
https://jira.jboss.org/jira/browse/JBAS-6223
Oh hmm that's my fault then :)
It was configurable, until it started to mess up the directory name for
some reason. I put it in the DeploymentRepository.load and forgot about
changing that back...
Dimitris Andreadis wrote:
> Scott Stark wrote:
> > I wanted it under a unique location to differentiate it from other
> > services.
>
> Unless there is some other technical reason I still think
> ${jboss.server.data.dir}/profile-service is the right location, along
> with other server data that can be backed up together, if necessary:
>
> data
> ├───hypersonic
> ├───tx-object-store
> └───xmbean-attrs
>
> The only glitch is we don't create this directory by default so you
> need to create the parent ${jboss.server.data.dir}, if not there.
>
> > Its configurable.
>
> Or hardcoded? ;)
>
> profile-repository.xml:
>
> <bean name="AttachmentsSerializer"
>
class="org.jboss.system.server.profileservice.repository.JAXBAttachmentSerializer">
>
> <!-- TODO This is getting set in the DeploymentRepository.load, to
> make sure that we use the same directory.
> <property
>
name="attachmentsStoreDir">${jboss.server.home.dir}attachments</property>
> -->
> </bean
>
6:32 p.m.
Its now configurable and set to data/attachments:
conf/bootstrap/profile-repository.xml
<bean name="SerializableDeploymentRepositoryFactory"
class="org.jboss.system.server.profileservice.repository.SerializableDeploymentRepositoryFactory">
<property
name="storeRoot">${jboss.server.base.dir}</property>
<property
name="attachmentsRoot">${jboss.server.data.dir}/attachments</property>
Emanuel Muckenhuber wrote:
Scott Stark wrote:
> I thought it was configurable, but its just the
> profileRoot/attachments. I'll make it configuration as I finish
> pulling out the profileservice-spi.
> https://jira.jboss.org/jira/browse/JBAS-6223
>
Oh hmm that's my fault then :)
It was configurable, until it started to mess up the directory name
for some reason. I put it in the DeploymentRepository.load and forgot
about changing that back...
> Dimitris Andreadis wrote:
>> Scott Stark wrote:
>> > I wanted it under a unique location to differentiate it from other
>> > services.
>>
>> Unless there is some other technical reason I still think
>> ${jboss.server.data.dir}/profile-service is the right location,
>> along with other server data that can be backed up together, if
>> necessary:
>>
>> data
>> ├───hypersonic
>> ├───tx-object-store
>> └───xmbean-attrs
>>
5879
days inactive
5883
days old
jboss-development@lists.jboss.org
5 comments
3 participants
participants (3)
-
Dimitris Andreadis -
Emanuel Muckenhuber -
Scott Stark