[Beepcore-java-users] problem w/ MessageStatus

[Ben F. <me...@be...>]

Hey ya'll,

I've invested some significant time in the last several days working on
idxp4j <http://sourceforge.net/projects/idxp-java/>.  The project coming
along pretty well (if slowly), but I'm stuck on a problem w/ the
MessageStatus returned from a call to sendMSG().  So I decided taht I its
time to call in all ya'll Beepcore-Java experts out there :)

I have an example IdxpDaemon (nearly identical to Beepd, but w/o any
config file or CLI args) and an example IdxpInitiatorClient.  The
IdxpDaemon and IdxpInitiatorClient are successfully completeing the IDXP
handshake.  After the handshake is complete, the IdxpInitiatorClient
attempts to send several dummy "Hello World" messages before tearing down
the channel and session.  (starting at IdxpInitiatorClient:255).  This is
where the problem is occuring.

After sending the first dummy msg using the Channel.sendMSG() method, I
check the status, as always. (see switch at IdxpInitiatorClient:281)  The
numeric status is always equal to MessageStatus.MESSAGE_STATUS_UNK.  This
is unlike the other MSGs sent by my example programs, whose status' are
always set to MessageStatus.MESSAGE_STATUS_SENT.  I've even added a loop
around the status check, hoping that eventually the status would become
MessageStatus.MESSAGE_STATUS_SENT.  No luck, it seems to be hung on
MessageStatus.MESSAGE_STATUS_UNK.

Could someone check out the idxp4j CVS tree and try to reproduce this
behavior?  Any ideas why the status is always
MessageStatus.MESSAGE_STATUS_UNK?

Also, is it expected behavior for sendRPY to have a return status of
MessageStatus.MESSAGE_STATUS_UNK?  It would almost make more sense to have
several different sets of status values, for the various sendXXX methods,
since one set of status' is kind of confusing for different all the
different message types (MSG, RPY, ERR, NUL, ANS).

Thanks much!,
Ben