David R. HeffelfingerSoftware Development Noteshttp://mail.ensode.net/roller/dheffelfinger/feed/entries/atom2022-05-31T09:53:37+00:00Apache Roller (incubating)http://mail.ensode.net/roller/dheffelfinger/entry/jakarta_ee_a_de_factoJakarta EE, A de facto standard in the makingDavid R. Heffelfinger2019-05-28T22:06:31+00:002019-05-28T22:06:31+00:00
<p><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" id="docs-internal-guid-32ec7eb0-7fff-79b8-0ee8-76e0ae352595"><span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">I’ve been involved in Java EE since the very beginning, Having written one of the first ever books on Java EE. My involvement in Java EE / Jakarta EE has been on an education / advocacy role. Having written books, articles, blog posts and given talks in conferences about the technology. I advocate Jakarta EE not because I’m paid to do so, but because I really believe it is a great technology. I’m a firm believer that the fact that Jakarta EE is a standard, with multiple competing implementations, results in very high quality implementations, since Jakarta EE avoids vendor lock-in and encourages competition, benefiting developers.</span></p><br /><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Oracle’s donation of Java EE to the Eclipse Foundation was well received and celebrated by the Java EE community. Many prominent community members had been advocating for a more open process for Java EE, which is exactly what Jakarta EE, under the stewardship from the Eclipse Foundation provides. </span></p><br /><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">There are some fundamental changes on how Jakarta EE is managed, that differ from Java EE, that benefit the Jakarta EE community greatly. </span></p><h1 dir="ltr" style="line-height: 1.38; margin-top: 20pt; margin-bottom: 6pt;"><span style="font-size: 20pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Fundamental differences between Java EE and Jakarta EE Management</span></h1><br /><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Some of the differences in the way Jakarta EE is managed as opposed to Java EE are that there is no single vendor controlling the technology, there is free access to the TCK and there is no reference implementation. </span></p><h2 dir="ltr" style="line-height: 1.38; margin-top: 18pt; margin-bottom: 6pt;"><span style="font-size: 16pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">No single company controls the standard</span></h2><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">First and foremost, we no longer have a single company as a steward of Jakarta EE. Instead, we have several companies who have a vested interest in the success of the technology working together to develop the standard. This has the benefit that the technology is not subject to the whims of any one vendor, and, if any of the vendors loses interest in Jakarta EE, others can easily pick up the slack. The fact that there is no single vendor behind the technology makes Jakarta EE very resilient, it is here to stay.</span></p><h2 dir="ltr" style="line-height: 1.38; margin-top: 18pt; margin-bottom: 6pt;"><span style="font-size: 16pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">TCK freely accessible</span></h2><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Something those of us involved heavily in Jakarta EE (and Java EE before), take for granted, but that may not be clear to others, is that Jakarta EE is a set of specifications with multiple implementations. Since the APIs are defined in a specification, they don’t change across Jakarta EE implementations, making Jakarta EE compliant code portable across implementations. For example, a Jakarta EE compliant application should run with minimal or no modifications on popular Jakarta EE implementations such as Apache Tomee, Payara, IBM’s OpenLiberty or Red Hat’s Thorntail</span></p><br /><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">One major change that Jakarta EE has against Java EE is the fact that the Technology Compatibility Kit (TCK) is open source and free. The TCK is a set of test to verify that a Jakarta EE implementation is 100% compliant with all Jakarta EE specifications. With Java EE, organizations wanting to create a Java EE implementation, had to pay large sums of money to gain access to the TCK, once their implementation passed all the tests, their implementation was certified as Java EE compatible. The fact that the TCK was not freely accessible became a barrier to innovation, as smaller organizations and open source developers not always had the funds to get access to the TCK. Now that the TCK is freely accessible, the floodgates will open, and we should see a lot more quality implementations of Jakarta EE.</span></p><h2 dir="ltr" style="line-height: 1.38; margin-top: 18pt; margin-bottom: 6pt;"><span style="font-size: 16pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">No reference implementation</span></h2><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Another major change between Java EE and Jakarta EE is that Java EE had the concept of a reference implementation. The idea behind having a Java EE reference implementation was to prove that suggested API specifications were actually feasible to implement. Having a reference implementation, however, had a side effect. If the reference implementation implemented something that wasn’t properly defined in the specification, then many developers expected all Java EE implementations to behave the same way, making the reference implementation a de-facto Java EE specification of sorts. Jakarta EE does away with the concept of a reference implementation, and will have multiple compatible implementations instead. The fact that there isn’t a reference implementation in Jakarta EE will result in more complete specifications, as differences in behavior between implementations will bring to light deficiencies in the specifications, these deficiencies can then be addressed by the community.</span></p><h1 dir="ltr" style="line-height: 1.38; margin-top: 20pt; margin-bottom: 6pt;"><span style="font-size: 20pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Conclusion</span></h1><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">With multiple organizations with a vested interest in Jakarta EE’s success, a lowered barrier of entry for new Jakarta EE implementations, and better specifications Jakarta EE will become the de-facto standard in server-side Java development.</span></p><br /></p>
http://mail.ensode.net/roller/dheffelfinger/entry/mitigating_risks_of_a_microservicesMitigating Risks of a Microservices ArchitectureDavid R. Heffelfinger2017-07-14T18:38:19+00:002017-07-14T18:54:31+00:00
<p><span id="docs-internal-guid-68d3068f-4261-8ca2-d592-d654b0bcc4fd"><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">In the “</span><a href="http://blog.payara.fish/demystifying-microservices-for-java-ee-developers-new-guide-now-available" style="text-decoration-line: none;"><span style="font-size: 11pt; font-family: Arial; color: rgb(17, 85, 204); background-color: transparent; text-decoration-line: underline; vertical-align: baseline; white-space: pre-wrap;">Demystifying Microservices for Java EE Developers</span></a><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">” guide I wrote for </span><a href="https://www.payara.fish/" style="text-decoration-line: none;"><span style="font-size: 11pt; font-family: Arial; color: rgb(17, 85, 204); background-color: transparent; text-decoration-line: underline; vertical-align: baseline; white-space: pre-wrap;">Payara</span></a><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">, I list several advantages and disadvantages of a microservices architecture. In the guide I list the disadvantages, but don’t really go into how to mitigate or even eliminate the risks. In this post I’ll go over these disadvantages and how to reduce the risks that they present.</span></p><h2 dir="ltr" style="line-height: 1.38; margin-top: 18pt; margin-bottom: 4pt;"><span style="font-size: 14pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Additional operational overhead</span></h2><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">When developing an application as a series of microservices, there will be some operational overhead since, instead of deploying one application into production, several small applications (i.e. your microservices) will need to be deployed. To decrease the costs of the operational overhead, a few approaches can be taken.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Deploy to the cloud</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">When deploying to the cloud, the cloud vendor can provide some of their resources to help with operation tasks for your application, freeing your team from having to perform these tasks. Additionally, most cloud vendors provide elasticity, meaning that your applications can be scaled up or down on demand, as their load increases or decreases, this helps with the scalability of your application as a whole.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Implement a DevOps approach</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Your development team assists with operational task such as deployment and monitoring</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Use an automated deployment tool</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">There are several tools in the market that can automate deployments, some free and open source, some commercial. Bamboo and Jenkins are two examples that are popular in the Java world. Puppet is another example, popular with languages typically used with Linux, such as Python or Ruby.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Use an Automated Performance Management (APM) Tool</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Monitoring performance becomes a lot harder if you deploy your application as a series of independent modules (microservices). An automated performance management tool can help with this. Some examples include AppDynamics, New Relic, Vector and Prometheus.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Use a log aggregation tool</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">When deploying an application as a series of microservices, instead of having a single log file to monitor, we typically have several, maybe hundreds of log files to monitor. Doing this by hand is not practical. To mitigate this risk a log aggregation tool such as Splunk, GrayLog or Loggly should be used.</span></p><h2 dir="ltr" style="line-height: 1.38; margin-top: 18pt; margin-bottom: 4pt;"><span style="font-size: 14pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Increased Debugging Complexity</span></h2><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">When debugging an application following a microservices architecture, it isn’t always obvious which of your microservices is causing the problem. Some user action (i.e. saving data on an HTML form) could trigger invocations to several microservices, making it harder to pinpoint the cause of the issue.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Additional Tooling</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Tools such as log aggregation tools and performance management tools may help.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Implement a policy of collective code ownership</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">“Collective code ownership” means that nobody owns code, ownership is shared across all teams and all developers in your organization. If a user reports a problem to your team, but it turns out that the problem is not with your code, but with another service that your code depends on, then if there is a policy of collective code ownership your team can fix the problem themselves, instead of waiting for the other team to get around to it.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Correlation Identifiers</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">When invoking your microservices, generate a correlation id, and pass it around as you invoke your microservices, then have your microservices log the correlation id as they are invoked. This will make it easier to trace microservices invocations when going through log files.</span></p><h2 dir="ltr" style="line-height: 1.38; margin-top: 18pt; margin-bottom: 4pt;"><span style="font-size: 14pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Distributed Transactions</span></h2><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Distributed transactions happen when we start a transaction, and while that transaction is in progress, an invocation to a microservice over the network takes place. Typically we want to avoid distributed transactions as there is a high probability they will timeout and rollback.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Implement your microservices as atomic units</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Commit all your transactions before making invocations across the network.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Use compensating transactions</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">If you commit a transaction that depends on a call to a microservices, and the call fails, then initiate a compensating transaction to revert the changes made by the original transaction.</span></p><h2 dir="ltr" style="line-height: 1.38; margin-top: 18pt; margin-bottom: 4pt;"><span style="font-size: 14pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Susceptibility to the fallacies of distributed computing</span></h2><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><a href="https://en.wikipedia.org/wiki/L_Peter_Deutsch" style="text-decoration-line: none;"><span style="font-size: 11pt; font-family: Arial; color: rgb(17, 85, 204); background-color: transparent; text-decoration-line: underline; vertical-align: baseline; white-space: pre-wrap;">L Peter Deutsch</span></a><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;"> came up with the </span><a href="https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing" style="text-decoration-line: none;"><span style="font-size: 11pt; font-family: Arial; color: rgb(17, 85, 204); background-color: transparent; text-decoration-line: underline; vertical-align: baseline; white-space: pre-wrap;">Fallacies of Distributed computing</span></a><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">, microservices being inherently distributed, are susceptible to these fallacies.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Implement the circuit breaker design pattern</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Modeled after an electrical circuit, the way the circuit breaker design pattern works is that your code attempts to make an invocation over the network, if the call fails, your code retries for a predetermined number of times, if the invocation does not succeed after repeated attempts, then the circuit breaker trips, and your code can handle the failure gracefully (how to do this depends on your specific application requirements).</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Use a load balancer</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">A load balancer such as nginx or F5 can distribute the load across several instances of your services. Most load balancers provide failover capabilities as well.</span></p><h3 dir="ltr" style="line-height: 1.38; margin-top: 14pt; margin-bottom: 4pt;"><span style="font-size: 12pt; font-family: Arial; color: rgb(102, 102, 102); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Deploy to the cloud</span></h3><p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">The elasticity feature of most cloud providers will help mitigate susceptibility to the fallacies of distributed computing.</span></p><div><span style="font-size: 11pt; font-family: Arial; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;"><br /></span></div></span></p>
http://mail.ensode.net/roller/dheffelfinger/entry/java_ee_9_may_doJava EE 9 may do away with application servers,should app server vendors be worried?David R. Heffelfinger2016-10-06T23:22:38+00:002017-07-16T19:53:29+00:00
<p><p>In my recent article, <a href="https://jaxenter.com/a-glimpse-at-java-ees-future-129340.html">A glimpse at Java EE’s future</a>, I stated that "Java EE 9 may do away with the concept of application servers completely". This generated some interest on Twitter.</p><h2>Background - Project Jigsaw and Java Modularity <br /></h2><p>Some background for those not in the loop, Java 9 will introduce <a href="http://openjdk.java.net/projects/jigsaw/">Project Jigsaw,</a> which will bring modularity to the Java platform. Java has been around for some 21 years or so, the JDK includes libraries that are not used a whole lot anymore, for example, libraries to support <a href="https://en.wikipedia.org/wiki/Common_Object_Request_Broker_Architecture">CORBA</a>, which was popular in the mid to late 90's but is seldom used anymore. However, the JDK team at Oracle is hesitant to remove these libraries because doing so would potentially break compatibility with existing applications that may be using them, therefore newer JDK's need to keep including these old libraries.</p><p>Project Jigsaw provides a solution to this problem, instead of including everything in the JDK, from Java 9 and beyond, the JDK will become modular. Applications will use only the modules that they use. Going back to our CORBA example, the few applications out there still using CORBA won't break, but all other applications not using CORBA won't have this unused library lying around. Project Jigsaw will work similarly to the way Maven handles dependencies today, however this functionality will be build right in the JDK.</p><p>Project Jigsaw won't be limited to eliminating "cruft" from modern versions of Java, in general, any dependencies an application may have could be declared as a module. Library authors may publish their libraries as modules, which will then be downloaded by any applications that require them at compile time when the application is built. </p><h2>Modular Java EE<br /></h2><p>I had the opportunity to attend a Birds of a Feather session titled <a href="https://oracle.rainfocus.com/scripts/catalog/oow16.jsp?event=javaone&search=BOF7984&search.event=javaone">"Enterprise Java for the Cloud"</a> during JavaOne 2016. During this session is when I heard that there is a possibility that Java EE 9 may do away with the concept of application servers, in favor of Java 9 modules. A very interesting concept and quite a change from the way we have been developing enterprise Java applications since J2EE was released back in 1999. Great news for application developers, but, should application server vendors be worried?</p><p>The answer is a resounding no. The way this would work is that vendors would provide their Java EE APIs as modules, then applications would include them as dependencies. Potentially, this could even benefit application server vendors, let me explain.</p><p>As most of you reading this blog probably know, Java EE is a series of specifications, with multiple implementations. For example, Hibernate, EclipseLink and OpenJPA are all implementations of the JPA specification. Similarly, Weld and OpenWebBeans are implementations of the CDI specification. Each application server ships with one implementation of each Java EE specification. As application developers, we are more or less stuck with the implementation that the application server vendor provides (there are ways around this, but they require jumping through hoops). If Java EE 9 adopts the modularity features of Java 9, then we as application developers may be able to pick and choose Java EE API implementations as we please, for example, we could use Hibernate as our JPA implementation, and OpenWebBeans as our CDI implementation (as far as I know, no application server currently provides this combination of CDI and JPA implementations). We as application developers benefit by picking our favorite implementations of each API, and vendors benefit by an increased pool of potential users for their Java EE API implementations.<br /></p><p><br /></p><p><br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/javaone_2016_day_3_fromJavaOne 2016, Day 3, from a Java EE PerspectiveDavid R. Heffelfinger2016-09-21T12:38:35+00:002016-09-21T12:38:35+00:00
<p><p>Yesterday was day 3 of JavaOne 2016. Oracle and the Java community is planning new features for the upcoming Java EE 8. I've been attending as many Java EE related sessions as I can, to see what the current plans are. All the speakers have made a point to state that nothing is carved in stone, all of this may change as it is still in planning stages.</p><p>I started the day attending "Cloud Native Java EE", a tutorial by <a href="http://www.payara.fish/">Payara</a> engineers Mike Croft (<a href="https://twitter.com/croft">@croft</a>) and Ondrej Mihályi (<a href="https://twitter.com/OMihalyi">@OMihalyi</a>). The talk was very good and explained how to deploy Java EE applications to the cloud using <a href="http://www.payara.fish/payara_micro">Payara Micro</a>.</p><p>I then headed over to Antoine Sabot-Durand's (<a href="https://twitter.com/antoine_sd">@antoine_sd</a>) session on CDI 2.0. Antoine is the CDI spec lead and obviously knows his stuff. He covered several new features coming to CDI 2.0 such as support for Java SE, asynchronous events, and the ability to add interceptors at runtime to CDI beans. That last one I thought was very impressive, I hadn't ever imagined that would even be possible.</p><p>Next I went to a JAX-RS 2.1 session by Ed Burns (<a href="https://twitter.com/edburns">@edburns</a>) and Pavel Bucek (<a href="https://twitter.com/pavel_bucek">@pavel_bucek</a>). The session covered several new JAX-RS features such as non-blocking I/O, server sent events and a reactive client API.</p><p>After that I attended "Portable Cloud Applications with Java EE" by Rajiv Mordani, Joe Dipol, Josh Dorr. This session covered how Java EE 9 will standardize the ability to deploy Java EE applications to different cloud providers.</p><p>The next session I attended was on Servlet 4.0, delivered by Ed Burns (<a href="https://twitter.com/edburns">@edburns</a>), discussing new features of this new version of the Servlet specification. This session started with a brief overview of network programming, Ed took some of us old timers in a trip down memory lane, mentioning things like <a href="https://en.wikipedia.org/wiki/Common_Gateway_Interface">CGI</a> and <a href="https://en.wikipedia.org/wiki/Gopher_(protocol)">Gopher</a>. Of particular interest in this session was Servlet 4.0 support for the HTTP/2 protocol. Ed was very good at explaining how this new version of HTTP addresses several limitations of the current HTTP 1.1 protocol supported by most browsers.</p><p>The last session I attended was "Security for Java EE 8 and the Cloud", by Kk Sriramadhesikan. The session covered security challenges posed by cloud environments and how the Java EE spec plans to address it. The new version of the Java EE Security API aims to make it easy for application developers to secure their cloud applications, leaving the details to security experts.</p><p>As evidenced by all of these great sessions, major changes are coming to Java EE in the not so distant future, looks like we will have some exciting times ahead. <br /></p><p><br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/javaone_2016_day_2_impressionsJavaOne 2016, Day 2 ImpressionsDavid R. Heffelfinger2016-09-20T05:12:10+00:002016-09-20T05:12:10+00:00
<p><p>This morning I attended Gaurav Gupta's JPA Modeler session, the tool is certainly very impressive and I wanted to learn more about it.</p><p>After Gaurav's session, I headed to the Franciscan C/D room to prepare for my own Hands-On Lab, "Java EE, Beyond the Basics". I had some materials (slides, manual, code samples, etc) to copy to the virtual machine's on the laptops and <a href="https://en.wikipedia.org/wiki/Murphy%27s_law">Murphy</a> reared his ugly head. The lab's virtual machines were not booting. I googled the error and learned that as a workaround I had to disable USB on the VMs. With the help of a couple of technicians, we disabled USB on each and every virtual. But I had the files I needed to copy on a thumb drive, how could I copy them with USB disabled? Luckily, I had the files online, therefore we were able to download them and copy them to each and every VM. By the way, all class materials can be downloaded <a href="http://www.ensode.net/files/javaee.zip">here</a>. Luckily we were able to finish on time, by the time the students showed up the VM's were ready to go.</p><p>The session went very well, I covered JSF and EJB, my co-speaker <a href="https://www.linkedin.com/in/rwlarsen">Bob Larsen</a> covered CDI. We were planning to cover JAX-RS as well, but unfortunately we ran out of time. I got some good feedback from the students both face to face and over Twitter, I think the session was well received.</p><p>After my session, I attended <a href="https://www.linkedin.com/in/lindademichiel">Linda DeMichiel's</a> session on Java EE 8 Update. Linda, for those that don't know her, is one of the specification leads for the Java EE platform. She covered current plans for Java EE 8, currently scheduled to ship sometime in 2017. A controversial proposal is to drop the MVC API from Java EE 7, as well as JMS 2.1 (JMS 2.0, the current version, would be delivered with Java EE instead).</p><p>I then attended "Enterprise Java for the Cloud" by Rajiv Mordani, Josh Dorr and Dhiraj Mutreja. This session was about what is planned for Java EE 9. Againn lots of speculation here, as everything is in early planning stages. One thing that I found interesting is the addition of a standard Java EE API for NoSQL databases, at this moment it is not clear if it will be a completely new API or an enhancement to JPA.</p><p> The next session I attended was on <a href="http://json-b.net/">JSON-B</a>, the new Java API for JSON Binding. This is a new API scheduled to be included with Java EE 7, this new API will populate Java objects from JSON strings, and vice-versa.</p><p>I then skipped the JCP party to attend the "Java EE for the Cloud" Birds of a feather (BOF) session. This BOF session was surprisingly well attended, it started at 7:00 pm, usually night sessions are not that well attended, they compete with parties and with tired, jet-lagged attendees, looks like many people, like myself, care deeply about the future of Java EE. There were very good questions in this session, for example, there is a new security API proposed for Java EE 7, one of the attendees asked about integrating applications using the existing security APIs with the new proposed Java EE 8 API. In this session the comment was made that, although speculation at this time, it is possible that Java EE 9 will do away with the concept of application servers, in favor of <a href="http://openjdk.java.net/projects/jigsaw/">Java 9 modules</a>.</p><p>There are lots of sessions on Java EE 8 and Java EE 9 during the conference, I will do my best to attend as many as I can, to try and pick the brains of the individuals working on the new specifications for these future Java EE versions.</p><p><br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/the_coolest_things_i_veThe Coolest things I"ve seen at JavaOne 2016 so farDavid R. Heffelfinger2016-09-19T12:26:02+00:002016-09-19T12:26:02+00:00
<p><p>Day one of JavaOne 2016 is in the books. Day 1 is typically JavaOne's NetBeans Day, and this year was no exception. Yesterday I had the opportunity to attend several sessions showcasing NetBeans capabilities, I saw features present in the current version of <a href="https://netbeans.org/downloads/">NetBeans</a>, some features are available in the upcoming <a href="https://netbeans.org/community/releases/82/">NetBeans 8.2</a>, others, Java 9 features specifically, will be available in a future version of NetBeans, but you can start experimenting with them today by downloading the <a href="http://wiki.netbeans.org/JDK9Support">NetBeans Java 9</a> build.</p><p>In no particular order, here are some of the coolest things I saw yesterday on day one of JavaOne 2016.</p><ol><li><b>Adding new refactoring capabilities to NetBeans on the fly.</b><br />Michael Nascimento Santos (<a href="https://twitter.com/mr__m">@mr__m</a>) demoed how to add refactoring capabilities to NetBeans on the fly with <a href="http://wiki.netbeans.org/Jackpot">Project Jackpot</a>. The specific example he showed was to add the capability for NetBeans to provide warnings when using <a href="http://www.joda.org/joda-time/">Joda-Time</a>, and suggest that the code use <a href="http://www.oracle.com/technetwork/articles/java/jf14-date-time-2125367.html">Java 8's Date/Time API</a> instead. Java 8, for those that don't know, introduced an improved Date / Time API which is much nicer than was what available with Java in earlier versions. Before Java 8, your best bet when working with dates was to use the Joda-Time library. You can see a video of Michael's demo <a href="https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=4&cad=rja&uact=8&ved=0ahUKEwjWh4HjspvPAhWHkh4KHY19AQoQtwIIMjAD&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYlE_SinDWb0&usg=AFQjCNGHzUCtfd7eO_ZGdHVRT3PE2lYBjw&sig2=x4NgpyRu9J-296QDnolw7w&bvm=bv.133178914,d.dmo">here</a>. <br /></li><li><b>Create complete Java EE applications with JPA Modeler.</b><br />Gaurav Gupta (<a href="https://twitter.com/jGauravGupta">@jGauravGupta</a>) demonstrated a very cool NetBeans plugin called <a href="http://jpamodeler.github.io/">JPA Modeler</a>. JPA Modeler can generate database tables, JPA artifacts (entities, DAO's etc), and even complete Java EE applications just from a database model. The tool works like those graphical applications that DBA's use to create the database (i.e things like ERWin), but goes beyond the capabilities of these tools by generating a scaffold of your Java EE application. Gaurav is JPA Modelers project lead.</li><li><b>NetBeans JShell Integration</b><br /><a href="https://blogs.oracle.com/java/jshell-and-repl-in-java-9">JShell</a> is a new upcoming feature of Java 9, it allows to write "low ceremony Java", which means, to develop a "Hello World" program, you would just have to type <font face="courier new,courier,monospace">System.out.println("Hello, World")</font>, instead of having to declare a class, create a main() method, etc. The NetBeans Java 9 build includes built-in support for JShell, you can open a JShell window from NetBeans, experiment with your Java code, then automatically create a Java class with your JShell code snippets. Geertjan Wielenga (<a href="https://twitter.com/GeertjanW">@GeertjanW</a>) demoed all this, it was jaw droppingly cool. You can read a blog post explaining NetBeans JShell integration in <a href="https://blogs.oracle.com/geertjan/entry/learning_java_with_jshell_in">Geertjan's blog</a>.<br /></li></ol></p>
http://mail.ensode.net/roller/dheffelfinger/entry/javaone_2015_java_ee_handsJavaOne 2015 Java EE Hands-on LabDavid R. Heffelfinger2015-10-27T03:10:16+00:002015-10-27T18:08:13+00:00
<p><p>Earlier today I delivered my JavaOne Java EE Hands-On Lab session with <a href="https://twitter.com/reza_rahman">Reza Rahman</a> and <a href="https://www.linkedin.com/in/rwlarsen">Bob Larsen</a>. The session was completely packed and well received. We covered topics such as JavaServer Faces (JSF), Contexts and Dependency Injection (CDI), the Java Persistence API, and Enterprise JavaBeans (EJB). </p>
<p></p><p>I delivered the same talk last year, it was so popular that this year we're scheduled to deliver it twice, both sessions are completely packed. I'll be delivering the same talk tomorrow morning at 8:30 am in the Hilton Franciscan B/C/D room.<br /></p><p>The session is actually based on a week-long class I taught for one of my clients. The JavaOne version is compressed to fit in a 2 hour session. I'll be happy to teach the full course for anyone that would like to get more in-depth training, contact me at dheffelfinger at ensode dot com for details, my <a href="https://www.packtpub.com/application-development/java-ee-7-glassfish-4-application-server">Java EE with GlassFish</a> and <a href="https://www.packtpub.com/application-development/java-ee-7-development-netbeans-8">Java EE with NetBeans</a> books also contain additional material.</p><p> Some of the students requested a copy of the materials, and I'm happy to oblige. <a href="http://ensode.net/roller/dheffelfinger/resource/JavaOne2015JavaEE_HOL.zip">Click here</a> to download a zip file containing all the materials, including the slides, exercise manual, source code for the demo and exercise solutions.<br /></p><p> </p><p><br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/scrollbars_in_linux_mint_cinnamonScrollbars in Linux Mint CinnamonDavid R. Heffelfinger2015-07-12T10:54:02+00:002015-07-12T10:54:02+00:00
<p><p>I like <a href="http://www.linuxmint.com/">Linux Mint</a>, and I have been using it as my primary Linux distribution for a couple of years now, but one thing that bugged me was the lack of scrollbars for some applications.</p><p>I had Googled around, and found some solutions, unfortunately while the solutions worked for most applications, some of my most frequently used applications like the terminal, Nemo (the file manager), and gedit were still lacking scrollbars.</p><p>I finally found a solution, first, I had to install the scrollbar-overlay package:</p><pre>sudo apt-get install overlay-scrollbar</pre><p> Then, from a terminal window, run the following command:</p><pre class="contents ">gsettings set com.canonical.desktop.interface scrollbar-mode normal<br /></pre><p> I finally have a scrollbar in all of my applications. That really was harder to figure out than it should have been.<br /></p><p><br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/javaone_2014_trip_reportJavaOne 2014 Trip ReportDavid R. Heffelfinger2014-10-04T14:29:58+00:002014-10-05T00:13:01+00:00
<p><p><br/>
I just came back from my annual trip to JavaOne. As usual, the conference was great. This year I had two talks, I participated in a panel at NetBeans day on Sunday right after the Technical Keynote. The title of the session was "Get Productive with Free Java Tools". I had the pleasure of presenting with Tony Epple (@monacotony), who was moderating the panel and gave a quick demo on <a href="http://dukescript.com/">DukeScript</a>, Sven Reimers (@SvenNB), who showed how to integrate the NetBeans IDE with JavaFX's SceneBuilder, Michelle Chamberlin, who explained the cool things she is doing at Boeing with the NetBeans platform, and Bernd Ruehlicke, who presented how the NetBeans platform is being used in the oil industry.<br /><br />My other session was a Java EE Hands-On Lab I co-presented with Mark Heckler (@MkHeck). Many thanks to Josh Juneau (@javajuneau), Sven Reimers (@SvenNB) and Bob Larsen, who helped us proctor the lab. The session was packed to the brim, there was a waiting list and many couldn't make it inside. </p><p><img border="0" hspace="0" align="bottom" vspace="0" src="https://lh5.googleusercontent.com/-QX9Gi9nzGRY/VC_wW3FABNI/AAAAAAAABDw/9ohJQHd2_yo/w506-h900/20141001_094831.jpg" /><br /><br />Feedback for the Hands-On Lab was great, attendees were stopping me in the hallway to tell me how much they enjoyed it, made my day. If you were one of those who couldn't make it in, or if you couldn't make it to the conference, all the materials for the lab can be found at <a href="http://ensode.net/downloads/JavaEE_Hands_On_Lab.zip">http://ensode.net/downloads/JavaEE_Hands_On_Lab.zip</a>.<br /><br />In addition to my own sessions, I attended several sessions by some of the other great speakers. Sunday morning I attended the GlassFish community panel, with John Clingan (@jclingan), Cameron Purdy (@cpurdy) and Anil Gaur (@annilgaur), moderated by Reza Rahman (@reza_rahman), in this session, the panelists reiterated Oracle's commitment to GlassFish. </p><p> </p><p><img border="0" hspace="0" align="bottom" vspace="0" src="https://lh4.googleusercontent.com/-2mfF__X6AGk/VChGk8uEmgI/AAAAAAAAAyg/wIsHIhRci_s/w946-h532-no/20140928_103402.jpg" /> </p><p>During the GlassFish Adoption session Mohamed Taman (@_tamanm) talked about a large scale deployment in Egypt, in which he used GlassFish on a UN project. His company won the contract, and by the time they started to work on it most of the work was already in place, readily impressing his client. Mohammed also briefly talked about this project during the community keynote. Martin Mares (@MartinJMares) also talked during this session, showing some cool things he is doing with the GlassFish command line administration tool, asadmin.</p><p><br />I then attended the technical keynote, which included speakers from IBM and Oracle. The keynote was running behind schedule, I had to leave early since I had a session right after, as I'm sure you've heard by now, Brian Goetz (@BrianGoetz) was kicked out of the stage towards the end. I missed when it happened live, but I plan to watch <a href="https://www.oracle.com/javaone/live/on-demand/index.html#javaone">the recording</a>.<br /><br />Later on Sunday I attended a session on using NetBeans for teaching, with Ken Fogel (@omniprof), Johannes Weigend (@JohannesWeigend), Paul Anderson (@Paul_ASGTeach), Gail Anderson (@gail_asgteach), Zoran Severac (@neuroph) and Andreas Stefik (@AndreasStefik). In addition to my daytime job as a Java EE software developer, I sometimes teach short courses on Java EE using NetBeans, I picked some good tips from this session that I'm sure to use in future courses.</p><p>John Ament (@JohnAment) gave a talk on Monday morning about building RESTful web services outside an application server.<br /><br />On Monday, there were many sessions about the future of Java EE, <a href="https://www.java.net/jcp/communityspotlight/linda-demichiel">Linda DeMichiel</a> had a very interesting presentation about the future of the platform as a whole. Pavel Bucek (@pavel_bucek) had a session about the future of the Java API for WebSocket. Martin Grebac (@mgrebac) had a session on the JSONB specification that is slated to be included in Java EE 8. </p><p>Geertjan Wielenga (@GeertjanW) and JB Brock (@peppertech) had a great <br/>
session on Monday about Coding for Desktop and Mobile with HTML5 and Java EE 7. In <br/>
this session they showed the NetBeans / Chrome integration, in which <br/>
changes to the markup in NetBeans result in an instant refresh on the <br/>
browser, greatly speeding up web application development, very <br/>
impressive. <br /></p><p>On Monday night I attended a couple of GlassFish Birds-of-a-Feather <br/>
(BOF) sessions. The first GlassFish BOF was the GlassFish Community BOF <br/>
and was led by John Clingan (@jclingan), I had the pleasure of meeting <br/>
Manfred Riem @mriem, JSF and MVC co-spec lead during this BOF. The <br/>
second GlassFish BOF was about contributing to GlassFish, it was led by <br/>
Reza Rahman (@reza_rahman), GlassFish and Java EE evengelist at Oracle, <br/>
and Steve Millidge. Steve is the CEO <br/>
of C2B2 consulting, a consulting firm in the UK, and is <br/>
also the man behind Payara, a new supported distribution of GlassFish, <br/>
if you are using GlassFish for your Java EE project, you should check Payara out.<br /><br />I also attended a JSF BOF on Monday night, in which <br/>
Kito Mann (@kito99) and another JSF expert group member explained their <br/>
ideas for future features in JSF.</p><p>On Tuesday, Arun Gupta (@arungupta) had an interesting talk about <br/>
lessons learned in real-life Java EE 7 projects. In this session he <br/>
described several Java EE 7 already in production, including Mohamed <br/>
Taman's project that was featured in the technical keynote on Sunday.</p><p><img border="0" hspace="0" align="bottom" vspace="0" src="https://lh5.googleusercontent.com/-q0k6lGsiQ_s/VCsKrhvWhZI/AAAAAAAAA2E/6jIQC-sLdZk/w299-h532-no/20140930_125518.jpg" /></p><p>Also on Tuesday, David Delabassee (@delabassee) had a very interesting talk about <br/>
implementing home automation with JavaEE. He was actually controlling <br/>
the lights in his home office in Belgium live from the session, which <br/>
was being held in San Francisco, very cool stuff.<br /><br /><img border="0" hspace="0" align="bottom" vspace="0" src="https://lh6.googleusercontent.com/-r6eUaaYbl2g/VCtPiZ3gWSI/AAAAAAAAA2s/vOtBKbildaY/w299-h532-no/20140930_174906.jpg" /><br /><br />Tuesday night there was a BOF on meeting with the Java EE specification leads with Bill Shannon, Linda DeMichiel, Ed Burns (@edburns), Manfried Riem (@mriem), Pavel Bucek (@pavel_bucek), and all other Java EE specification leads. It is always an honor to be in the same room with those to work so hard to bring us the latest Java EE specs.</p><p><img border="0" hspace="0" align="bottom" vspace="0" src="https://lh4.googleusercontent.com/-dIAIoHS9VA0/VCtvx_KrhaI/AAAAAAAAA28/Bdlkozekldc/w946-h532-no/20140930_200643.jpg" /><br /><br /><br />Josh Juneau (@javajuneau) had a session Wednesday afternoon about Concurrency Utilities for Java EE, a new API that was introduced in Java EE 7.</p><p><img border="0" hspace="0" align="bottom" vspace="0" src="https://lh3.googleusercontent.com/-Gp83ldB8DGE/VCyOh1pPICI/AAAAAAAAA7Y/sLOyw0CiWj0/w946-h532-no/20141001_163003.jpg" /><br /><br />On Thursday morning I attended the community keynote, it started with <span class="_dwd st s std">Michael Greene</span> from Intel, we saw some of the stuff that Intel is doing with Java on the server side, also, there was an announcement about Intel joining the OpenJDK project. During the community keynote, there was a lot of very interesting coverage about Java powered robots, including automated cars from Perrone Robotics, a company based in Charlottesville, Virginia, not too far from my neck of the woods. There were several community members on stage at one point or another. The community keynote wrapped up with no other than James Gosling, the father of the Java language, talking about how Java has come full circle, it started as an "Internet of Things" language, and is currently used more and more in that realm.<br /><br />An annual tradition during JavaOne keynotes is that at one point or another, they start throwing t-shirts at the audience. This year there was a twist, they were using a rubber catapult contraption to be able to throw t-shirts to members of the audience that are sitting farther back (side note, Sven Reimers, which was sitting two seats away from me, got hit in the face with one of these t-shirts thrown using the contraption, Sven, if you are reading this, I hope you are ok, but that was very funny). Every year I try very hard to catch one of these t-shirts, to no avail, this year, I finally was able to catch one.</p><p><img border="0" hspace="0" align="bottom" vspace="0" src="https://lh5.googleusercontent.com/-9RcwCaiuXmM/VC2Xx9bRHoI/AAAAAAAABCE/uRRokcoWOT4/w299-h532-no/20141002_112106.jpg" /><br /></p><p>On Thursday right after the community keynote there was a very <br/>
interesting Java EE 8 community panel, with representatives from all <br/>
major Java EE application servers, including [dude's name] from IBM, <br/>
Mark Little [twitter] from Red Hat, David Blevins (@dblevins) from Tomee<br/>
[spelling], Cameron Purdy representing GlassFish, John Clingan <br/>
(@jclingan) representing the Avatar project. And Adam Bien representing <br/>
himself as a member of the Java EE community.</p><p>Bruno Borges (@brunoborges) had an interesting session Thursday afternoon on implementing JavaFX clients for Java EE server side code.<br /><br />Also on Thursday, Adam Bien (@abien) had a cool session about using Nashorn, the JavaScript implementation included in the Java Development Kit (JDK) 8, in Java EE applications. Adam is a great speaker, make sure you check his AirHacks online seminars.<br /><br /><br />I tend to focus on Java EE sessions when I go to JavaOne, but this year I went to a couple of sessions covering other very cool stuff. Tony Epple (@monacotony) and Jaroslav Tulach (@JaroslavTulach) had a very funny and informative session about DukeScript, DukeScript applications are plain Java applications that internally use HTML5 technologies and JavaScript for rendering.<br /><br />Baruch Sadogursky and Yoav Landman , another great comedic duo, had a great session on Groovy puzzlers.<br /><br />Venkat Subramaniam (@venkat_s) delivered a fast paced, humorous and interesting talk on Groovy closures, this was late in the day on Thursday, a great way to end the conference.<br /><br />A major part of the conference is the vendor's booths. This year I dropped by the Tomitribe booth, Tomitribe provides support for the Apache TomEE application server. I also visited the CodeName One booth, these guys make a product that allows you to develop applications in Java for both Android and Mac OS. I also dropped by the IDR solutions booth, this company makes a product that converts PDF documents to HTML5, and the Payara booth, who provides technical support for GlassFish.<br /><br />Wednesday afternoon I had a book signing at the JavaOne bookstore, my first time signing books at JavaOne, great experience.<br /><br />In addition to sessions, booths and book signings, JavaOne always has plenty of social activities. This year I attended the NetBeans party on Saturday night, the Java EE community appreciation event on Sunday night, and the JCP party on Monday night. I also attended the Oracle appreciation event, this year they had none other than Aerosmith playing at the event. </p><p><img border="0" hspace="0" align="bottom" vspace="0" src="https://lh4.googleusercontent.com/-EOyB2VT4W5I/VCjfSjKHrcI/AAAAAAAAAyE/SC0iQs1FUHs/w946-h532-no/20140928_212533.jpg" /><br /><br />As always, JavaOne was awesome, great sessions, great social activities and above all the opportunity to rub shoulders with the greatest minds in the Java community. Every year I meet new great people from all over the world, and even though I don't see them often, when I run to them at the conference it is always as if I'm meeting with old friends.<br /><br />Next year marks the 20th anniversary of the Java language, I'm sure JavaOne 2015 will be out of this world, I can't wait.<br/>
</p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/5_perks_you_can_offer5 Perks You can offer to attract good Software DevelopersDavid R. Heffelfinger2014-06-06T14:28:12+00:002014-06-06T14:29:38+00:00
<p><p>Software developers are in high demand nowadays. We get contacted on a daily basis by companies requesting we go work for them. We frequently get emails with the words "Great Opportunity!" and "Urgent Requirement". The thing is, not many of the projects we get contacted for offer compelling reasons for us to make the change. I decided to make a list of things that would make us as software developers consider the possibility of moving on to another project.</p><p><b>1. Working on a brand new project</b> </p><p>Most of the projects out there are maintenance of an existing application, brand new projects built from the ground up are few and far in between. If you have a brand new project, then you have a leg up over all the other companies looking to hire software development talent.</p><p><b>2. Quiet working spaces</b> </p><p>Software development requires concentration, this concentration is hard to obtain in the modern cubicle farm, with all the interruptions around (conversations, phones ringing etc). Offer your developers quiet working spaces and you have a perk that most employers around can't offer. Ideally, give each developer their own private office, now you really have a perk that puts you head and shoulders above the competition. If you can offer private offices, at least offer cubicles with doors, which provide a bit more privacy than the usual open cubicles.<br /></p><p><b>3. The ability to work remotely</b></p><p>Nowadays high speed internet is so common, that there really is no reason for most people to actually drive to an office. A lot of companies want to see "butts in chairs", this is really not necessary, you should know if the work is getting done, your development team does not have to physically be at your location. This is one very rare perk, offering this will certainly make your company an attractive place to work for software developers. This also has the side effect of increasing the available talent pool, since members of the development team does not have to live in the same geographical area as your company.<br /></p><p><b>4. Allow the development team to use their own equipment</b></p><p>To this day, many companies are shy about allowing non-company laptops into their network. The development team has to use company approved hardware. Many software developers would prefer to work using their own laptops, it shouldn't be a big deal to allow them to do so. As a bonus, when working with a programming language that is platform independent, such as Java, it doesn't matter if the developer is using a Mac, Windows or Linux, therefore developers can work with their preferred platform, as opposed to being tied to whatever the company standard is.</p><p><b>5. Keep meetings to a minimum</b></p><p>In my experience, in most cases, most people attending a meeting have no real business being there. They could be doing productive work instead. Meetings interrupt the workflow of software developers and in most cases are a massive waste of time. I'd recommend not more than a 1 hour meeting a week. If you need daily status reports, an email works better than a daily meeting, that way the developers can do it at their leisure, not at a set time, and they don't have to sit through and listen to the status of all the other team members, which more than likely has no impact whatsoever in whatever they may be working on.<br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/things_i_would_tell_recruitersThings I would tell recruiters if I wasn't afraid to sound arrogantDavid R. Heffelfinger2014-06-03T17:52:35+00:002015-12-05T12:53:50+00:00
<p><p><br/>
I am fortunate enough to work in a field for which there is a lot of demand out there. I get multiple emails every day from companies asking for help with their server side Java projects. Java developers such as myself<br /><br /><b>1. Don't call your position "an opportunity"</b><br />Like I mentined in the intro, I get tons of "opportunities" every day via email or LinkedIn messages. Java projects are a dime a dozen, chances are your project is not a "great opportunity" for me. You know and I know that Java developers are hard to find, if anything, me agreeing to work on your project is an opportunity for you, and not for me.<br /><b></b></p><p><b>2. Don't say you have an "urgent requirement"</b><br />You may urgently need a Java developer, and I'm here drowning in emails from recruiters that also need Java developers. It may be urgent for you to fill that position, but it is not urgent for me to accept it. While we are on the topic, don't say the requirement is urgent if you are not willing to be flexible. One perk that would certainly catch my attention would be the ability to work remotely, but very few customers are open to the possiblity. If your requirement is so urgent, shouldn't you be a bit more flexible? Oh, and by the way, no, I am not willing to relocate just so that I can work on a 6 month project.<br /><b></b></p><p><b>3. I don't stay on the market too long.</b><br />I work as a consultant on a C2C basis, therefore I switch projects every few months. Every time I post my resume on one of the job boards, I get bombarded with calls and emails from recruiters (even more so than when I'm not actively looking).<br />If you are interested in my services, you have to move fast, chances are that in a week or less I won't be in the market anymore.<br /><b></b></p><p><b>4. Don't make me jump through hoops</b><br />I've written several books on Java, taught Java classes and been a speaker at Java conferences, as well as having about 18 years of experience. I think my experience speaks for itself. Please don't make me go through several rounds of interviews or take a silly test just so that I can work on your project. Just by talking to one of your developers he or she will be able to tell that I know what I'm talking about.<br /><b></b></p><p><b>5. If I accept/am about to accept another project, don't ask me to "wait a few days"</b><br />As much as I get contacted by recruiters for several different positions, it is mentally exhausting and draining to talk to several potential clients, send resumes, etc. I just want to get it over with, so as soon as I get an offer, I'm taking it. <br /><br/>
</p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/java_ee_course_trip_reportJava EE Course Trip ReportDavid R. Heffelfinger2014-06-03T17:01:05+00:002014-06-03T17:01:06+00:00
<p>I just came back from teaching a Java EE class in San Francisco.<br /><br />The course lasted two days, and it covered the most commonly used Java EE technologies and API's such as JavaServer Faces (JSF), Contexts and Dependency Injection (CDI), Enterprise JavaBeans (EJB), the Java Persistence API and the Java Message Service(JMS). The course also touched on Bean Validation and the Java API for RESTful Web Services (JAX-RS).<br /><br />The students were veteran Java developers and architects, ranging from around 5 to 18 years of experience. There were a few students that had use EJB's back in the J2EE era, some that had used earlier versions of JSF (1.x) and some that had been focusing on Spring for their server side Java development.<br /><br />None of the students had use modern versions of EJB or JSF, they were very impressed on how much easier modern versions of these frameworks are compared to their Java EE counterparts.<br /><br />Since we had only two days, we only covered the basics of each technology, such as Facelets markup for JSF. For CDI, we covered context (scope) annotations and dependency injection for CDI. We mentioned additional CDI features such as qualifiers, stereotypes and interceptor binding types.<br /><br />The different Bean Validation annotations were covered, pointing out how simple it is to do validation using just a few simple annotations. As far as EJB's go, I covered the different type of session beans, such as Stateless, Stateful, and Singleton session beans; as well as Message driven beans. For EJB's we went a bit deeper, covering things such as transaction management, interceptors for Aspect Oriented Programming (AOP) and the EJB timer service.<br /><br />When talking about JPA, the class covered basic JPA annotations such as @Table and @Column, as well as one-to-many, many-to-one, many-to-many and one-to-one entity relationships. We also covered eager vs lazy fetching, and the advantages and disadvantages of each approach. We ended the JPA topic with a discussion of the Java Persistence Query Language (JPQL) and the JPA Criteria API.<br /><br />I overheard some comments from the students, for example, one mentioned "EJB's are cool", which I completely agree. Another student noted that there isn't anything in Java EE that he cannot accomplish with Spring, which, while it may be true that the end result is the same, fails to take into account that the amount of work to get this end result tends to be a lot less with Java EE.<br /><br />There were hands-on labs for the students to practice the concepts taught in class. I chose NetBeans as the IDE for the exercises, since it comes bundled out of the box with everything needed to build complete applications, such as a Java EE compliant application server (GlassFish), and a fully functional RDBMS (JavaDB). Not many of the students had previous NetBeans experience, however most of them were able to finish the exercises (which were simple, but complete Java EE applications) in about 30 minutes or so.<br /><br />While discussing the hands-on labs, I provided some NetBeans tips, such as the ability to generate boilerplate code (Alt-Ins), generate JPA entities from an existing database, and the NetBeans JPQL editor, which provides code completion when developing JPQL queries.<br /><br />All in all, a great experience. I don't get to teach as often as I'd like, it is a nice change of pace from my day to day job developing real-life Java EE applications.</p>
http://mail.ensode.net/roller/dheffelfinger/entry/javaserver_faces_jsf_in_aJavaServer Faces (JSF) in a HurryDavid R. Heffelfinger2014-04-04T00:21:28+00:002014-04-06T01:10:46+00:00
<p><p>Need to learn JSF in a hurry? I'm here to help! </p><p>Assuming you already have some Java experience, as well as some HTML experience, there is nothing to JSF, you can learn the basics in a few minutes. I also assume that you are familiar with packaging and deploying Java code to an application server such as GlassFish, WildFly, JBoss, Weblogic or Websphere, or to a servlet container such as Tomcat or Jetty.</p><p><br />JSF has evolved over the years, this blog post covers the best practices in JSF 2.0 or newer, specifically, Facelets is used to develop the front end (as opposed to JSP) and CDI Named beans are used to develop the server side code (as opposed to managed beans).</p><p><br /></p><h4>Step 1: Develop Java class(es) that will hold information (the Model in the MVC pattern)</h4><p>Your Java class will be a Plain Old Java Object (POJO), it will consist of private properties public setters and getters.<br /></p><p>package com.ensode.jsfinahurry.model;<br />import javax.enterprise.context.RequestScoped;<br />import javax.inject.Named;<br /><br />@Named<br />@RequestScoped<br />public class Person {<br /><br /> private String firstName;<br /> private String lastName;<br /> private Short age;<br /><br /> public String getFirstName() {<br /> return firstName;<br /> }<br /><br /> public void setFirstName(String firstName) {<br /> this.firstName = firstName;<br /> }<br /><br /> public String getLastName() {<br /> return lastName;<br /> }<br /><br /> public void setLastName(String lastName) {<br /> this.lastName = lastName;<br /> }<br /><br /> public Short getAge() {<br /> return age;<br /> }<br /><br /> public void setAge(Short age) {<br /> this.age = age;<br /> }<br /><br />}<br /></p><p>The @Named annotation designates the class as a CDI managed bean, gives it a name, which by default is the class name with its first character switched to lowercase (“person”, in our case). This annotation allows JSF pages to access our Java class.<br /></p><p>The @RequestScoped annotation gives our CDI bean a scope of request. If you have developed web applications in Java before you should be familiar with bean scopes by now.</p><p>The following table shows the most commonly used scopes for CDI named beans:</p><p><table border="1" cellspacing="1" cellpadding="1" style="width: 100%;"><tbody><tr><td style="width: 50%;"><b> Annotation</b></td><td style="width: 50%;"> <b>Scope</b></td></tr><tr><td style="width: 50%;"> @RequestScoped</td><td style="width: 50%;"> Request</td></tr><tr><td style="width: 50%;"> @SessionScoped</td><td style="width: 50%;"> Session</td></tr><tr><td style="width: 50%;"> @ApplicationScoped</td><td style="width: 50%;"> Application</td></tr><tr><td style="width: 50%;"> @ConversationScoped</td><td style="width: 50%;"> Conversation</td></tr><tr><td style="width: 50%;"> @FlowScoped</td><td style="width: 50%;"> Flow</td></tr><tr><td style="width: 50%;"> @Dependent</td><td style="width: 50%;"> Dependent pseudo scope<br /></td></tr></tbody></table><br />The first three should be self-explanatory, the last two (@ConversationScoped and @FlowScoped) are both meant for the bean to live throughout two or more requests, but not last through the whole session. Since we're in a hurry, I can't explain these in detail, but suffice to say that @FlowScoped was introduced in JSF 2.2 as part of Java EE 7 and is the preferred way to achieve this functionality if you are using JSF 2.2 or newer. @Dependent just means that the bean will be created as needed.<br /></p><h4>Step 2: Develop a controller class</h4><p>This is the controller in the Model-View-Controller (MVC) design pattern. As far as plumbing, there is not much to do for controllers, just use the @Named annotation and an appropriate annotation.<br />package com.ensode.jsfinahurry.controller;<br /><br />import javax.enterprise.context.RequestScoped;<br />import javax.inject.Named;<br /><br />@Named<br />@RequestScoped<br />public class PersonController {<br /> public String processData(){<br /> <br /> //in a real application, we would process user-input here<br /> //more than likely saving data to a database<br /> <br /> return "confirmation";<br /> }<br />}<br /></p><p>Our JSF pages will invoke the processData() method when the user clicks on a button, via a method binding expression (next section). By convention, the next page to render in the browser will match the return value of the invoked method (processData(), in our case). For our example, we will develop a page named confirmation.xhtml (matching the return value of “confirmation”) that will be rendered after our processData() method is invoked.<br />Step 3: Develop the pages<br />Now that we have our Java code in place, we need to develop the user interface. JSF pages are developed using Facelets, a JSF specific view technology. Facelets pages are nothing but standard XHTML pages using some JSF specific name pages.<br />A page used to allow the user to enter person data (to be stored in our Person class) may look like this:<br /></p><p><?xml version='1.0' encoding='UTF-8' ?><br /><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br /> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br /><html xmlns="http://www.w3.org/1999/xhtml"<br /> xmlns:h="http://xmlns.jcp.org/jsf/html"><br /> <h:head><br /> <title>Enter Person Data</title><br /> </h:head><br /> <h:body><br /> <h3>Enter Person Data</h3><br /> <h:form id=”personForm”><br /> <h:panelGrid columns="2"><br /> <h:outputLabel for="firstName" value="First Name"/><br /> <h:inputText id="firstName" label="First Name" value="#{person.firstName}"/><br /> <h:outputLabel for="lastName" value="Last Name"/><br /> <h:inputText id="lastName" label="Last Name" value="#{person.lastName}"/><br /> <h:outputLabel for="age" value="Age"/><br /> <h:inputText id="age" label="Age" value="#{person.age}"/><br /> <h:panelGroup/><br /> <h:commandButton value="Submit" action="#{personController.processData()}"/><br /> </h:panelGrid><br /> </h:form><br /> </h:body><br /></html><br /></p><p>If you know even basic HTML, you should have a pretty good idea of how the above Facelets markup works. Before explaining the markup, notice that most JSF specific tags on the page have an id attribute. This attribute is optional, but it is a good idea to set it, for starters, it allows us to link labels to input fields (explained below), but also, when things don't work as expected it is much easier to identify which tag is causing trouble, as most JSF error messages will display the id of the component (if we don't set it, JSF will assign one, that will be meaningless to us).<br /></p><p>The <h:head> and <h:body> tags are drop-in replacements for HTML <head> and <body> tags.<br /><h:form> is equivalent to the HTML <form> tag, notice that for JSF we don't need to specify the method and action attributes (method will always be “post” and the action will always point to the JSF servlet, which is automatically used when developing with JSF).</p><p><br />The <h:panelGrid> component lays out JSF tags on the page, similar to using a table to lay out HTML tags. Its column attribute specifies how many tags will be placed in each column.<br /><h:outputLabel> renders an HTML <label> tag, its “for” attribute must match the id attribute of the input component the label is meant for.</p><p><h:inputText> is equivalent to an HTML <input> tag with a type of “text”. A nice thing about JSF is that it automatically converts user-entered values to the appropriate type in the corresponding CDI named bean. The value of the value attribute is what is known as a value binding expression, we can recognize these since they are encapsulated in curly braces and preceded by a hash (i.e. #{..}). Value binding expressions are used to automatically populate the corresponding attribute in a CDI named bean with the user-entered value for the corresponding input text. Remember the @Named annotation? “person” inside each value attribute corresponds to the name of our Person bean. The value after the dot corresponds to the corresponding property in the Person bean. For example, #{person.firstName} corresponds to the firstName property of the Person bean.<br /></p><p><h:panelGroup> is used to group JSF tags together in a single cell. In our case, all we wanted to do was have an empty cell so that our button would vertically align with the rest of the input fields, so we placed an empty <h:panelGroup> tag at the appropriate location in our <h:panelGrid>.</p><p><br />Finally, <h:commandButton> submits our form, its value attribute sets the label for the button, its action attribute indicates which CDI named bean method to execute when the button is clicked (processData(), in our case). This is what is called a method binding expression. The method must be public, return a String and take no arguments. What we implemented here is what is referred to as dynamic navigation, although our simple example always returns the same String, there is nothing stopping us from returning different values depending on some conditions, we can then take the user to different pages depending on these conditions (picture a switch statement or if/then/else, with different return values for different conditions).<br />If we don't need to do any processing after the user clicks the button and we always will display the same page, we can use static navigation, in which case the value of the action attribute can be hardcoded, like this:</p><p><br /><h:commandButton value=”Submit” action=”somepage”/><br /></p><p>We know that the value is hardcoded and not an expression since it is not surrounded by curly braces preceded by a pound sign (“#{...}”). In this case a page named somepage.xhtml would be rendered on the browser every time the user clicks on the button.<br />The markup for our confirmation page simply displays the values the user entered on the previous page.<br /></p><p><?xml version='1.0' encoding='UTF-8' ?><br /><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br /> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br /><html xmlns="http://www.w3.org/1999/xhtml"<br /> xmlns:h="http://xmlns.jcp.org/jsf/html"><br /> <h:head><br /> <title>Confirmation Page</title><br /> </h:head><br /> <h:body><br /> <h3>You entered the following data</h3><br /> <b>First Name:</b> ${person.firstName}<br/><br /> <b>Last Name:</b>${person.lastName}<br/><br /> <b>Age:</b>${person.age}<br /> </h:body><br /></html></p><p><br />The only thing new on this page is the use of curly braces preceded by a dollar sign (“${...}”) to retrieve a named bean's properties. When the page is displayed the value of the corresponding property is displayed on the page.<br /></p><h4>Our application in action</h4><p>Once we package our application in a WAR file and deploy it to our application server of choice (I'm using GlassFish), our input page will be rendered. Here is what it would look like after a user entered some data:<br /><img vspace="0" hspace="0" border="0" align="bottom" src="http://ensode.net/roller/dheffelfinger/resource/input_screen.png" /><br />Notice that we didn't have to specify any mappings in web.xml (as a matter of fact, web.xml is optional in modern JSF applications). By default, JSF pages are mapped to the /faces prefix.<br />When the user clicks on the Submit button, the processData() method on our PersonController class is executed, which takes us to the confirmation screen.<br /><img vspace="0" hspace="0" border="0" align="bottom" src="http://ensode.net/roller/dheffelfinger/resource/confirmation_screen.png" /><br /></p><h4>What I left out</h4><p>This post is meant as a quick introduction to JSF, so I obviously did not cover every JSF nook and cranny. There are lots of additional JSF tags that I didn't cover, there are JSF specific equivalents to every HTML input tag.<br /></p><p>JSF also has input validation built-in, we can make fields required and also accept only specific formats, for example. For application specific cases, we can develop our own custom validators.<br /></p><p>JSF has built-in data conversion, we saw this in action by adding a property of type short and having the user-entered value automatically converted to the appropriate type. JSF also allows us to develop custom data converters.<br /></p><p>JSF also has Ajax integration built in, a topic that I obviously didn't cover.<br />Finally, almost nobody develops “raw” JSF applications, the beauty of JSF is that allows the creation of component libraries. Most JSF applications employ one of these component libraries. Some of the most popular include PrimeFaces, RichFaces and IceFaces.<br /></p><h4>Where to go from here</h4><p>After reading this short blog post, you should have a pretty good idea of the basic mechanics of JSF. To learn more about it, I'd be very grateful if you purchased one my books, <a href="http://www.packtpub.com/java-ee-7-with-glassfish-4-application-server/book">Java EE 7 Development With GlassFish 4</a> or <a href="http://www.packtpub.com/java-ee-6-development-with-netbeans-7/book">Java EE 6 Development With NetBeans</a>, or, if you need personalized training, I can help you with that as well, just head over to my company web site: <a href="http://www.ensode.com">http://www.ensode.com</a> for my contact information.<br />Of course, there is a ton of free information on the web as well, now that you know the basics other tutorials out there that assume basic knowledge should make more sense, just use your favorite search engine to find out more. </p><p> The source code for the example shown in this post can be downloaded <a href="http://ensode.net/roller/dheffelfinger/resource/jsfinahurry.zip">here</a>.<br /></p><p><br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/java_lingo_for_non_javaJava Lingo for Non-Java PeopleDavid R. Heffelfinger2013-11-16T18:59:59+00:002013-11-16T19:43:03+00:00
<p><p><br/>
This post is meant for managers, business analysts, recruiters, and anyone else who needs to interact with Java developers but is not a Java developer him/herself.<br />Just like any other discipline, Java development is full with lingo that may be intimidating to those not in the field.</p><p><b>Java</b><br />Java itself is a programming language that is platform independent, which means that Java code can run unmodified on a variety of operating systems such as Windows, Linux/Unix, and Mac OS. Traditionally source code needs to be compiled for each specific platform, this is not the case for Java.</p><p><b>The Java Virtual Machine</b><br />But Java is not only a programming language, it is also a platform. Java code runs on the Java Virtual Machine (JVM), which translates Java bytecode (compiled Java code) into native code for each platform. There are several other languages that run in the JVM, such as JRuby, Clojure, Groovy, Ceylon and many others.</p><p><b>Eclipse, NetBeans, IDEA</b><br />Java applications are typically developed using an Integrated Development Environment (IDE), the three most popular IDEs are Eclipse, NetBeans and IntelliJ IDEA.</p><p><b>ANT, Maven, Gradle</b><br />Java applications also typically use a build tool to help compile, build and deploy applications, the three most popular build tools are ANT, Maven and Gradle.</p><p><b>Java EE, JEE, J2EE</b><br />Java is extremely popular for developing enterprise server side applications, these types of applications typically use a web based user interface, with the business logic running on a server. Java Enterprise Edition (Java EE) is a set of Application Programming Interfaces (APIs) used to develop server side applications. Sometimes Java EE is referred to as JEE, however the officially sanctioned name is Java EE and the use of the term JEE is discouraged by Oracle, the company behind the Java platform (Oracle bought Sun Microsystems, the original company behind Java, back in 2010). Java EE was formerly known as J2EE, the J2EE term was so popular that it is still commonly used to refer to Java EE.</p><p><b>Spring</b><br />The Spring framework is an alternate set of APIs used to develop server side applications. In general, server side Java developers belong to either the Java EE or Spring camps, rare is the developer that is a fan of both.<br /></p><p><b>GlassFish, Weblogic, Websphere, JBoss, Tomcat, etc</b><br />Server side Java applications are deployed to an application server. Application servers provide functionality that is common to all enterprise applications so that application developers don't have to concern themselves with implementing this functionality. For example, application servers take care of transaction management, security and scalability. Some examples of application servers include GlassFish, JBoss, WildFly, Weblogic and Websphere. Tomcat can be thought of as an application server as well, however strictly speaking, it is a servlet container, that is, it provides less functionality out of the box than full fledged application servers. Java applications written using Spring typically don't require a full fledged application server and can be deployed to Tomcat. Another popular servlet container is Jetty.</p><p><b>JSF, Struts, GWT, Etc</b><br />There are several Java web frameworks that are used to ease and accelerate the development of web based applications. JavaServer Faces (JSF) is the standard Java EE framework for web development. There are several JSF component libraries that run on top of JSF, these libraries make it easy to develop nice looking JSF based web applications. Some examples of these libraries include PrimeFaces, RichFaces and IceFaces. In addition to JSF, there are several other Java web frameworks such as Struts (considered by many to be a legacy framework), the Google Web Toolkit (GWT), Struts Web MVC and Wicket.</p><p><b>EJB</b><br />On the server side, Enterprise JavaBeans (EJBs) provide transactions, security and scalability out of the box. This frees Java developer from having to implement this functionality and allows them to focus on implementing the business logic.</p><p><b>JPA, Hibernate, MyBatis</b><br />There are Java APIs (Application Programming Interfaces) that help developers write code to interact with a database, the Java Persistence API (JPA) is the standard Java EE API used for this purpose. Hibernate and MyBatis (formerly known as iBatis) are two other popular libraries used for this purpose.<br /></p><p><br />So there you have it, my friend, after reading this post you'll have some idea of what the heck those Java guys are talking about or what it is that is needed for that Java developer position your company is hiring for.</p><p>Anything I missed? Leave a comment. <br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/so_you_want_to_become1So you want to become an independent consultant?David R. Heffelfinger2013-10-28T23:51:51+00:002013-11-01T01:08:44+00:00
<p><p>I have been an independent consultant for almost 7 years. Last month I had the opportunity to speak at the JavaOne conference, I identified myself as an independent consultant, after my talks a few attendees approached me to ask how to go about becoming one. </p><p>The other day a former coworker found my <a href="http://www.linkedin.com/in/dheffelfinger">LinkedIn profile</a>, saw that I'm independent now and gave me a call asking for advice and guidance on going on his own.</p><p>Since there seems to be a lot of interest in finding out how to strike it out on your own, I'll write down about my experiences here, then in the future direct people to this blog post.</p><p>The first thing I'd like to clarify is that I live in an area where most software development work is contract work anyway. Another thing that I'd like to point out is that by the time I decided to go out on my own I was already a published author, that fact helped me market my services and obtain work fairly easily. Your mileage, as they say, may vary.<br /></p><p>When doing contract work, there are three ways to go about it. </p><p><b>W2, 1099 or C2C?</b> <br /></p><p>When hired as a W2, you become a temporary employee of the company hiring you. The client (your temporary employer) takes care of your tax deductions. There are also 1099 contracts, in which the company hires you as an individual, but you are not their employee, you are responsible for deducting your own taxes. The third way to do it is a Corp to Corp contract, commonly abbreviated as C2C. When doing C2C contracts, you need to incorporate a company, in this case the clients hires your company, not you directly.</p><p>Before I incorporated <a href="http://www.ensode.com/">Ensode Technology, LLC</a>, I was doing a lot of W2 contracts, since like I mentioned before the majority of software development work in my area is contract work . W2 contracts usually lasts from 6 months to a year, in rare occasions it can go beyond that. Since I had no job security anyway I figured that I may as well go all the way, start my own company and incorporate. </p><p><b>How do I incorporate my own company?</b> <br /></p><p>Incorporating a company is very easy. First come up with a name, google it to make sure it is not taken (by the way Ensode stands for <b>En</b>terprise <b>So</b>ftware <b>De</b>velopment). I incorporated Ensode Technology online and didn't even had to get up from my seat, if I remember correctly it cost me about $100 USD. </p><p><b>Getting a Business Bank Account </b></p><p>You need to get a business bank account primarily so that you can get paid. Your clients will be writing checks to your company, not to you personally. Any bank will be more than happy to help you open an account with them.<br /></p><p><b>Getting Insurance</b><br /></p><p>After incorporating, the next step was to get insurance, a lot of clients won't do business with you unless you are insured. I have liability insurance covering up to $1,000,000, it costs me about $500 a year.</p><p><b>Taking care of tax deductions</b> <br /></p><p>Lastly, I hired a payroll service to take care of my tax deductions, that sets me back around $85 USD a month or so.</p><p>Once you have incorporated your company, gotten liability insurance and hired a payroll service (this third step is optional, but I highly recommend it), you are ready to strike it out on your own, so the next question get asked a lot is:</p><p> <b>How do you get projects?</b></p><p>When your company has only one employee, getting contracts is not much different from the way most other people find regular jobs. You post your resume on a job board, and wait for companies to contact you, once you start talking about a potential job, you should let them know that you are only looking for C2C contracts.</p><p>So there you have it, as you can see striking it out on your own is not really that hard. Good luck in your new venture.<br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/so_you_want_to_becomeSo you want to become a technical author?David R. Heffelfinger2013-10-19T17:19:29+00:002013-10-19T17:19:29+00:00
<p><p>Last month at the JavaOne conference I had the opportunity to participate in a birds of a feather session titled <a href="https://oracleus.activeevents.com/2013/connect/sessionDetail.ww?SESSION_ID=3692">"So you want to be a published technical author?"</a>. I was glad to share my experiences as a published book author, unfortunately the session was only 45 minutes and we had 5 people plus the moderator in the panel, so we didn't have time to cover everything we wanted to. Here are some things we covered during the session, plus a few more things that were left unsaid.</p><p><b> How do I get noticed?</b></p><p>The easiest way to get noticed is to blog about the topic you are interested in writing. Personally, the way I got discovered was when one of the articles I wrote for my own web site was linked to from <a href="http://www.theserverside.com/news/thread.tss?thread_id=36347">The Server Side</a>. My advice to aspiring authors would be to blog about your topic of choice then submit your own blog posts to Reddit, Hacker News and other popular technology sites.</p><p><b>Is it profitable?</b></p><p>Not directly. Yes, you'll get some extra cash, but not enough to live on. However, the fact that you are a published author will increase your demand as a programmer a lot, allowing you to charge higher rates. Also, being published opens the door to other opportunities that further increase your exposure, such as speaking engagements and invitations to write articles for high profile publications. A quote I read somewhere that deeply resonates with me: "You don't write books for the royalties, you write books for the consulting fees".<br /></p><p><b>How do you find the time to write?</b></p><p>Very few technical authors write books for a living, for most of us that is something we do on the side. Since we have a full time job we have to write on nights and weekends. Personally, I have a home office in my basement where I go on the evenings to work on my books.</p><p><b>What topics should I write about?</b> </p><p>Something you are passionate about. Personally, I tend to pick open source projects such as NetBeans and GlassFish and write about versions that are still in development and have not been officially released yet. I try to time the book publication to match the official release of the project in question. This approach has the risk that things I write about may change in the final version of the product, however the trade off is that your book will cover the latest version of the technology in question.<br /></p><p><br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/why_is_it_so_hardWhy is it so hard to find Java talent?David R. Heffelfinger2013-10-19T14:27:13+00:002013-10-19T14:27:13+00:00
<p><p>One common complaint that I hear from my clients and recruiter friends is that it is very hard to find good Java talent.</p><p>I am fortunate enough to be on the other side of the coin, I have been working with Java for several years now, I have authored several <a href="http://www.amazon.com/David-R.-Heffelfinger/e/B0034O0CIE">books</a> on Java and have been a speaker at Oracle's JavaOne conference on more than one occasion, so I'd like to think I'm one of those hard to find good Java developers.</p><p>Being on the other side of the coin, I am bombarded every day with emails from recruiters interested in my services, I am fortunate enough to be able to be selective about the projects I work with. In my experience there are three things that drive me away from accepting a project. Here are my suggestions on things you can do to attract top Java talent.</p><p><b>Make it easy to apply</b> </p><p>It is mind boggling to me the number of companies that require me to go fill out some long, convoluted form just so that I can apply for a job with them. I have several other companies that are dying to hire me, don't make it a hassle for me to apply for a job for you. On a similar note, many companies require me to fill out some form made in Word that duplicates all the information that already exists in my resume. </p><p>If you want me to work for you, don't make it a hassle for me to apply.</p><p><b>Be flexible with your tax terms</b></p><p>For quite a few years now, I've been an independent consultant, in order to do this, I had to incorporate, hire a payroll service, and get insurance for my business. I already have an infrastructure in place to run my business, therefore I only take Corp-to-Corp (C2C) contracts. A lot of companies do W2 only, or want a permanent employee only. Again, I have several potential clients that want to hire me and agree to my terms, your chances of hiring me are slim to none if you are unwilling or unable to do a C2C contract.</p><p><b> Your project has to be interesting</b></p><p>I'm not going to pull any punches here, a lot of the Java projects out there just suck, plain and simple. If what you want me to do is maintain an old J2EE application using Struts 1 and Spring 1 or 2, I'm not going to be very interested in your project. You need to modernize your infrastructure if you want to attract top Java talent. I have actually researched the topic on modernizing legacy server side Java web applications, and wrote a <a href="http://www.oracle.com/technetwork/articles/java/springtojavaee-522240.html">series of articles</a> for the Oracle Technology Network (OTN) a while back on the topic. The articles focus on Spring to Java EE migration, but the same concepts apply to J2EE to Java EE migration. If you need help modernizing a legacy project, <a href="http://www.ensode.com/">drop me a note</a>, this will certainly be an interesting project and I'll be happy to help.<br /></p><p><br /></p><p><br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/screencast_and_code_for_myScreencast and Code for my JavaOne Java EE 7 / HTML 5 PresentationDavid R. Heffelfinger2013-09-26T02:46:06+00:002013-09-26T02:47:33+00:00
<p><p>Earlier this week I had the pleasure and the privilege to give a talk at the 2013 JavaOne conference. The session was very well attended and liked.</p><p>In the session I gave a demo on how to develop JSF applications using HTML 5 friendly markup, that is, no JSF specific tags, instead using regular HTML 5 input fields with JSF attributes to bind user input to a CDI managed bean. I started the application using a sample Websocket application included with NetBeans as a base.<br /></p><p> Then I finished the demo by adding developing a Java EE Websocket server endpoint that returned a JSON containing data to populate the JSF/HTML5 page, and finally added some Javascript to the page to parse the JSON and populate the page. <br /></p><p>After the talk was over, a number of attendees asked for the source code to the demo. I wasn't expecting to be asked for the source code, so I hadn't uploaded it anywhere, but since there was demand for it, I just uploaded a zip file containing all of the demo source code. Feel free to <a href="http://ensode.net/downloads/Echo.zip">download</a> it and use it as you please.</p><p>Additionally, if you weren't able to make it to the talk, I just uploaded a screencast of the demo to Youtube, you can find it <a href="http://www.youtube.com/watch?v=jfQ0A-zgXd4">here</a>, or, even easier, embedded below. </p><p>If you would like to learn more about Java EE development with NetBeans, please check out my <a href="http://www.packtpub.com/java-ee-development-with-netbeans-7/video">Java EE Development with NetBeans</a> video course.</p><p> <br /></p><p> </p></p>
<p><iframe width="420" height="315" frameborder="0" src="http://www.youtube.com/embed/jfQ0A-zgXd4"></iframe></p>
http://mail.ensode.net/roller/dheffelfinger/entry/my_new_java_ee_developmentMy New Java EE Development With NetBeans Video Course is now availableDavid R. Heffelfinger2013-08-01T12:00:13+00:002013-08-01T12:00:13+00:00
<p><p>For the past several months I've been diligently working on developing a <b>Java EE Development with NetBeans</b> video course.</p><p> The course has just been published by Packt Publishing and is available for download at <a href="http://www.packtpub.com/java-ee-development-with-netbeans-7/video">http://www.packtpub.com/java-ee-development-with-netbeans-7/video</a>.</p><p>It covers all of the most popular Java EE Technologies and APIs including JSF, Facelets, EJB, and JPA, as well as many NetBeans specific tips and tricks to boost productivity.<br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/netbeans_tip_quickly_opening_windowsNetBeans Tip: Quickly opening windows without memorizing keyboard shortcutsDavid R. Heffelfinger2012-11-06T17:05:05+00:002012-11-06T20:44:53+00:00
<p><p>When working with NetBeans, sometimes I need to open a window to look at some information (breakpoints, output, etc). Windows can be accessed by going to the "Windows" pull down menu, then selecting the appropriate window, or, most windows have a keyboard shortcut (ctrl+1 for projects, for example).</p><p>The "Window" menu has several submenus, and it is not always entirely obvious where a specific window may be (the "Terminal" window, for example, is under "Output").</p><p> <img vspace="0" hspace="0" border="0" align="bottom" src="http://ensode.net/roller/dheffelfinger/resource/netbeans_window_menu.png" alt="NetBeans Window Menu" /></p><p> Sometimes I would like to open a window, but I'm not sure exactly where it is located, and I don't know it's keyboard shortcut.</p><p>Fortunately NetBeans has a "Quick Search" text field at the top right, and typing the name of the window makes it appear in the search results, therefore, if I want to open the "Breakpoints" window, for example, all I have to do is type "Breakpoints" in the quick search</p><p><img vspace="0" hspace="0" border="0" align="bottom" src="http://ensode.net/roller/dheffelfinger/resource/netbeans_search_window.png" alt="NetBeans search window" /><br /></p><p><br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/java_one_jsf_with_netbeansJava One JSF with NetBeans BOF DemoDavid R. Heffelfinger2012-10-06T16:18:31+00:002012-10-06T16:18:31+00:00
<p><p>I had the pleasure of being a speaker at this year's JavaOne conference. One of the sessions I participated was a Birds of a Feather (BOF) session on JSF development with the NetBeans IDE.</p><p>During the demo I showed how a complete, nice looking application can be developed in only a few minutes using NetBeans.</p><p>For the benefit of those that couldn't attend the session, here is a video of said demonstration.</p><p>For those that want to learn more, I wrote a <a href="http://www.packtpub.com/java-ee-6-development-with-netbeans-7/book">book on NetBeans and Java EE</a>.</p><p> </p><p><br /></p></p>
<p><iframe width="560" height="315" src="http://www.youtube.com/embed/BTzP2ln6wmY" frameborder="0" allowfullscreen></iframe></p>
http://mail.ensode.net/roller/dheffelfinger/entry/trying_to_keep_an_openTrying to keep an open mind in the Spring Vs Java EE DebacleDavid R. Heffelfinger2012-04-29T12:38:13+00:002012-04-29T12:38:13+00:00
<p><p>One common criticism of my Spring to Java EE Migration article series (see <a href="http://www.oracle.com/technetwork/articles/java/springtojavaee-522240.html">part 1</a>, <a href="http://www.oracle.com/technetwork/articles/java/springtojavaee2-1414289.html">part 2</a>, <a href="http://www.oracle.com/technetwork/articles/java/springtojavaee3-1569377.html">part 3</a> and <a href="http://www.oracle.com/technetwork/articles/java/springtojavaee4-1592643.html">part 4</a>) is that the article uses an old version of Spring against a modern version of Java EE. There's a reason for that, since project using older versions of Spring are the most likely ones to be looking to migrate to a newer technology stack, be it a newer version of the Spring Framework, Java EE or something else.</p><p>Nevertheless, truth be told, I've been focusing on Java EE projects for the last few years, and the times I've used Spring have been when maintaining legacy applications that don't use modern versions of the Spring framework.</p><p> Trying to keep an open mind, I bought <a href="http://www.amazon.com/gp/product/1449306403/ref=as_li_ss_tl?ie=UTF8&tag=ensode-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=1449306403">Just Spring</a> by Madhusudhan Konda for my <a href="http://www.amazon.com/gp/product/B0051VVOB2/ref=as_li_ss_tl?ie=UTF8&tag=ensode-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=B0051VVOB2">Kindle Fire</a>. The book uses Spring 3.0, versus Spring 2.5 in my article series. I decided to go for this book since it is a quick read (just over 60 pages), I didn't want to have to go through a 300+ behemoth of a book just to see if my opinion of Spring was outdated.</p><p>Quite frankly, the book did little to change my opinion in the Java EE vs Spring debacle. Although annotations get a brief mention in Konda's book, most of the examples still use XML configuration, and the seemingly endless XML needed to do anything nontrivial in Spring is one of the main reasons I'm not a fan of the framework. <br /></p><p> </p><p>To learn more about Java EE development, please check out my own books, <a href="http://www.amazon.com/gp/product/1849510369/ref=as_li_ss_tl?ie=UTF8&tag=ensode-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=1849510369">Java EE 6 with GlassFish 3 Application Server</a> and <a href="http://www.amazon.com/gp/product/1849512701/ref=as_li_ss_tl?ie=UTF8&tag=ensode-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=1849512701"> Java EE 6 Development with NetBeans 7</a>.<br /></p><p> </p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/tar_failing_with_error_messagetar failing with error message "file changed as we read it"David R. Heffelfinger2012-04-28T17:27:10+00:002012-04-28T17:28:45+00:00
<p><p>Today I'm upgrading my laptop to the recently released Ubuntu 12.04 Precise Pangolin.</p><p>Even though I have my /home directory in it's own partition and the installer shouldn't wipe it out, I'm erring on the side of caution and backing up my home directory before beginning the installation.</p><p>I'm using the Linux tar command to compress and back up my home directory, but for some reason after waiting for several minutes the command kept failing with the following error message:</p><p>"file changed as we read it"</p><p>After googling for a bit I found the solution to the problem, using the <font face="'courier new', courier, monospace">--ignore-failed-read</font> flag for tar took care of the issue.</p><p><font face="'courier new', courier, monospace">tar --ignore-failed-read -ztvf backup.tar.gz /home/myhomedir</font></p><p>did the trick. </p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/spring_to_java_ee_migration2Spring to Java EE Migration Article, Part 4David R. Heffelfinger2012-04-28T17:20:11+00:002012-04-28T17:20:12+00:00
<p><p>The fourth and final part of my Spring to Java EE migration article series has been published.</p><p><a href="http://www.oracle.com/technetwork/articles/java/springtojavaee4-1592643.html">Spring to Java EE Migration, Part 4</a> </p><p>Part 4 compares equivalent functionality in Java EE and Spring, covering topics such as MVC design pattern implementation, data access, transaction management, and dependency injection. </p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/spring_to_java_ee_migration1Spring to Java EE Migration Article, Part 3David R. Heffelfinger2012-04-04T21:25:35+00:002012-04-04T21:25:35+00:00
<p><p><a href="http://www.oracle.com/technetwork/articles/java/springtojavaee3-1569377.html">Part 3 of my Spring to Java EE migration</a> article series has been published.</p><p>This part covers how to tweak the NetBeans-generated JSF user interface and compares the Spring and Java EE versions of the Pet Clinic application. </p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/spring_to_java_ee_migrationSpring to Java EE Migration, Part 2David R. Heffelfinger2011-12-17T11:57:46+00:002011-12-17T11:57:46+00:00
<p><p><a href="http://www.oracle.com/technetwork/articles/java/springtojavaee2-1414289.html">Part 2</a> of my Spring to Java EE migration series has been published. </p><p>This part of the article shows off NetBeans Java EE capabilities, such as automatically generating JSF pages, JSF managed beans and Data Access Objects (DAO's) implemented as EJB session Beans. </p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/new_spring_to_java_eeNew Spring to Java EE Migration Article SeriesDavid R. Heffelfinger2011-11-02T10:41:54+00:002011-11-02T10:41:54+00:00
<p><p>For the past few weeks I've been working on a new article series for the <a href="http://www.oracle.com/technetwork/index.html">Oracle Technology Network</a>. The topic of the series is Spring to Java EE migration using the NetBeans IDE. </p><p><a href="http://www.oracle.com/technetwork/articles/java/springtojavaee-522240.html">Part 1</a> of the series was just published. In this part we begin migrating Spring's sample Pet Clinic application to standard Java EE APIs such as JavaServer Faces (JSF) and the Java Persistence API (JPA), while showcasing time saving NetBeans features such as JPA entity generation.</p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/ordered_a_sony_xperia_playOrdered a Sony Xperia Play from AmazonDavid R. Heffelfinger2011-09-04T13:04:35+00:002011-09-04T13:04:35+00:00
<p><p>Amazon has a deal going on for the <a href="http://www.amazon.com/gp/product/B004UBD066/ref=as_li_ss_tl?ie=UTF8&tag=ensode-20&linkCode=as2&camp=217145&creative=399373&creativeASIN=B004UBD066">Sony Xperia Play</a> for one cent (<span id="wirelessPriceFromValue"><span id="wirelessPriceFromPrice">$0.01) with a two year contract with Verizon Wireless.</span></span></p><p>I was already with Verizon and fairly happy with them, and my old Motorola Droid was starting to show it's age (the power button sometimes doesn't work, I have to press it multiple times to turn the phone on or off), so I decided to give it a go.</p><p> For those that don't know, the Xperia Play is the so called "Playstation Phone", that has a built in game pad and several exclusive titles. The XPeria play also has stock Android 2.3 (Gingerbread). I'm not a fan of Android skins like Sense UI and others, since having those skins make the phones harder to upgrade for the manufacturer, since they have to update their skins for every new version of Android.</p><p>As far as the Sony Xperia Play goes, I am primarily interested in getting a Stock Android Gingerbread device for 1 cent, plus it is a nice hardware upgrade for me. The fact that it has a built in gamepad and exclusive games is just gravy, at least it will give me something to do during my daily bus and train commute.<br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/kevin_mitnick_s_ghost_inKevin Mitnick's "Ghost in the Wires"David R. Heffelfinger2011-09-01T23:07:09+00:002011-09-01T23:28:00+00:00
<p><p>I just finished reading Kevin Mitnick's new book, <a href="http://www.amazon.com/gp/product/0316037702/ref=as_li_ss_tl?ie=UTF8&tag=ensode-20&linkCode=as2&camp=217145&creative=399369&creativeASIN=0316037702">Ghost in the Wires</a><img width="1" height="1" border="0" style="border: medium none ! important; margin: 0px ! important;" src="http://www.assoc-amazon.com/e/ir?t=&l=as2&o=1&a=0316037702&camp=217145&creative=399369" />, on my Kindle.</p><p>I remember learning about Mitnick by reading about him on <a href="http://www.slashdot.org">Slashdot</a> via the "Free Kevin" movement several years ago. </p><p>Mitnick's life story is quite interesting, and the book is full of several interesting anecdotes. </p><p>He explains how he was able to figure out a way to travel for free on the bus as a kid; illustrating how he had an ability for social engineering from a young age.</p><p>Mitnick then goes on to tell the story explaining how some friends from high school introduced him to phone phreaking, making long distance phone calls for free. <br /></p><p>He also tells a story on how he was able to defeat the security of the computer systems in the college he was attending, and how his professors asked him to secure the system as an "honors project" or face expulsion. </p><p>The book is full of several stories detailing how he was able to break into several computer systems, steal cell phone service, monitor phone calls (including FBI lines), obtain new identities and other clever and "less than legal" activities. Mitnick had an ability for social engineering, that is, he could easily dupe people into giving him information that he shouldn't have. He would call companies and pretend to be a coworker or customer, and more often than not he could convince the other person on the line to do something for him or provide some confidential information, including usernames and passwords.</p><p>All in all, <a href="http://www.amazon.com/gp/product/0316037702/ref=as_li_ss_tl?ie=UTF8&tag=ensode-20&linkCode=as2&camp=217145&creative=399369&creativeASIN=0316037702">Ghost in the Wires</a><img width="1" height="1" border="0" style="border: medium none ! important; margin: 0px ! important;" src="http://www.assoc-amazon.com/e/ir?t=&l=as2&o=1&a=0316037702&camp=217145&creative=399369" /> is a very interesting read, and very much worth it for anybody interested in computers or security.<br /></p></p>
http://mail.ensode.net/roller/dheffelfinger/entry/james_gosling_father_of_javaJames Gosling, Father of Java, Leaves GoogleDavid R. Heffelfinger2011-08-31T22:51:19+00:002011-09-01T13:22:26+00:00
<p><p>A while back, there were news all over the blogosphere about James <br/>
Gosling, father of Java, leaving Oracle shortly after the database giant<br/>
bought Sun Microsystems.</p><p> Gosling was unemployed for a while, but in March 2011, he went to work for Google. Today he published a <a href="http://nighthacks.com/roller/jag/entry/i_ve_moved_again">new blog entry</a>, announcing that he left Google to join a company called <a href="http://liquidr.com/">Liquid Robotics</a>, a company that makes an unmanned ocean vehicle called the Wave Glider.</p><p>I'm<br/>
surprised that Mr. Gosling decided to leave Google after less than six <br/>
months of employment; nevertheless I wish him the best of luck in his <br/>
new endeavors. I'm sure Liquid Robotics will benefit greatly from the <br/>
positive public relations of having the father of Java join their <br/>
company, and I'm sure they are hoping his tenure will be longer than the<br/>
one he had at Google.<br /></p></p>