Hi Steven,

Thank you for the good wishes.

I've been testing from inside out. So I did test the loading first prior to checking the translator.

$perl
use Admin_server::Parser;
use Admin_server::Parser::Plugin::Feedhandler;
[download]

I don't get any errors.

Also,

$prove -lv t/Plugin/FeedHandler.t 
t/Plugin/FeedHandler.t .. 
1..34
ok 1 - use Admin_server::Parser::Plugin::FeedHandler;
ok 2 - Admin_server::Parser::Plugin::Feedhandler can be instantiated.
ok 3 - Instantiated object is of type Admin_server::Parser::Plugin::Fe
+edhandler.
ok 4 - Conforms to canonized plugin interface - does Admin_server::Int
+erface::ParserInterface.
ok 5 - Feed handler application correctly identified.
ok 6 - tell_instance_info succesfully called.
ok 7 - tell_instance_info returns a hash reference.
ok 8 - tell_instance_info return hash has a key of 'instance_name'.
ok 9 - Instance name correctly extracted from first line of log4x data
+.
ok 10 - Instance name negative test successful.
ok 11 - Instance name negative test successful.
ok 12 - tell_script_names successfully called.
ok 13 - tell_script_names returns a hash.
ok 14 - The tell_script_names return hash has a key of start_script.
ok 15 - The tell_script_names return hash has a key of stop_script.
ok 16 - Start script name correctly extracted from first line of log4x
+ data.
ok 17 - Stop script name correctly extracted from first line of log4x 
+data.
ok 18 - Start script name negative test successful - (with erroneous d
+ata).
ok 19 - Stop script name negative test successful - (with erroneous da
+ta).
ok 20 - Start script name negative test successful - (with undef data)
+.
ok 21 - Stop script name negative test successful - (with undef data).
ok 22 - tell_status successfully called with a log4x line not having a
+n error.
ok 23 - tell_status returns a hash.
ok 24 - tell_status correctly diagnoses feed handler as up.
ok 25 - tell_status return hash doesn't have the app_down key when app
+ is up.
ok 26 - tell_status return hash doesn't have the app_unknown key when 
+app is up.
ok 27 - tell_status successfully called with a log4x line having an er
+ror.
ok 28 - The tell_status correctly diagnoses feed handler as down.
ok 29 - tell_status return hash doesn't have the app_up key when app i
+s down.
ok 30 - tell_status return hash doesn't have the app_unknown key when 
+app is down.
ok 31 - tell_status successfully called with a undef value.
ok 32 - The tell_status correctly diagnoses feed handler status as unk
+nown.
ok 33 - tell_status return hash doesn't have the app_up key when app i
+s unknown.
ok 34 - tell_status return hash doesn't have the app_unknown key when 
+app is unknown.
ok
All tests successful.
Files=1, Tests=34,  1 wallclock secs ( 0.03 usr  0.01 sys +  0.22 cusr
+  0.02 csys =  0.28 CPU)
Result: PASS
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.