What is bootstrap-repo.xml?

[peterj]

Under what circumstances would I want to use bootstrap-repo.xml instead of bootstrap.xml?

I have run with both and the only difference I can detect is that because profile-service-repository.xml does not contain the various VFS deployers, hot deployment does not work. (By the way, are there any plans to provide a system property that can be used to decide which file to use? Right now bootstrap.xml is hard-coded and I had to rename the files to use bootstrap-repo.xml.)

I tried to access the JBAS-5525 issue referenced when bootstrap-repo.xml was created, but that issue is no longer in JIRA (it redirects to JBWS-2185).

On a related note, why is profile-service.xml not called simply profile.xml? The extension -service.xml is usually associated with JMX, but in this case the file is used with the microcontainer. I know that file naming conventions (e.g., *-service.xml) apply only in the deploy directory, and not in conf, but it can be initially confusing.

[alesj]

"PeterJ" wrote:
Under what circumstances would I want to use bootstrap-repo.xml instead of bootstrap.xml?

AFAIK this is meant as a drop-in replacement if you want to use profile-service.
e.g. building profileservice AS configuration:
jboss5/trunk/testsuite/build profileservice-config

"PeterJ" wrote:

I have run with both and the only difference I can detect is that because profile-service-repository.xml does not contain the various VFS deployers, hot deployment does not work. (By the way, are there any plans to provide a system property that can be used to decide which file to use? Right now bootstrap.xml is hard-coded and I had to rename the files to use bootstrap-repo.xml.)

On a related note, why is profile-service.xml not called simply profile.xml? The extension -service.xml is usually associated with JMX, but in this case the file is used with the microcontainer. I know that file naming conventions (e.g., *-service.xml) apply only in the deploy directory, and not in conf, but it can be initially confusing.

Start this discussion on 'Design of POJO server' forum.
Which will probably lead to JIRAs creation, and me fixing them. :-)

[peterj]

alesj wrote:
Which will probably lead to JIRAs creation, and me fixing them. :-)

Aw, man, that means yet another change for the beans configuration section in the book! I practically had to rewrite that section because on the changes made since beta4. ;-) (Ignore me, I just like to complain)

[starksm64]

"PeterJ" wrote:
Under what circumstances would I want to use bootstrap-repo.xml instead of bootstrap.xml?

To have the full featured profile service that provides the ManagementView, DeploymentManager spis into the server you need to run the bootstrap-repo.xml.

"PeterJ" wrote:

I have run with both and the only difference I can detect is that because profile-service-repository.xml does not contain the various VFS deployers, hot deployment does not work.

That should not be the case, both versions support hot deployment. I'll have to validate it.

"PeterJ" wrote:

(By the way, are there any plans to provide a system property that can be used to decide which file to use? Right now bootstrap.xml is hard-coded and I had to rename the files to use bootstrap-repo.xml.)

Yes, we should have something.

"PeterJ" wrote:

On a related note, why is profile-service.xml not called simply profile.xml? The extension -service.xml is usually associated with JMX, but in this case the file is used with the microcontainer. I know that file naming conventions (e.g., *-service.xml) apply only in the deploy directory, and not in conf, but it can be initially confusing.

Fair enough. The conventions apply to any deployments processed by the deployers, so its the deployers, deploy directories. We might as well be consistent in naming conventions.

[alesj]

"PeterJ" wrote:

(By the way, are there any plans to provide a system property that can be used to decide which file to use? Right now bootstrap.xml is hard-coded and I had to rename the files to use bootstrap-repo.xml.)

Yes, we should have something.

You can already do this:

 -Djboss.bootstrap.url=file:/C:\projects\jboss5\trunk\build\output\jboss-5.0.0.CR2\server\default\conf\bootstrap-repo.xml ^

Showing here:

11:37:02,343 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.CR2/server/default/conf/bootstrap-repo.xml/

[peterj]

Ah, now I see. The comment for BOOTSTRAP_URL in main/src/main/org/jboss/system/server/ServerConfig.javaServerConfig.java confused me (its wrong - possible a cut-and-paste error from ROOT_DEPLOYMENT_FILENAME).