RE: [Quickfix-developers] fromAdmin / fromApp callbacks in Application interface (java)

[Alvin W. <AW...@FF...>]

Hi Dave, 

I can understand where you are coming from. But I think an onError 
callback is more straighforward.  Otherwise, we would have to use the 
seqnum to retrieve the original message from MySql (what if QF is 
configured to use other logging method?)

Thanks
Alvin








"Dave Linaker" <dav...@ma...>
06/07/2005 12:32 PM
Please respond to dave.linaker

 
        To:     "'Alvin Wang'" <AW...@FF...>, 
<qui...@li...>, 
<qui...@li...>
        cc: 
        bcc: 
        Subject:        RE: [Quickfix-developers] fromAdmin / fromApp callbacks in Application 
interface (java)


Hi Alvin,
 
As you say, fromApp and fromAdmin aren't called if the message is rejected 
at the Session level (i.e. if it fails the basic message validation) but 
toAdmin is called as a result of the Reject message being sent.  The 
Reject message will contain some basic information about why the message 
was rejected, at the very least a SeqNum and Text containing a description 
of why it was rejected.  So the application can be aware of the rejection, 
although it's not being passed the message. Were you looking for something 
more than this?
 
Kind regards
 
 
Dave
 
-----Original Message-----
From: qui...@li... 
[mailto:qui...@li...] On Behalf Of Alvin Wang
Sent: 07 June 2005 23:11
To: qui...@li...; 
qui...@li...
Subject: [Quickfix-developers] fromAdmin / fromApp callbacks in Application 
interface (java)


Hi, 

I have found that if a message is rejected by QF, fromAdmin or fromApp 
will not be invoked by QF. As a result, we have no knowledge about the 
message and what happened at all.  I can understand that QF tries to 
filter out those malformated msgs, but application should also be notified 
by some ways. (what about a callback called onError?) 

Thanks 
Alvin ********************************************************************** 
This e-mail message is intended solely for the use of the addressee. The 
message may contain information that is privileged and confidential. 
Disclosure to anyone other than the intended recipient is prohibited. If 
you are not the intended recipient, please do not disseminate, distribute 
or copy this communication, by e-mail or otherwise. Instead, please notify 
us immediately by return e-mail (including the original message with your 
reply) and then delete and discard all copies of the message. We have 
taken precautions to minimize the risk of transmitting software viruses 
but nevertheless advise you to carry out your own virus checks on any 
attachment to this message. We accept no liability for any loss or damage 
caused by software viruses. 
**********************************************************************