Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion Threading Policies
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Stefan Weber  
View profile  
 More options Nov 12 2009, 9:08 am
From: Stefan Weber <stefan.we...@gmail.com>
Date: Thu, 12 Nov 2009 15:08:08 +0100
Local: Thurs, Nov 12 2009 9:08 am
Subject: Re: Threading Policies

On Thu, Nov 12, 2009 at 2:56 PM, Sergio Bossa <sergio.bo...@gmail.com>wrote:

> I've lost you there: even if you get a generic Message instance,
> CoreHandler works by reflection and you don't need to do any wrapping.
> In other words, if you get a generic Message whose actual type is
> BarMessage, and you annotate your handler object with
> @OnMessage(type=BarMessage.class), CoreHandler will call the correct
> method.

> Does it make sense for your use case, or am I getting it wrong?

It makes sense, but unfortunately not for my use case ;)

In short: the dynamic type of the Message I'm getting is NOT BarMessage.

Example: I get an ASCII string from the network and wrap it in a Message.
Then I call getMessageType on it and Message will parse the ASCII string and
return the message type. Only then I know what specific message it is.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.