Java Development

[shubhra]

When you register a lisenter to monitor for Incoming and outgoing PIN messages, In the callback you always get  message.getMessageType() = Email_Message and NOT PIN_Message whether the device gets/sends email or a PIN message.

I'm using JDE API version 4.3.0. Is this s known bug? Any workarounds to this?

Is there any authoritative answer?

Thanks.

[shubhra]

When you register a lisenter to monitor for Incoming and outgoing PIN messages, In the callback you always get  message.getMessageType() = Email_Message and NOT PIN_Message whether the device gets/sends email or a PIN message.

I'm using JDE API version 4.3.0. Is this s known bug? Any workarounds to this?

Is there any authoritative answer?

Thanks.

[BBDeveloper]

Check this thread.

http://supportforums.blackberry.com/t5/Java-Development/IS-this-a-known-bug-on-RIM-API/m-p/38415

[shubhra]

Thanks BBDeveloper.

I checked it. But in my case things are going wrong in v 4.3.0 as well (the post says that worng value is returned from 4.5.0 onwards). I just want to make it sure whether 4.3.0 is faulty?

[BBDeveloper]

Have you got a chance to check on other versions.. 4.2 etc?

[RexDoug]

What is your test environment?

[shubhra]

Thanks for your responses guys :-)

I'm coding on Eclipse and running the simulator using JDE. I use JDE 4.3.0 and when I attach the simulator to handheld (Bold device) and then send/receive PIN messages to/from another device, I see in debugging that the message.getMessageType() returned is always net.rim.blackberry.api.mail.Message.EMAIL_MESSAGE and never net.rim.blackberry.api.mail.Message.PIN_MESSAGE.  I'm using folder events to listen to messages.

I want to know if this a known problem in JDE 4.3.0 and what do I do about it? any workarounds/alternate solutions?

[BBDeveloper]

Is the device also running with the same OS version?

If you are trying to differentiate between use a work around like get the Message which has come and differentiate based on presence of @.

[shubhra]

I'm using Bold device whose OS version is 4.6 and the JDE version is 4.3. So the versions of JDE and device OS do not match.

Let me do that and then I'll tell you how much feasible it is.

Do tell me any more new appraoches/workarounds if any...

Thanks

[RexDoug · Accepted solution]

This feature is broken in 4.5 and 4.6 OS - it has nothing to do with the JDE level.

If you compile on 4.3 and run on 4.6, you will see the issue.

[shubhra]

Thanks RexDoug. You cleared my doubt.