patch_msg.txt
|
Relates |
|||
| is related to |
|
Add clear and isEmpty operation to Fi... | Closed |
[QFJ-25] Message constructor throws NullPointerException with empty string Created: 09/Jun/06 Updated: 02/Sep/06 Resolved: 10/Jun/06 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | Engine |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.1 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Oren Miller | Assignee: | Steve Bate |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
patch_msg.txt
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
I discovered this when passing an empty (not null) string into the message constructor. The parseHeader assumes that BeginString, Length, and MsgType will be present in the string, when in fact they might not be. This causes parseHeader to operate on a nul field returned by extractField. Below is a patch with tests. |
| Comments |
| Comment by Steve Bate [ 10/Jun/06 ] |
|
Patches applied to both the 1.0.x branch and the trunk |