This video tutorial covers the Mockito framework and testing REST APIs/services.

A developer discusses the idea of quarantining as a means of mitigating risk in software and how it can be applied to the development of microservices.

Migrate from Sencha EXTJS to ReactJS in a few, simple steps.

Curious about Vue's application data store? Read on to learn how to move your exiting Vue.js project to Vuex, and get an expert's opinion on what this does.

Java serialization is convenient to store the state of Java objects. However, there are some drawbacks of serialized data: It is not human-readable. It is Java-specific and is not exchangeable with other programming languages. It is not migratable if fields of the associated Java class have been changed. These drawbacks make Java serialization not a practical approach to storing object states for real-world projects. In a product developed recently, we use XStream to serialize/deserialize Java objects, which solves the first and second problems. The third problem is addressed with XMT, an open source tool developed by us to migrate XStream serialized XMLs. This article introduces this tool with some examples. Computer Languages Need to be Simplified So many of the issues that we all run into when we are working on converting computer languages into something that can be better understood by human beings is the fact that computer languages need to be simplified if possible. These languages are great for the computers that speak back and forth with one another, but they don’t necessarily work out as well when humans try to become involved with them. Many humans end up confused and unable to make much progress at all on getting these systems cleared up. Thus, it is necessary to get them cleaned up and made more usable. There are people who are actively working on this problem right now, but in the meantime, we may simply have to deal with computers that can’t do everything we would like for them to do. XStream deserialization problem when class is evolved Assume a Task class below with a prioritized field indicating whether it is a prioritized task: package example; public class Task { public boolean prioritized; } With XStream, we can serialize objects of this class to XML like below: import com.thoughtworks.xstream.XStream; public class Test { public static void main(String args[]) { Task task = new Task(); task.prioritized = true; String xml = new XStream().toXML(task); saveXMLToFileOrDatabase(xml); } private static void saveXMLToFileOrDatabase(String xml) { // save XML to file or database here } } The resulting XML will be: true And you can deserialize the XML to get back task object: import com.thoughtworks.xstream.XStream; import com.thoughtworks.xstream.io.xml.DomDriver; public class Test { public static void main(String args[]) { String xml = readXMLFromFileOrDatabase(); Task task = (Task) new XStream(new DomDriver()).fromXML(xml); } private static String readXMLFromFileOrDatabase() { // read XML from file or database here } } Everything is fine. Now we find that a prioritized flag is not enough, so we enhance the Task class to be able to distinguish between high priority, medium priority and low priority: package example; public class Task { enum Priority {HIGH, MEDIUM, LOW} public Priority priority; } However, deserialization of previously saved XML is no longer possible since the new Task class is not compatible with the previous version. How does XMT Address the Problem XMT comes to the rescue: it introduces the class VersionedDocument to version serialized XMLs and handles the migration. With XMT, serialization of task object can be written as: package example; import com.pmease.commons.xmt.VersionedDocument; public class Test { public static void main(String args[]) { Task task = new Task(); task.prioritized = true; String xml = VersionedDocument.fromBean(task).toXML(); saveXMLToFileOrDatabase(xml); } private static void saveXMLToFileOrDatabase(String xml) { // save XML to file or database here } } For task class of the old version, the resulting XML will be: true Compared with the XML generated previously with XStream, an additional attribute version is added to the root element indicating the version of the XML. The value is set to "0" unless there are migration methods defined in the class as we will introduce below. When Task class is evolved to use enum based priority field, we add a migrated method like the below: package example; import java.util.Stack; import org.dom4j.Element; import com.pmease.commons.xmt.VersionedDocument; public class Task { enum Priority {HIGH, MEDIUM, LOW} public Priority priority; @SuppressWarnings("unused") private void migrate1(VersionedDocument dom, Stack versions) { Element element = dom.getRootElement().element("prioritized"); element.setName("priority"); if (element.getText().equals("true")) element.setText("HIGH"); else element.setText("LOW"); } } Migration methods need to be declared as a private method with the name in the form of "migrateXXX", where "XXX" is a number indicating the current version of the class. Here method "migrate1" indicates that the current version of the Task class is of "1", and the method migrates the XML from version "0" to "1". The XML to be migrated is passed as a VersionedDocument object which implements the dom4j Document interface and you may use dom4j to migrate it to be compatible with the current version of the class. In this migration method, we read back the "prioritized" element of version "0", rename it as "priority", and set the value as "HIGH" if the task is originally a prioritized task; otherwise, set the value as "LOW". With this migration method defined, you can now safely deserialize the task object from XML: package example; import com.pmease.commons.xmt.VersionedDocument; public class Test { public static void main(String args[]) { String xml = readXMLFromFileOrDatabase(); Task task = (Task) VersionedDocument.fromXML(xml).toBean(); } private static String readXMLFromFileOrDatabase() { // read XML from file or database here } } The deserialization works not only for XML of the old version but also for XML of the new version. At deserialization time, XMT compares the version of the XML (recorded in the version attribute as we mentioned earlier) with the current version of the class (maximum suffix number of various migrate methods), and runs applicable migrate methods one by one. In this case, if an XML of version "0" is read, method migrate1 will be called; if an XML of version "1" is read, no migration methods will be called since it is already up to date. As the class keeps evolving, more migration methods can be added to the class by increasing the suffix number of the latest migration method. For example, let's further enhance our Task class so that the priority field is taking a numeric value ranging from "1" to "10". We add another migrate method to the Task class to embrace the change: @SuppressWarnings("unused") private void migrate2(VersionedDocument dom, Stack versions) { Element element = dom.getRootElement().element("priority"); if (element.getText().equals("HIGH")) element.setText("10"); else if (element.getText().equals("MEDIUM")) element.setText("5"); else element.setText("1"); } This method only handles the migration from version "1" to version "2", and we do not need to care about version "0" anymore, since the XML of version "0" will first be migrated to version "1" by calling the method migrate1 before running this method. With this change, you will be able to deserialize the task object from XML of the current version and any previous versions. This article demonstrates the idea of how to migrate field change of classes. XMT can handle many complicated scenarios, such as migrating data defined in multiple tiers of class hierarchy, addressing class hierarchy change, etc. For more information of XMT, please visit http://wiki.pmease.com/display/xmt/Documentation+Home

It is a computer file known as an image that functions much like a real computer. Windows, Linux, and other operating systems can all run it.

This article presents the features and advantages of Microsoft Azure Service Fabric, a platform that simplifies the creation and administration of microservices.

This article is about automating processes, workflows, etc., using Platform as a Service (PaaS) from Microsoft Azure's Azure Logic Apps.

Azure Key Vault is a Key Management system that can be used. The encryption keys to encrypt your data are simple to create and manage.

Azure AD is a cloud service for managing identities and access that facilitates access to additional SaaS applications, the Azure portal, and external resources.

This microservice building tutorial continues by walking through Eureka service discovery, the config server and user service, and configuring the email service.

In the era of containers (the ''Docker Age'') Java is still on top, but which is better? Spring Boot or Quarkus?

Mixing a few JBoss tools, Apache Camel, OpenShift Enterprise, and a little secret sauce to make your home smarter.

We continue our introductory series on microservices by taking a look at some of the advantages they offer devs and architects.

Microservies and Docker have become the peanut butter and jelly of modern app delivery. They allow organizations to work in a consistent, isolated runtime environment.

How to deploy a Micronaut application using GET, PUT, and POST, and how its performance compares to when it's deployed with JVM runtime vs. as a native language.

See this developer's journey creating a React Native app with MiBand 3.

Today we complete our trilogy of interviews with the Individual Eclipse Community Awards nominees with the Top Committer nominees. The award is to recognize an Eclipse committer who best exemplifies support for the community through newsgroups, Bugzilla, white papers, conference presentations, blogs and other forums. This year's Top Committer nominees are: Martin Oberhuber Martin has been nominated for his work in leading the TM project and for reviving the Eclipse Architecture Council. Steffen Pingel Steffen has been nominated for his contributions to the Mylyn project, with half of last year's commits to the project coming from him. Thomas Watson Thomas has been nominated for being the man behind the Equinox curtain. He also represents Eclipse on the EEG and CPEG committees at OSGi.org Jason Weathersby Jason is well known for his work on the BIRT project, speaking at conferences, monitoring the news group and writing papers. Paul Webster Paul has been nominated for his efforts helping people on IRC and newsgroups. David Williams David has been nominated for his work on the WebTools project, providing an incubator within WebTools and for helping to catch those release trains Over the next few pages we will introduce and interview each of the nominees. It's interesting to see what each of these guys do for the community, so please consider each of the nominees before you place your vote. Martin Oberhuber DZone: Congratulations on the nomination Martin. Could you tell us more about yourself? Martin: I'm 37 years old, married and got 2 kids. I live in Salzburg, Austria, and have been working for Wind River (formerly TakeFive software) since 10 years. I've always been interested in software development process and practices to ensure top quality. I'm glad that quality plays such a big role at Eclipse. In my little spare time, I like reading, skiing and hiking. DZone: What are the main things that you do within the community? Martin: I'm leading the DSDP Target Management Project, and I'm a platform core committer, but I guess what's most important to the Community is my role on the Eclipse Architecture Council. As the chair of the AC, I see myself as a facilitator: collecting the topics that the Community cares about, and bringing the great people together that we have in order to move things forward in a positive way. I'm also active on the Galileo cross-project list, testing things and filing bugs to ensure that the Release train really works as a whole as it should. DZone: How long have you been involved with Eclipse? Martin: Wind River proposed the Device Software Development Platform (DSDP) project in March 2005, and along with it the Target Management project was created shortly after. I've been leading the TM project since it's inception, but have also been reaching out to the wider community from the beginning. DZone: Do you have a favourite project within the Eclipse ecosystem? Martin: There's so many exciting new things going on that it's hard to make a choice here. I'm really thrilled about the great amount of innovation and quality work. If I must make a choice, I guess that the Platform and Equinox are still dearest to me because they really are the enablers for all the great work going on -- both in terms of technology and the exemplary process that they have been practicing. DZone: In the Eclipse world, what were your highlights of 2008, and what are you looking forward to in 2009? Martin: Well my personal highlight of 2008 is being able to serve on the Architecture Council. It's really exciting to be able and work with some of the greatest engineers in our industry to move things forward. I'm really glad that Wind River allows me to spend the time for this work. For 2009, I'm most looking forward to the work on the e4 project, exploring some fundamental change in the base Eclipse architecture while still doing our best to remain compatible to clients. The work surrounding this is really exciting. DZone: What is your full time job? Martin: I'm employed by Wind River as a full time Eclipse committer and contributor to other Open Source projects. Of that time, in the past quarter I've been spending about 30% for the TM project, 30% for the Architecture Council, 30% for the Platform and e4, and 10% for other Open Source projects (JSch, RXTX, Apache Commons). Of course things are changing quickly in our industry, and my priorities have been shifting as needed. DZone: What do you like most about contibuting to Eclipse? Martin: Working in a multi-national setting of great engineers and the high focus on quality. DZone: Is it difficult for you to find the time to commit to Eclipse projects? Martin: No, thanks to my employer, Wind River, who's sponsoring my work full time. DZone: Why do you think you should be chosen as Top Committer? Martin: Because I'm caring for the Community, looking beyond just my own projects, and working to improve things for all committers. Steffen Pingel DZone: Congratulations on the nomination Steffen. Could you tell us more about yourself? Steffen: I graduated from the University of Stuttgart, Germany two years ago. During my Masters' degree, I got involved with Eclipse by creating the Mylyn Trac connector as a Google Summer of Code student in 2006. At that same time, I was in the process of moving to New York city to work as a Java developer on Swing applications but I stayed involved with the Mylyn project in my spare time, and earned my commit rights. My contributions made it into the June 2007 release of Mylyn 2.0. After that, Tasktop Technologies, the startup that created and leads Mylyn, extended me an offer to work full time on Mylyn and Mylyn-based technologies.I have since moved to Canada where a lot of the Eclipse excitement is happening. I enjoy working on tools that keep developers focused and productive, when I am not riding my bike in the beautiful mountains surrounding Vancouver. DZone: What are the main things that you do within the community? Steffen: Most of my Eclipse time is spent collaborating with the community through Bugzilla and the Mylyn newsgroup. The Mylyn project has a very active user base who keeps me busy with a never ending stream of feedback and contributions. We applied over 130 patches for the next 3.1 release in March alone. While prioritizing contributions is a great way to evolve the tool to users' and integrators' needs, I also enjoy hacking on new Mylyn features. DZone: How long have you been involved with Eclipse? Steffen: I started using Eclipse for Java programming when support for Emacs key-bindings was added. Ever since the time I spent in the workbench has steadily increased. Thanks to the endless number of extensions I now do the occasional Python and C++ hacking in Eclipse and don't need to rely on browsers and emails for tracking tasks anymore. My first serious exposure to plug-in programming was getting my feet wet as a Google Summer of Code student. Since then I have been getting sucked into the broader Eclipse community and taken over more responsibilities in the Mylyn project. I am managing the project's participation in the Ganymede and Galileo release train and I am also one of the maintainers of the Java EPP package. DZone: Do you have a favourite project within the Eclipse ecosystem? Steffen: That's easy. Mylyn. DZone: In the Eclipse world, what were your highlights of 2008, and what are you looking forward to in 2009? Steffen: The Ganymede release is the first 2008 Eclipse highlight that comes to mind. As part of that I worked hard on releasing Mylyn 3.0 which was a major milestone for the project. My favorite new Eclipse feature that was added last year is PDE's API tooling. It's the type of automation that makes maintaining API much easier. And it helps us ensure that we don't cause integrators problems by accidentally changing public method signatures. I also had the privilege to be a Google Summer of Code mentor last year. Owen Ou integrated rich text wiki editing with the Mylyn task editor based on WikiText which is a new component contributed by David Green. It was great to be part of this team effort and to see the results of the project which are now being released for the first time. I am very much looking forward to EclipseCon in March. It's always a great opportunity to meet other committers in person. This year it will be my first time to give a talk at the conference so I am extra excited. DZone: What is your full time job? Steffen: I am a software developer at Tasktop Technologies, which is the company behind the Mylyn project. DZone: What do you like most about contibuting to Eclipse? Steffen: I keep being impressed by the quality and extensibility of the platform. It's fun to work with the rich APIs and solid framework Eclipse provides. It also sets a high bar for every Eclipse project to meet the same standard. I enjoy this challenge and the positive community feedback makes it worth the effort. DZone: Is it difficult for you to find the time to commit to Eclipse projects? Steffen: Yes, even though I am in the great position that Eclipse development has become my day-to-day job it's still challenging at times to find enough cycles to dedidicate to Mylyn between my different responsibilities at Tasktop. DZone: Why do you think you should be chosen as Top Committer? Steffen: As a committer, my goal is to build solid, reusable frameworks. Eclipse thrives on everyone's participation which I am supporting through my active involvement with cross-project, the EPP project and user community. Thomas Watson DZone: Congratulations on the nomination Thomas. Could you tell us more about yourself? Thomas: I live, work and play in Austin, Texas with my wife and 7 month old daughter. I have been developing software for the past 11 years at IBM and have worked on a number of projects with-in IBM including network computers, service gateways, embedded devices and server technologies. I have spent the better part of the past 7 years working on the OSGi specification and implementing various parts of the specification in the Equinox project at Eclipse. DZone: What are the main things that you do within the community? Thomas: I am the co-lead of the Equinox project and the lead developer of the Equinox OSGi framework. DZone: How long have you been involved with Eclipse? Thomas: In the Summer of 2003 I became a member of the Equinox technology project to assist the Core Platform team in moving the Eclipse 3.0 runtime over to the OSGi Framework. Since then I have become the development lead of the Equinox OSGi Framework and the co-lead of the Equinox project. The Equinox project has come a long ways since its initial days as a technology project at Eclipse. DZone: Do you have a favourite project within the Eclipse ecosystem? Thomas: Other than the Equinox project I would say e4. I think they are really starting to do some interesting things in e4 and I hope to be able to contribute some time to the project in the future. DZone: In the Eclipse world, what were your highlights of 2008, and what are you looking forward to in 2009? Thomas: In 2008 there has been continued growth in the use and interest of OSGi technology and the modularity runtime it provides. An Enterprise Expert Group was started at the OSGi Alliance to investigate using the modularity concepts of OSGi in the enterprise space. I have enjoyed working on the new challenges and developing the next OSGi R4.2 specification as well as implementing the specification within the Equinox project. In 2009 I look forward to participating in e4. In particular I hope to be able to spend time working on modularity in other languages besides Java. I also look forward the next major release of the OSGi specification. I hope we can finally modernize the OSGi API. Perhaps I can finally start using features of JavaSE 1.5. DZone: What is your full time job? Thomas: Sometimes it feels like I have two full time jobs. My first job is my roles as an Eclipse committer which includes co-leading the Equinox project and development lead of the Equinox OSGi Framework. My second job is participating in the expert groups within the OSGi Alliance developing the next versions of the OSGi specification. DZone: What do you like most about contibuting to Eclipse? Thomas: I enjoy the community of Eclipse and working on a core technology that get used by such a diverse set of projects at Eclipse as well as others outside of Eclipse. DZone: Is it difficult for you to find the time to commit to Eclipse projects? Thomas: I have the luxury of having a day job that requires I participate in Eclipse. I easily consume more than enough hours in the day working on Eclipse. The question is do I find it difficult to do anything else? DZone: Why do you think you should be chosen as Top Committer? Thomas: I am very active in both the Eclipse community and the OSGi community developing modularity features needed by the Eclipse platform. Jason Weathersby Waiting.. Paul Webster DZone: Congratulations on the nomination Paul. Could you tell us more about yourself? I've been working in the industry for about 14 years now in C, C++, and Java, and up until I joined the eclipse team mostly on low level framework or networking applications. I went to school in Waterloo, and currently work for IBM Rational in Ottawa. > -What are the main things that you do within the > community? I try and answer questions in the eclipse.platform.* branch of newsgroups :-) > -How long have you been involved with Eclipse? (and in > what ways) I've been working on Eclipse for almost 4 years on the Platform UI team. I started off in presentations and workbench part lifecycle, and then moved onto actions and commands. > -Do you have a favourite project within the Eclipse > ecosystem? I'm quite partial to EMF+GMF (it can do cool things). > -In the Eclipse world, what were your highlights of 2008, > and what are you looking forward to in 2009? 2008 included Eclipse 3.4, which had some new and very useful features (especially in the PDE area) and but also had some improvements to help mature the Commands Framework. In 2009 I hope to get the chance to contribute to some of the Eclipse 4.0 work (e4) which I think has a lot of potential. > -What is your full time job? IBM employs me as a full time committer on the Eclipse Platform UI team. > -What do you like most about contibuting to Eclipse? I like working through the public bugs and mailing lists. Communication with our downstream consumers is very important and I think that on some other software projects (especially commercial ones) it is hard to get that communication that level of communication. > -Is it difficult for you to find the time to commit to > Eclipse projects? Not in my case, no :-) > -Why do you think you should be chosen as Top Committer? Ha, would you believe I don't have an answer for that except it would be a good opportunity to poke fun at Chris Aniszczyk :-) s David Williams -Congratulations on the nomination David. Could you tell us more about yourself? I've worked in the software industry for 25 years, all for IBM. First in Usability, making products (software and hardware) easier to use. Then in Software Consulting, mentoring customer developers on how best to use VisualAge for Smalltalk, and then VisualAge for Java, along with all the principles and best practices of OO Programming. And then I worked with Eclipse. At first, for several years, I was a consumer of Eclipse which formed the platform of some some commercial products we were developing. In 2004 we started the Web Tools Platform Project and that's when I became an Eclipse committer. -What are the main things that you do within the community? I am the WTP PMC Lead where I try to influence the whole of WTP in positive directions and try to keep it vibrant, and diverse. I'm also on the Eclipse Foundation Planning Council, which is a group made up of members from each Eclipse Project, and together we decide how and when to do our simultaneous release each year. I also recently became lead of the Orbit Project, which is a repository of OSGi bundles for use by other Eclipse Projects. So, I have lots of opportunities to work with other Eclipse Projects. In day-to-day terms, the main things I do are monitoring the mailing lists and bugzilla notices, helping to answer questions when I can. Looking for ways to make things easier for developers and the community. -How long have you been involved with Eclipse? (and in what ways) Technically, I was involved before it was called Eclipse ... and, before there was an Eclipse Foundation. But, I like to think of "starting" in 2004 ... about the same time the Eclipse Foundation was formed ... and when I became an official Eclipse committer. Then I learned that developing in the open makes you very vulnerable ... everyone can see your mistakes and ignorance. It turns out, luckily, that is a good thing. Gradually I have became less involved in day-to-day programming, and more involved in over all project leadership and architecture. -Do you have a favorite project within the Eclipse ecosystem? Web Tools of course! -In the Eclipse world, what were your highlights of 2008, and what are you looking forward to in 2009? The Releases and advances in the Web Tools Platform are always the largest highlights. But the most personally rewarding things are the smaller, everyday things ... seeing incubating projects start to blossom, seeing the collaboration between projects and developers bloom into some useful result or bug fix. Plus, I do look forward to EclipseCon every year! -What is your full time job? This is it! I'm very lucky (or, crafty?) that my company is willing to pay for my (nearly) full time involvement with Eclipse. I have the impression that's becoming more rare at Eclipse. Of course, that's not just altruistic on their part. Eclipse in general, and the parts I'm responsible for, all benefit our Products in one way or another. -What do you like most about contributing to Eclipse? The collaboration with a wide-range of diverse groups. I think development in the open is the best way to develop software ... and, makes it more interesting and fun to see others ways of working or solving a problem. -Is it difficult for you to find the time to commit to Eclipse projects? There's never enough time in the day, if that's what you mean, but on the other hand, I always make time to contribute something. -Why do you think you should be chosen as Top Committer? Honestly, I do not know. Don't get me wrong, I'm honored to have been nominated ... and enjoy being appreciated, just like everyone does ... but there are so many talented and deserving people at Eclipse, I think it is very hard to choose any particular one as "top". I think I was nominated because I have helped some incubating projects get started at Eclipse. Part of that is helping them get through the bureaucracy and technicalities, but I'd like to think, too, that I help new committers feel more comfortable and learn the ways of Eclipse. So now you have met most of the nominees for the Top Ambassador, Top Contributor and Top Committer awards. We hope that we have made it easier for you to choose who to vote for.

I hope everyone wants a slice of Raspberry Pi because there's a lot of it this month! Here's some inspiration for your next IoT project.

Automation: for when you can't (or just can't be bothered to) do it manually.