Logkit: Specify ErrorHandler on Constructor for JMS

[da...@hic.gov.au]

Here (finally) are these changes to allow the application to specify an
error handler when instantiating the JMS Target. BTW I have been having
some
problems with posting. I suspect that it just me but the error
is Enhanced Mail System Status Code (RFC1893): 4.2.0 (4 - Transient 2 -
Mail Box Status and
0 - Other or undefined mailbox status) which hints at a recipient problem.

The handling of any exceptions (on say connecting or context lookups) is
therefore under the complete control of the app.

Diffs preceed the actual code. We use VAJ here at work and it has the habit
of sorting all the methods alphabetically
and does not preserve the original order of CVS source. Had to play around
to produce the diffs shown here - otherwise
the diffs make no sense whatsoever.

(See attached file: AbstractTarget.diff)


(See attached file: AbstractTarget.java)

     (See attached file: AbstractJMSTarget.diff)
(See attached file: AbstractJMSTarget.java)

         (See attached file: JMSQueueTarget.diff)

(See attached file: JMSQueueTarget.java)
(See attached file: JMSTopicTarget.diff)
(See attached file: JMSTopicTarget.java)

Here is a jUnit test class for the above but I have not really tested the
classes beyond checking that the ErrorHandler cannot be null. At work we
are using an MQ target which has been tested however and I have seen it
throw exceptions when the connection to MQ fails.

(See attached file: ConstructorErrorHandler.java)



(See attached file: AbstractTarget.java)
(See attached file: AbstractJMSTarget.java)
(See attached file: JMSQueueTarget.java)
(See attached file: JMSTopicTarget.java)
(See attached file: ConstructorErrorHandler.java)

****************************************************************
NOTICE - This message is intended only for the use of the
addressee named above and may contain privileged and
confidential information.  If you are not the intended recipient
of this message you are hereby notified that you must not
disseminate, copy or take any action based upon it.  If you
received this message in error please notify HIC immediately.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of HIC.
****************************************************************

(See attached file: AbstractTarget.diff)
(See attached file: AbstractJMSTarget.diff)
(See attached file: JMSQueueTarget.diff)
(See attached file: JMSTopicTarget.diff)
(See attached file: AbstractTarget.java)
(See attached file: AbstractJMSTarget.java)
(See attached file: JMSQueueTarget.java)
(See attached file: JMSTopicTarget.java)
(See attached file: ConstructorErrorHandler.java)
(See attached file: AbstractTarget.diff)
(See attached file: AbstractJMSTarget.diff)
(See attached file: JMSQueueTarget.diff)
(See attached file: JMSTopicTarget.diff)
(See attached file: AbstractTarget.java)
(See attached file: AbstractJMSTarget.java)
(See attached file: JMSQueueTarget.java)
(See attached file: JMSTopicTarget.java)
(See attached file: ConstructorErrorHandler.java)

Re: Logkit: Specify ErrorHandler on Constructor for JMS

[Peter Donald <pe...@apache.org>]

On Fri, 17 May 2002 10:13, david.gray@hic.gov.au wrote:
> The handling of any exceptions (on say connecting or context lookups) is
> therefore under the complete control of the app.

thanks - patches applied!

-- 
Cheers,

Peter Donald


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>