In addition to zero trust, using appropriate tooling like SASE can help secure an organization’s IT infrastructure from threats posed by third-party access.
Some have probably been expecting it for a long time, and this week it finally happened. Apache Harmony, an open source cleanroom implementation of Java was moved to the Apache Attic, where inactive projects are sent. The project management committee voted 20 to 2 in favor of discontinuing the project. One of the votes against moving Harmony to the Attic was PMC chair Tim Ellison, who thought it was too early to deactivate Harmony. But Harmony was probably already dead and buried once it's primary corporate sponsor, IBM, switched its support to OpenJDK last year. Android has not gotten invovled in the Harmony project recently because of their ongoing lawsuit with Oracle. Developers may still use the code while it resides, inactive, in the Apache Attic. Here were some comments from last year when most predicted the death of Harmony: "Well, pragmatically I would prefer one great open source JVM, rather than multiple average ones. So as long as OpenJDK is still GPL, I see no reason to cry over this. Reality is that I don't know of a single project going into production using Harmony. " --Jacek Furmankiewicz "Google has single handedly turned around the disaster that was J2ME. Assuming they'll eventually sort out the patent mess (and given the stakes, they will) that removes from the equation all the partners that had very little to bring to the table when it comes to mobile Java. Meanwhile, Oracle and IBM need to demonstrate through actual technical innovation that they are still relevant in the Java world. Last time I checked, the enterprise Java world was dominated by things like Spring (under the Apache license) rather than any JCP efforts. Oracle bought an empty shell. Filing patent related lawsuits left and right is probably not going to be very helpful since that tends to scare away customers. So, I'm hoping that this will end pretty quickly. Once it does, all parties can get back to moving the agenda forward on the run-time, language, and APIs. There is a lot of stuff that needs to start happening there and if Oracle won't do it, others will do it for them. In a nutshell, that's why Google is shipping Harmony rather than CDC. I'm pretty sure Google would have preferred to stay in the Sun community a few years ago if only Sun was not being so unreasonable." --Jilles van Gurp "For me, the question is: what to we, as coder, expect from Java? I don't think I will ever use a self patched SDK/openSDK in any production; I even doubt I would ever work in a project which would like todo that. Oracle might be the bad boy here, but -man!- they know techology. I strongly believe, that the SDK will be less stagnant in performance/features and lots of those 10 year old problems in Bugzilla will finally be tackled. Sun let the "open" part of Java start smelling and people started to invest significant time in non-Java languages like Scala and new ways of dealing with partitioning of services aka OSGi containers. Since JVM 1.5 they were not really able to focus this community power to anything bigger then some lame syntactic sugar and a DOA flash clone. Harmony is a nice place to play around with an open JVM, but I think this job moves more over to the more general LLVM. And I don't think that I want to bet my (professional) future on the fact that Google has to step always in when the rest of the industry has just a bad haircut day. IBMs move is logical. Whatever Harmony is or was, the impact was already limited. You simply can't build such infrastructure without more people building it. One company alone wouldn't push Apache or Tomcat, and any serious openJDK shouldn't do either." --Igor Laera Let the conversation now continue.
the approval of the blueprint container specification by the osgi alliance enterprise expert group (eeg) inspired members of the eeg to start an open source project centered around implementing the blueprint spec and other technologies for osgi applications. in september the apache aries project was born in the apache incubator. the purpose of the apache aries incubator is to create a new community of people interested in building enterprise osgi technology geared toward the application programming model. for an introduction to the history and the purpose of the aries project, dzone interviewed ian robinson, a distinguished websphere engineer and a member of the osgi eeg. robinson is at the frontrunner for the apache aries project and has begun using its technology for ibm's websphere application server. dzone asked robinson about the factors inspired the aries project. robinson said, "from a standards direction, the work of the osgi alliance eeg was to define a set of specifications that would form part of an enterprise profile for osgi." he says the eeg has approved several specs for technologies that allow osgi applications to consume existing java ee technologies like jta, jpa, jndi, etc. "the purpose of the eeg was not to try and define competing specifications but to take what exists already in the java enterprise space and define how those technologies become consumable for applications running in an osgi framework," robinson said. robinson also observed some point efforts starting up inside existing apache projects that didn't have an enterprise osgi home to host them. one example was an implementation of the blueprint container spec, which started out inside apache geronimo , an open source java ee application server. robinson said that developing a blueprint implementation in geronimo made sense since the app server could use the it, but that didn't provide much visibility of the blueprint work outside of the geronimo project. robinson and his collaborators thought it would be a better idea to start a new incubator project who's primary focus was enterprise osgi, form a community around it, and then gather a set of osgi technologies in that new project so that other projects like geronimo, felix karaf, and servicemix could use that technology in their own runtime environments. apache aries is not an effort to build a new enterprise application server or a new application integration runtime. robinson says the purpose of the project is to build components like the blueprint container that can be used by those enterprise application servers. apache geronimo is currently working on consuming the aries blueprint container and apache felix karaf , which is the kernel of an enterprise integration runtime, is already consuming the aries blueprint container. in its three month existence, the apache aries incubator has already been successful in building a sizable community. including robinson, there are currently 43 committers distributed across a wide variety of companies. robinson says at the end of an incubation period, an incubator is considered a success and a top level project if it builds a vibrant community, and aries is well on its way with companies like red hat, progress, ibm, and sap represented. right now, no timeframe has been determined for when the aries project intends to graduate from incubation. robinson says the community will decide when they've done enough work to become a top level project. dzone asked robinson the most important question for any apache project: 'how did the project get its name?' robinson explains: "we started thinking in ibm about the aries project way back in early april when the blueprint work started in apache geronimo. i mentioned that geronimo is a consumer of blueprint, but not the obvious project to develop it - we thought back then that what we needed was a new incubator for the blueprint container and other enterprise osgi technologies. aries is the star sign for that time of the year - simple as that." hence the logo for apache aries is the ram. ibm's websphere application server v7 already uses some of the technology in the apache aries project for its open alpha , which helps deploy enterprise applications as osgi bundles. to get involved with the apache aries project, you can visit their "getting inolved" page.
I posed the question "Should There be Enterprise RIA Style Guidelines?" on JavaLobby in late 2008, and received some valuable feedback/discussion. Based upon that feedback, I'm replacing my question with the following challenge: "Create an application in JavaFX that exemplifies the appearance and behavior of a next-generation enterprise RIA application". Here are the rules to this JavaFXpert RIA Exemplar Challenge: 1) Each application must be created in JavaFX by a team consisting of two participants: A graphic designer, and an application developer. Both participants on the winning team will be recognized, and will share the prize. 2) The code must be offered as open source, in the form of the updated Berkeley Software Distribution License. The code for the winning entry will be added to the open source JFXtras project samples library. 3) The entries must be submitted in the form of a NetBeans project by 00:00 GMT on 10 January 2010. I'll provide an email address for submissions soon. The entries will be judged by one JavaFX developer (Jim Weaver), and one graphics designer (I'll let you know who this is as soon as I've chosen him/her). The criteria for judging will be how well we feel that the entry "exemplifies the appearance and behavior of a next-generation enterprise RIA application". 4) The winning entry will be announced on 20 January 2010 on the JavaFXpert.com blog. 5) The prize, which is a cash award of USD 2000 (USD 1000 for each one of the two participants), will be awarded after the winning team is announced. If you have any questions about this contest, please leave a comment on the associated JavaFXpert.com blog post. Thanks, and have fun with the contest! Jim Weaver JavaFXpert.com
Looking over the top 11 cloud platforms for Internet of Things (IoT), we highlight the importance of scalability, cost, and connectivity. Click here for more.
