When introduced to JSR 371 (MVC 1.0), the first issue that comes to mind is JSF. Reza Rahman explains that MVC is not replacing JSF and, perhaps more importantly, why we need both frameworks in Java EE.
Arun Gupta shows us how to secure your WebSocket based application. Including code and config samples.
Reza Rahman points out an interesting alternative to JPA for ORM in EE applications using CDI to connect to MyBatis, which relies heavily on native SQL queries.
Val Huber outlines a process for creating a RESTful solution that addresses the common concerns around enterprise database access, including what you can reasonably expect from your REST vendors.
Michael Scharhag Provides a slightly different take on using DI; rather than injecting a service (or repo, or other resource), he suggest directly injecting the desired domain object. Code samples using spring, with a description of changes needed to use CDI.
Another Great Issue of Java Magazine has just been released. This one focused on expanding the next generation of the Java Community as well as Java running in places other than the traditional servers and workstations. IoT and Robots and Pi! Oh, My!
Peter Lawrey walks us through some of the idiosyncrasies of casting between numeric types and performing mixed type arithmetic. Fair warning: this one may make your brain hurt.
1. On English site, create new content
URL on English site = myDecodedToken/nodeTitle
URL on Spanish site = es/myDecodedToken/nodeTitle
(so only 1 of the 3 node module tokens decodes)
2. On English site, add Spanish translation
URL on English site (has miraculously changed) = node/"nid"
URL on Spanish site = es/nodeJoinPath/nodeName/myDecodedToken/nodeTitle
(so Spanish site is correct)
Alex Zhitnitsky gives us a glimpse into the Java Community Process and shows us the process required for a change to Java, and how you can help. That's right folks, not only should you pay attention to the man behind the curtain, you could even be the man behind the curtain.
Sivaprasadreddy Katamreddy offers some opinions on the IDE flame wars from the perspective of an Eclipse user and includes strengths and weaknesses for each option.