[jboss-as7-dev] "JBoss-Product-Console-Slot"

[Brian Stansberry]

It's meant to control what module slot is used for loading the console 
module. Different products would have different console modules stored 
in differently named slot. Default is "main". To change the slot the AS 
uses:

1) A properties file $JBOSS_HOME/bin/product.conf is included in the 
product.

2) On boot, this properties file is loaded and an attempt is made to 
load a module named "org.jboss.as.product" with a module slot specified 
in the properties file. See constructor of ProductConfig at [1].

3) That module includes a MANIFEST.MF that provides the name of the 
module slot from which manifest attributes are read, including 
JBoss-Product-Console-Slot.

4) The ProductConfig is made available to services in the AS via the 
ServerEnvironment service. The http management services use it to 
provide the slot to the ResourceHandler for the console [2], which does 
the actual loading of the module.

The part in step 2) involves a fair bit of indirection just for reading 
a few properties, but it's a more future-proof approach, since that 
"org.jboss.as.product" module could someday involve a lot more than just 
a few manifest attributes. It's also simpler to patch stuff that's in a 
module.

[1] 
https://github.com/jbossas/jboss-as/blob/master/process-controller/src/main/java/org/jboss/as/version/ProductConfig.java

[2] 
https://github.com/jbossas/jboss-as/blob/master/domain-http/interface/src/main/java/org/jboss/as/domain/http/server/ConsoleMode.java#L111

On 9/13/12 5:16 AM, Heiko Braun wrote:
> Can someone explain how the "JBoss-Product-Console-Slot" is going to be used?
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat