[jboss-dev-forums] [Design of POJO Server] - Re: Clustered DeploymentRepository for 5.1

scott.stark@jboss.org do-not-reply at jboss.com
Mon Mar 2 16:30:56 EST 2009


"emuckenhuber" wrote : 
  | This has not been discussed a lot, therefore how you exactly are going to specify the profile is still open :)
  | This depends on how the structure of "common/*" looks like, maybe we have some aliasing for the jboss-profile-source. But in general you should just need to say <jboss-profile> and the profiles, deployments which are required.
The test.xml example is a little too file based to be a general metadata view unless the source can be taken as just a URI to be resolved by something. So I would expect test.xml to be something like:


  | <profiles
  | 	xmlns="urn:jboss:profileservice:profiles:1.0"
  | 	name="profiles">
  | 
  | 	<profile name="immutable">
  | 		<profile-source>
  | 			<source>jboss-deployers:javaee5-deployers</source>
  | 			<source>jboss-bootstrap:conf/bootstrap.xml</source> 
  | 		</profile-source>
  | 		<sub-profile>ejb3</sub-profile>
  | 		<deployment>myEjb3Deployment.ear</deployment>
  | 	</profile>
  | 	
  | 	<hotdeployment-profile name="mutable">
  | 		<profile-source>
  | 			<source>${jboss.server.home.url}deploy</source>
  | 			<source>${jboss.server.home.url}deploy2</source>
  | 		</profile-source>
  | 		<sub-profile>immutable</sub-profile>
  | 	</hotdeployment-profile>
  | 
  | 	<maven-profile name="maven" xmlns="urn:jboss:profileservice:profile:maven:1.0">
  | 		<profile-source>
  | 			<source>http://repository.jboss.org/maven2</source>
  | 		</profile-source>
  | 		<sub-profile>hotdeployment</sub-profile>
  | 		<deployment>org.jboss.jboss-profileservice:profileservice-spi-6.0.0-GA</deployment>
  | 	</maven-profile>
  | 
  | </profiles>
  | 

where both the profile metadata and interpretation will be a function of the factory that matches up to the metadata. This is an aside to the original question of how to create the profile.

So, if creation of a profile is a process of supplying the profile metadata to a factory, that would be fine. It would not matter whether the bootstrap and core profiles are immutable as I don't expect the profile to be iteratively created in terms of adding core deployers, bootstrap deployments.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214305#4214305

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214305



More information about the jboss-dev-forums mailing list