views:

131

answers:

4

I'm looking forward to start developing a new server side enterprise communication framework in Java and I'm wondering if anyone knows a good book on the subject? Some best practices and advice would be welcome.

Thanks.

+6  A: 

"Practical API Design: Confessions of a Java Framework Architect" by Jaroslav Tulach (NetBeans architect) sounds like the best fit you're going to find.

But the best advice on developing new frameworks is: don't. Especially if you have to ask. It's very unlikely that you'll do a better job than all the people who wrote the multitude of frameworks already out there.

Michael Borgwardt
+1 Best advice!
Stephen C
The problem is that there is no framework that fits my needs. Thanks for the book, sounds promising.
Andrejj
@user459493, not to sound like a prick here, but are you really sure that no framework suits your needs in enterprise communication (presumably, messaging is the right word) ? That topic is more or less well studied, and certainly an existing framework would take care of **most of your** needs.
Vineet Reynolds
Well most it's not enough, we are integrating two eDMS systems, both proprietary. So if you can suggest a framework that could fit the profile I will be very grateful.
Andrejj
+2  A: 

"How To Design A Good API and Why it Matters" by Josh Bloch.

http://www.youtube.com/watch?v=aAb7hSCtvGw

mindas
+1  A: 

A couple of recommended books:

Péter Török
A: 

I don't know how exactly your eDMSs should connect which each other, if they are code compatible etc. But this may be helpful for you.

Check Java Content Repository (JCR) standard and JBoss ModeShape as implementation. Most of content (also document) repository software providers are JCR-Compliant, e.g. Alfresco but also other not related with Java.

Instead of writing own framework, just write simple ModeShape JCR connector for your eDMS. Then you can easly do federated DMSes, replication, use existing repository management tools, expose your repos via Web Dav, REST, comunicate with other protocols, and do many many other things with opensourced and commercial tools - your repository just must provide JCR connector.

gertas
They should be fully integrated (2 way communication, document search, etc.), one is written in Java and the other one is in .net. They are both written by us so there is maybe some room for modification of the existing code. Thanks for the suggestion.
Andrejj
Check also this article http://dev.day.com/content/ddc/blog/2008/01/fudbusting2.html about using JCR outside Java.
gertas