I’ve participated in several Garage48 events in last few years. What I like about them is that it puts agile approach on steroids. As the event’s name suggests, a small team has only 48 hours to go from an idea on paper to a running app in production. And that brings streamlining to an extreme. One has no choice but to focus on development and avoid everything that even hints at overhead.
When you think about it, though, this approach is not reserved for 48-hour weekend hackathons only. It is applicable to startups as well. It is surprising how long a lean, lightweight dev environment can hold up. It’s only much, much later when the time is suitable for more heavyweight practices.
In late November, we announced that JRebel Remoting will be available for SAP Netweaver Cloud. That little announcement marked a major milestone in our efforts during the last year: namely, that we have added support for JRebel Remoting to all the major app servers and all the major IDE’s.
Our next goal is making JRebel Remoting available in all kinds of cloud environments such as Amazon EC2 (it’s done, try it), SAP Netweaver Cloud (we’re in beta), Heroku (it actually works), Jelastic, CloudBees, CloudFoundry and OpenShift.
Note: This tutorial is gonna show you how to code Java without any of the traditional B.S., like XML and app server restarts. It’s split into 3 parts so that your brain doesn’t freak out at a 50 meter long webpage. Enjoy!
Did you realize that Hibernate has been around for more than 10 years? And Spring will begin its second decade next year? There was a time when Spring+Hibernate was widely considered an unofficial industry standard, but today is portrayed as an ancient beast whose XML appetite kills little rainbow scroll wheels. That assessment is not true, however. Both technologies have seen continuous development and are still competitive today.
Doesn’t it make more sense to compare apples to apples? For example, don’t put JEE6 with CDI up against Spring 1.0. Spring and Hibernate don’t require three miles of XML anymore. In fact, it’s possible to set them both up with zero lines of XML.
With servlet 3.0, even web.xml can go the way of the dodo. When all you’re trying to accomplish is a simple helloWorld guestbook, then Java, Spring and Hibernate will require more effort to get there, but can you name any app which is that trivial in real life? Proper applications are expected to satisfy far greater needs, both functional and non-functional, which is the area where Java, supported by wisely-chosen tools & frameworks, really shines.
Note: This tutorial continues from Part 1 and is gonna show you how to code Java without any of the traditional B.S., like XML and app server restarts. It’s split into 3 parts so that your brain doesn’t freak out at a 50 meter long webpage. Enjoy!
Adding Hibernate to the mix is rather easy. All I need to do is add a few beans to the
WebappConfig class. Which beans to add depends whether you wish to stick to the classic Hibernate API that uses SessionFactory or switch to a modern JPA, which uses
EntityManager instead. Note that JPA is a specification and we’re still using Hibernate as an implementation. The basic concepts and programming model are the same for classic Hibernate and JPA, but in my opinion JPA is easier to set up and more beautiful, not to mention it being an official JEE specification. By the way, even when using plain old Hibernate, the class annotations such as
@Entity still belong to JPA.
Note: This tutorial continues from Part 2 and is gonna show you how to code Java without any of the traditional B.S., like tons of XML and app server restarts. It’s split into 3 parts so that your brain doesn’t freak out at a 50 meter long webpage. Enjoy!
Part 1 | Part 2 | Part 3
Enough with the setup, let’s write some code!
Once upon a time, Sun started with the PetStore sample application and Spring continued it with the PetClinic. Now that the cute little goblins have been bought and cared for, let’s publish their pictures for the whole world to see – introducing Snoutbook!
For those with only few minutes to spare, this post addresses the ways in which JRebel, Java’s famed redeploy killer, has made an impact on how developers spend their day coding. With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time learning and communicating with colleagues instead of waiting for the dreaded application redeploy to finish.Read more
Java is not dead…in fact, it’s got more than enough energy to kick your app in the butt. Too often, critics focus on niche issues and make unfair comparisons to other technologies or languages that do not have the same level of widespread use, applicability or history as Java. It’s like comparing a car to a carpet.Read more