>> I always have trouble naming my projects. "Pluggable Popsicles" would be a great name for a persistence engine. Can I steal it?
Sure go ahead. ;P
I agree with everything you said. I just think we ought to be focusing on what creates value (technology) and not on buzzwords.
>> Threadweaver, you've told us you don't like CMP-EJB and don't like CORBA. What do you like to use?
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?
>>(New EJB specs are like a bad sequel to a bad movie, "EJB 4: CMP -- The Apology.") LMFAO.
>> Threadweaver, treating your data-bearing objects as immutable documents works wonders in concurrent systems. Agreed. I was just saying that is not required in strict-english interpretation of the term SOA since, any service could represent SOA under the terms defined in the dictionary.
>> Wow... I didn't expect a philosophical discussion. I was hoping more for comments like, "I'm using technology X to get feature A," so I could skip over the drab also-ran technologies to the good stuff.
I have been attacked for that in other circles (if you want more info let me know). Ultimately, I think that people that are good natured generally want answers rather than to cling to some dogma. I want working answers as well, but it seems logical to me that it is impossible to arrive at a result other than confusion without a mutual definition of terms at the outset. In other words, I think it will be easier to arrive at things that work in the real world if we are speaking the same language. |
java.net RSS Feeds
