Earlier quoted context omitted.
> The framework basically forces you to abandon messaging (since there is no exchange of messages, just single directional messages flow from the router), The services receive messages from the router, then send messages to whatever they need to call to get the job done. Being sent messages by the framework is what makes it a framework and not a library; I don't get your objection here. > abandon encapsulation (since…
The services receive messages from the router, then send messages to whatever they need to call to get the job done. Being sent messages by the framework is what makes it a framework and not a library; I don't get your objection here. If it was a framework modelled in an object oriented way it would itself be built of classes exchanging messages, but it isn't. It encourages you to also structure your code in a non ob…
Eh? The sentence you quoted explains that putting domain logic in the persistence objects is precisely what objectify avoids. I do't see any examples of domain logic as separate from persistence logic at all in the examples, so I'm not sure where you're getting the idea that the framework encourages it from. If you're that tied to "how Rails works", why are we even discussing this? Objectify exists to change the way Rails works, because the way Rails works is broken.
> Ehm, no?
Ehm, yes.
class MyFunkyResolver
def new
5
end
end
Foo = MyFunkyResolver.new
p Foo.new
# 5