the blog for developers

Is werx dead?

Werx is a type safe intra-application message bus in Java. I’ve been a happy werx user for a while, but when I headed back to the werx website the developers obvisously haven’t renewed their domain (downloads can be still found on the werx sf website;). The developers aren’t answering questions, so is the project dead?

You can leave a Reply here. Of course, you should follow me on twitter here.

You can share this post!
Do you want to tell others about this article? Use the social bookmark icons to submit this artice to the service of your choice. Thanks.

About the author: Stephan Schmidt is head of development at brands4friends. He has more than 15 years of internet technology experience and 10 years experience in agile. He was head of development, consultant and CTO and is a speaker, author and blog writer. He specializes in organizing and optimizing software development helping companies by increasing productivity with lean software development and agile methodologies. Want to know more? All views are only his own.
Leave a reply.

Comments

I`m currently working on a lightweight message solution for in a single vm. Although the website hasn’t been updated for some time ( http://channels.sourceforge.net ) I`m currently working on it at home and in the very near future I want to update the whole website and make some serious work from it.

The company I work for (http://www.jteam.nl ) wants that all employees get involved with opensource projects: assisting projects or creating it themselfes. So this is a good chance to do some serious work on the channels project.

I`m also working on a concurrency library that extends and complements the concurrency library of Java 5. The channels library depends on the concurrency library in some cases.

stephan

A great, I’ll take a look, thanks.

I haven’t released any sources. So you can’t download anything.

But in the near future I can give a ‘alpha’ version to you if you want. What are you going to use it for?

stephan

I like message buses for intra-application communication. That greatly decouples services from each other.

What did you think of the threading control in Werx? Personally I thought it sucked because you don’t have much control (if I remeber most channels were active by default). The whole idea behind my Channels project is that components should be very configurable and give complete control on the threading behaviour (like blocking, number of threads, priority of threads, maximum number of messages in the buffers etc etc etc)

stephan

Yes, the threading in werx is only basic. The nice things in werx, for which I chose it, are:

- easy to develop (Reflection finds channel() methods, no framework dependencies for receivers)
- type safe, type hierarchy
- listen to supertype messages (e.g. all StorageMessages = UserStorageMessage, PageStorageMessage)
- easy to use

Threading wasn’t such a big problem, but more control would be nice.

Leave a Reply

What people wrote somewhere else:

Additional comments powered by BackType