Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=4279288
By: rob_blake
Rob,
No that class is the actual code for the check_http plugin itself. But it looks
like the plugin code is being bundled up with the web application code as well.
I can't really see a reason for this to be so (other than it's easier for our
build process to include everything that way) so I'll open up a low priority
feature request to get this ironed out for the next release.
The code that you are interested in running is the blue-check-http.jar that
resides in the $BLUE_HOME directory. Essentially this acts as a wrapper for
the check_http.class so when you run java -jar blue-check-http.jar from within
Blue, its actually calling the check_http.class. The version of the check_http.class
that is executed is contained within the blue-plugins.jar (hence me wondering
why there is a need for us to bundle the plugin code with the webapp other than
for ease of build) in the ~lib directory of your Blue installation. The
blue-check-http.jar version does a few house keeping tasks such as setting the
correct classpath for the check_http.class. The check_http plugin makes use
of the commons-httpclient libraries from Apache and these need to be on the
classpath of the plugin at runtime.
Thanks for the testing offer. Any feedback is appreciated. I'll try and set
aside some time for finishing off the check_http plugin shortly.
cheers
Rob
______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=545812
|
