> For a moment I wasn't understanding why you were writing in english :-)
:) since I'm lunking here for a while decided to start posting here. > In any case: > > + there's a very simple pubsub EventBus behind the scenes which broadcasts > messages, and the topic is the message class > + @MessageListener is used by reflection to register the method as listener > for the topic given by its unique parameter > + @Message is just used for a formal check (@MessageListener methods must > have a single @Message parameter) > + @Actor is currently not used in the small test, but in a real thing it > would be used for classpath discovery and actor instantiation > + each actor instance is backed by an EventBus listener that receives the > message and posts it to a simple worker executor which dispatches to a pool > of threads each actor is on its own thread, correct? I have similar needs too (apart that my actors need to dynamically start and stop and maybe work with osgi services). One thing about I'm not sure is how to integrate normal threads (aka servlets) with actors. I'm speaking from a clean design perspective. > simple things for solving simple problems. Fortunately, there are a lot of > simple problems around, but the lack of simple solutions is the main reason > for the excessive growth of classpath. +1 :) > > For the record, my code is at > https://bitbucket.org/tidalwave/bluemarine-integritychecker-src/ but it's > still very rough (it's an incomplete NetBeans Platform project and to run a > small test you need to manually launch a Main from inside the NetBeans IDE). I'll look at it, thanks Uberto -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
