[Quickfix-developers] Re: empty tag

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

Oren, I can understand where you are coming from. It makes total sense if 
QF throws NoTagValue exception in this case. However, I just feel it will add workload to the developers 
and the production may become disruptive. 

Thanks
Alvin






"Oren Miller" <or...@qu...>
07/05/2005 10:00 AM

 
        To:     <qui...@li...>, 
<qui...@li...>, "Alvin Wang" 
<AW...@FF...>
        cc: 
        bcc: 
        Subject:        Re: empty tag


We could, although more likely I would throw a NoTagValue exception.  I 
don't much like the idea of having QF silently ignoring a field that the 
developer would be expecting to go out in the message (much like I don't 
like the current behavior).  I can imagine the head scratching that would 
go on if they added a field and then found it mysteriously absent in the 
logs.
 
In either case if you have a field that might contain a blank value, I 
would suggest checking it before adding it to a message.
 
--oren
----- Original Message ----- 
From: Alvin Wang 
To: qui...@li... ; qui...@li... 
Cc: Oren Miller 
Sent: Tuesday, July 05, 2005 9:10 PM
Subject: empty tag


HI 

If I set a tag as below: 
message.set(new Text(text)); 
and if the variable "text" is null. QF will include an empty tag 58. As a 
result, some FIX engine (such as QF itself) on the other end will reject 
the message.  Can QF skip including empty tag? 

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. 
**********************************************************************