>>For persistence, Hibernate, which I think has held up very well in the real world. For services, I still like EJB although I have not had time to really play with JINI or anything other than RMI (JRMP) yet. What about you?
Current project is very lightweight: JMS for comms (both between threads and between remote processes). Mostly immutable objects flowing between things via serialization. For the moment, we're using serialization for persistence. (I'm trying to keep a database out of our part of the system.) We've just hard-coded the orchestration in Java for now. JNDI for a service locator. We might eventually use JINI to build up a larger system.
EJB was originally for coordinating transactions over multiple XA resources. Are you actually using it for that? It does a great job, but the problem doesn't come up that often. I gave up tracking the spec after it passed 800 pages.
>>I agree with everything you said. I just think we ought to be focusing on what creates value (technology) and not on buzzwords.
I'm interested in what makes one technology useful, and another just resume crud. I think those things can be characterized, and the characterization can be collected into something that makes sense as a whole.
Buzzwords are an interesting facet of the problem, along with things in "util," things named "*Manager" and "*tion" words. People imagine them to mean whatever fits their view of the universe, then are disappointed when things don't work out. (Think of experiences with the word "documentation." Does it mean writing documents, reading documents, or doing something vague, not coding? How do you know when you're done?)
I think we're just now getting to the point where we can define what we want and start asking for it. I'm hoping we'll recognize it when we see it. JINI's an example of something great that most of us missed. |
java.net RSS Feeds
