StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow can I create a component-based message handling system with traits?
primarykey
Id
5425380
data
AcceptedAnswerId
0
AnswerCount
3
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-03-24T20:53:32.337
FavoriteCount
1
LastActivityDate
2011-03-27T20:53:28.410
LastEditDate
2011-03-25T03:08:53.627
LastEditorUserId
49018
OwnerUserId
49018
ParentId
0
PostTypeId
1
Score
2
ViewCount
319
LastEditorDisplayName
text
Body
Here's a short example of what I want to do: <pre><code>abstract class Message() case class FooMessage() extends Message case class BarMessage() extends Message //... other messages ... trait Component { def handleMessage(msg: Message):Unit } trait ComponentType1 extends Component { abstract override def handleMessage(msg: FooMessage) = { //handle foo, pass it up the chain super.handleMessage(msg) } abstract override def handleMessage(msg: BarMessage) = { //handle bar, pass it up the chain super.handleMessage(msg) } } //handles some other messages, also might handle the same messages as ComponentType1 trait ComponentType2 extends Component { .. } </code></pre> Then, these <code>ComponentType</code>s are mixed in to a class to form an object that is completely composed of modular components. I have a bunch of different <code>Message</code>s and a bunch of different <code>Component</code>s. <ul> <li>Not all components handle all message types.</li> <li>Multiple components can handle the same message type. <ul> <li>The message cascades up through the components, even if it's handled by another component.</li> </ul></li> <li>A Component can handle more than one message type.</li> </ul> The problem is since <code>handleMessage</code> is defined in <code>Component</code> as accepting a <code>Message</code>, when I try to specialize the <code>msg</code> parameter it doesn't count as an override. I know one possible solution to this is to declare a big <code>handleMessage</code> method with a big match statement, but I'd like to define a method per message if possible.
Tags
<oop><scala><types>
Title
How can I create a component-based message handling system with traits?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USryeguy
UserOwnerUserId
1. USryeguy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHow can I create a component-based message handling system with traits?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POHow can I create a component-based message handling system with traits?
 UserUserId
 USMike
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POHow can I create a component-based message handling system with traits?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.