Ask questions and see you at 11th April at 6.PM. CET: http://www.ustream.tv/channel/adambien Also see archives: airhacks.tv
- Java EE 8 News
- 2 years of airhacks.tv celebration (now really 2 years)
- Do you think NetBeans is still a good IDE for JEE, Java, HTML, SPA, etc, development in 2016? I'm currently faced with a number of developers who seem to love IntelliJ, but I'd love a free alternative for some of our projects. We're currently using Eclipse (and STS), but that platform doesn't agree with me which is why I'm considering NetBeans. I know I should just make up my own mind about this, but I appreciate your work a lot and would love to hear your opinion.
- How to access the "other side" with afterburner.fx?:
@Service
public class Receiver {
private long counter = 0;
@PostConstruct
public void init() {
System.out.println("Receiver.init()");
}
@RabbitListener(queues = "hello")
public void receiveMessage(Message message) {
String s = new String(message.getBody());
// msgRepository.save(new Msg(null, s));
Platform.runLater(() -> {
counter++;
System.out.println("Received <" + s + ">" + counter);
//I want to print this log to JavaFx Label
});
}
}
I was listening to one of the recent Airhacks and I think you mentioned that you rarely put business logic in Entities. I dug up these old blog posts of yours:
These are almost 10 years old, so I understand your thinking should change. I'm just bringing these up for comparison.
I've read your description of ECB/BCE, and looking at Lightfish I see no business logic in the Escalation entity. On the other hand, in javaee-bce-archetype you have a small amount of business logic in Registration.
It seems like good object-oriented design to put business logic in our business objects. Do you have some updated advice on this?
I think I'm not alone in feeling that thin entities and EJBs pull us away from object-oriented design. EJBs aren't objects, and if our entities are thin, they're anemic objects. I don't think object-oriented design is some Ultimate Paradigm that is only productive when we strictly adhere to it, but to me it just seems like a good idea for business objects to "own" their business logic.