layout question

[llo...@oreillyauto.com]

I'm in the process of refactoring some code and getting it ready for 3.0 in the process.

I'm trying to better modularize things as well.

I've got a general tomcat module, but I also have a number of tomcat related things that only apply to one class of appserver we have.

What would be the best way of handling these?

Should I create a module, say, teamname_tomcat and have it inherit from the main tomcat and put the various defines and classes needed for this one grouping of tomcat installs there? Though that would involve cross-module inheritance, which I understand to be A Bad Thing(tm). Though I guess I could just have it require / include the tomcat module.

I've got a few other modules where a specific grouping of instances will have/need special defines and classes that the most instances won't need.

Any recommendations would be appreciated.

Thanks.

[Felix Frank]

Hi,

On 07/09/2012 08:17 PM, llo...@oreillyauto.com wrote:
> What would be the best way of handling these?

that's really hard to say at this level of granularity.

Can you name a typical example of what can differ among appserver classes?

[llo...@oreillyauto.com]

Comments in line.

On Tuesday, July 10, 2012 8:39:17 AM UTC-5, Felix.Frank wrote:

Hi,

On 07/09/2012 08:17 PM, llowder wrote:
> What would be the best way of handling these?

that's really hard to say at this level of granularity.

Can you name a typical example of what can differ among appserver classes?

In one of our clusters we override/rewrite the tomcat init script and also  also remove all of tomcat's daily cron jobs, as we use a different logrotation scheme.

Our standalone / special purpose tomcat instances use the default init script and logrotation methods.

We do something similar with one of the apache clusters vs the handful of standalone / special purpose apache instances.