Gabor
Unregistered
|
|
Carlo,
Thank You for your clear answer. I'm a newbie for OO paradigme (I have som VB experience), so apologize for the stupid question.
Does it mean, if we have an association between two classes, and need some attribute from the server object, we have to send the client object via interface to the server, that fills the requested properties via interface's method?
Thanks
Gabor
|
Anonymous
Unregistered
|
|
What about... <% IDisplayPerson personDisplay = Person.getDisplay(request); %> <table><tr><td>
<%= personDisplay.getProperty("name_css_id") %> <%= personDisplay.getProperty("address_css_id") %> </table></td></tr>
|
Anonymous
Unregistered
|
|
---------------- If you want me to explain why I believe high cohesion and low coupling are desireable, let me know. ---------------- good one that should shut some of those 'closed-minded, unwilling to admit that they're not world's greatest programmers' suckers up...
|
Anonymous
Unregistered
|
|
I agree with this method of minimizing the coupling between objects. But in the area's of persistence and viewing this method is only adding to the complexity. Secondly. I have to alter the java code when the interface changes, thats a big NONO in my book. The people that design the interface no nothing about java code, this means I need 2 people to do 1 simple thing.
I think this way of programming (Which I also do) is best used in the business domain and the controller domain. view and persistence domain are not suitable (with current tools) to adopt the suggested method in the article.
|
Pedant
Unregistered
|
|
Dear Mr. Hed, How can you tell if there is beer in the fridge (the Heisenberg's Beer Dilema) ? Just tell the beer to go drink itself !
|
Anonymous
Unregistered
|
|
you just made an business object dependent on HttpRequest. you will never be able to use this person class in any other environment but a web application. i think introducing a dependency from business layer to presentation layer is much much more evil then getters/setters.
remember: data goes up, dependencies go down !
|