Re: Java servlet on browsers: dying or kicking ?
On 28.12.2012 22:08, lipska the kat wrote:
On 28/12/12 20:22, Robert Klemme wrote:
On 28.12.2012 18:50, lipska the kat wrote:
I spend much of my working life translating a clients business processes
into something that can run on a computer and the trend is now more than
ever away from a strictly web based process and towards systems that are
completely independent of delivery mechanism.
This sounds exactly like the use case JEE was intended for.
Well yes, I remember early days writing EJB deployment descriptors by
hand. What a hideous nightmare that was. An early, poorly documented
version of Weblogic and trying to figure out how everything was glued
together because the company couldn't afford the price of Weblogic
training. RMI over IIOP, stubs and skeletons, oh misery thy name is J2EE
... and don't get me started on the Sun One application stack
But you did notice that things have considerably changed in JEE world,
did you?
You know what, I don't actually use it much these days. I have a bunch
of classes that implement the core business logic. A facade hides the
atomic business logic methods from clients and people write to the
facade. Need more functionality ... no problem, update the facade by
combining atomic methods in new ways.
I rarely use web frameworks either, or persistence frameworks or any
other type of framework unless the client specifically requests it.
I still write most of my own SQL ... for the same reason I still write
stuff in assembler. It just seems like a good idea to stay close to the
machine/problem space
This sounds like a case of NIH syndrome. It may actually be that you'd
be better off with all the framework logic though. If things work well
for you the way they are then that's good.
Validation is done serverside, client side validation is a nice thing to
have but I would never rely on this, I would always back it up on the
server, after all, validation can be a fundamental part of your business
logic.
Absolutely.
Cheers
robert
--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/