[Wrapper-user] Java Classpath and Cascading Include Files

[Sean A. <say...@gm...>]

Hey,

I am currently using version 3.3.0 of the Java Service Wrapper.  We've been
running the wrapper successfully for awhile with an #include file that
includes the default initialization parameters for our services.

I recently attempted to create include files for some of the common java
classpath entries that were occurring in all our service wrapper
configuration files.  I gave each of these include files their own range of
values for the wrapper.java.classpath.<n> properties (i.e. first one has the
range of 100-199, second has the range of 200-299, etc).  I turned on the
#include.debug and I can see that every include file is being located when
the services are installed/uninstalled.  Each include file also sets the
wrapper.ignore_sequence_gaps property to TRUE.

With all debugging turned on, I can see the full java command being run and
can tell that the classpath entries in the include files are NOT being added
to the classpath argument, and the only ones found within the classpath
argument are the ones explicitly listed in the service's own .conf file.  I
can't find anywhere in the documentation that would indicate that the
wrapper.java.classpath.<n> properties can't be used within #include files,
so I am just curious as to why the classpath entries in my "#include" file
are not being picked up but the ones in the servicename-wrapper.conf files
are (ignore_sequence_gaps has been set to true).

Thanks,
Sean A.