I am trying to figure out the architecture of a prototype application.
In it, the presentation layer (Wicket) needs to work with a service
layer to display and edit lists (among other things). The service
layer also exposes some Web Services via SOAP/REST which I intend to
use for a
Put your services in the same webapp.
On Tue, Mar 24, 2009 at 11:37 AM, Kaspar Fischer fisch...@inf.ethz.ch wrote:
I am trying to figure out the architecture of a prototype application. In
it, the presentation layer (Wicket) needs to work with a service layer to
display and edit lists (among
Yes, I suggest to you the same approach. Put everything in the same
webapp, just take care to separate the tiers.
For example: don't modify inside a service method the method
parameters because it won't work in a EJB for example.
I used to build a huge environment n-tier with different jar files
On Tue, Mar 24, 2009 at 11:56 AM, Eduardo Nunes esnu...@gmail.com wrote:
I always use DTO in service methods. My point of view is that if you
have a method named getSimpleUserList and your User entity has 10
attributes and for this simple list you just need 3 of them, doesn't
make sense to me
I agree wholeheartedly with both of James' points. Put it all in the same
webapp until you are absolutely certain that you've outgrown that. And I
don't like DTO's. Why is it better to return an object that only has
three fields when you don't need all ten? Doesn't this imply that you've
Yes, I understand you too. What do you do when you have to send a set
of entities and a calculation for each entity? you encapsulate it
inside another class?
On Tue, Mar 24, 2009 at 1:02 PM, James Carman
jcar...@carmanconsulting.com wrote:
On Tue, Mar 24, 2009 at 11:56 AM, Eduardo Nunes
On Tue, Mar 24, 2009 at 12:08 PM, Eduardo Nunes esnu...@gmail.com wrote:
Yes, I understand you too. What do you do when you have to send a set
of entities and a calculation for each entity? you encapsulate it
inside another class?
A domain-driven design advocate would say that the entity knows
Agree again.
--
Jeremy Thomerson
http://www.wickettraining.com
On Tue, Mar 24, 2009 at 11:11 AM, James Carman jcar...@carmanconsulting.com
wrote:
On Tue, Mar 24, 2009 at 12:08 PM, Eduardo Nunes esnu...@gmail.com wrote:
Yes, I understand you too. What do you do when you have to send a set
Ok I got it. One question, consider that you have this model:
Person 1xN Address
You have a screen that list a detailed view of a person, including a
list of addresses. What approach do you use to implement it?
- A service method that returns a Person entity with eager load of the
list of
James, Eduardo, Jeremy, thank you very much for your input!
I follow your discussions with great interest.
Can you recommend a book on this sort of questions? I have read books
on Spring and Hibernate but not from this high-level point of view.
Cheers,
Kaspar
On 24.03.2009, at 17:38,
in context:
http://www.nabble.com/OT%3A-How-to-connect-Wicket-layer-to-underlying-service-layer-tp22683138p22684726.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
Maybe Eric Evans Book 'Domain-Driven Design'?
Kaspar Fischer wrote:
James, Eduardo, Jeremy, thank you very much for your input!
I follow your discussions with great interest.
Can you recommend a book on this sort of questions? I have read books
on Spring and Hibernate but not from this
On Tue, Mar 24, 2009 at 12:53 PM, Dave Schoorl mailli...@cyber-d.com wrote:
Maybe Eric Evans Book 'Domain-Driven Design'?
Yep, that's the one I would suggest. Although, I am going to check
out Fowler's book too. That's one I don't have yet! :)
Me too, it's not easy to find these books in Brazil, I will try to buy
a electronic copy of it.
On Tue, Mar 24, 2009 at 2:40 PM, James Carman
jcar...@carmanconsulting.com wrote:
On Tue, Mar 24, 2009 at 12:53 PM, Dave Schoorl mailli...@cyber-d.com wrote:
Maybe Eric Evans Book 'Domain-Driven
14 matches
Mail list logo
