Fwd: [jboss-as7-dev] Optional modules / subsystems usage best practices?

Charles Crouch ccrouch at redhat.com
Mon Oct 1 14:16:27 UTC 2012


We should probably make sure our AS7 migration includes a slimming/hardening phase too. I don't know about this time but with the previous app server we ended up turning off a lot of services we weren't using just to reduce the number of open ports...

----- Forwarded Message -----
From: "Marek Goldmann" <mgoldman at redhat.com>
To: jboss-as7-dev at lists.jboss.org
Cc: "Ben Browning" <bbrownin at redhat.com>
Sent: Monday, October 1, 2012 3:40:24 AM
Subject: [jboss-as7-dev] Optional modules / subsystems usage best practices?

Hi all,

We are able to make a dependency optional in modules.xml. That's 
awesome, now the question is how to use this feature in real life? Are 
there any best practices?

A bit of background.

In TorqueBox we add several subsystems to the plain JBoss AS 7. We plan 
to have a slimmed down TB called TorqueBox Lite, that will run as a 
RubyGem directly. It's obvious that we would like to slim down the JBoss 
AS distribution itself too since >120MB is too big for a reasonable 
sized Gem. I dropped everything we don't need and I end up with JBoss AS 
distribution that weights ~15MB.

In the TB Lite version we don't need several of AS7 subsystems, that are 
required in the normal TB distribution. One example is the jmx 
subsystem. It's currently marked as optional in the TB core subsystem.

How can I make sure I use the jmx subsystem only when it's available? It 
would be ideally if we could disable some subsystems without breaking 
the platform and instead just remove some features. What's the best way 
to do it?

Thanks!

--Marek
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev




More information about the rhq-devel mailing list