Enterprise JavaBeans (EJB) components are discreet units of functionality in enterprise software terms, so that you can think of it as encapsulating a certain amount of lines of code to achieve a specific outcome. Components have long been something of a 'holy grail' in software coding, as it could be re-usable as well as sold as stand-alone function. EJBs came out in the late 1990s with that same promise and were mildly successful in its first generation.

Read more ...

The case is simple, and it has a history: build functional applications that are cross-platform, and revive the model of Java to be write-once-run across multiple platforms. This was done, in some form, by Theory Center before they were acquired by BEA in 1999, and it allowed WebLogic to take the early lead, that ultimately led to their sizable cash-out, in the form of the Oracle acquisition. Nothing made IT managers happier than to see something actually working on top of these Internet operating systems, that were to be known as application servers.

Read more ...

If its not going to be used to sell hardware, then it should be given its own life, outside of Oracle, its wasted value, just to be specification Reference Implementations, that is comical, its industry-grade, and can stand on its own, it should be set free. MySQL, SSO, ESB, JEE, even NetBeans could sustain a whole new company, and these are redundant assets within the parent company's offering, they are not investment worthy, so why not let someone else do something with it.

Read more ...

Its predecessors in Netscape Application Server and iPlanet Application Server did not work, and so it took the re-write of the Reference Implementation of the Sun ONE Application Server to provide the roadmap that would lead to a stable app server platform, that could be open sourced and turned in to Glassfish. Now, it is being systemically dismantled in the hands of Oracle as all the real money is in the big-ticket product lines of WebLogic, Oracle DB, and PeopleSoft ERP, and no one seems to notice.

Read more ...

i am just trying to reconcile how the better product receives 1/10th the resources, i mean WebLogic was dying before the acquisition, JBoss had it beat, and then Oracle picks it up for a song, somewhat cheaper than they got Sun, in relative terms, and turns it in to the base of Fusion, and ERP, and invests all this money in to it to become the enterprise platform, all while Glassfish was getting good, and ready to take-down JBoss, or at least take on Spring Source, and then the acquisition, and all funding dried up, all OSS community participation went away, and now its just a small division i

Read more ...

The really impressive thing about the Glassfish 3.1 release is the position it puts the product-line in to deliver on a whole new open platform for Oracle to pursue over-time non-established customer bases, in all target verticals, customers or in many cases, enterprises, that have not committed their entire infrastructure to Oracle or SAP, or IBM for that matter.

Read more ...

i have been advocating over the issue of Glassfish, for Google to become a thriving web company, needs to get in the enterprise space with something more than AppEngine, and the best place to do for Java what Google has done for mobile Android, is on Enterprise Java, settle with Oracle, start paying them a royalty, which is standard practice, and get the assets of the acquired Sun middleware quotient in-house, so that Google can use the ESB, IDE, App Server, and MySQL to build out a yearly release of software that can be utilized within businesses, that want to stay away from united Microsoft

Read more ...

The Glassfish team has made some rather strange tweets lately, as if Google does not have a point with Oracle being heavy-handed, i mean where would Java be without Android?, it would not be relevant, so a deal is needed to assist with the transformation some might say a revolution of approaches even it seems so unlikely to get Glassfish under Google, and let Oracle gain from Google's knowledge on the database of cloud datacenters better than any other vendor out there, Oracle would greatly benefit from having Google on board, and trusting them to take the simple task force of upending Microso

Read more ...

Is there any doubt now that Google has to do a deal with Oracle, to settle the Android law-suit, pay-up for Java, and get Glassfish in return?

My home for most things Google Glassfish:

https://sites.google.com/site/douglasdooleyglassfish/

Can't slow down Android adoption through FUD on legal matters, have to settle immediately, and might as well get Glassfish in return....

Even as I advocate, in relative terms that the Oracle stewardship of Glassfish will be sub-par, and under-resourced, the team treks on, and does amazing things like come out with Cluster in the Admin Console in 3.1 M3, i saw the demo on the video capture of someone starting and destroying a cluster, in about six minutes, and it all looked so easy, and powerful, and it got me thinking that this must be what its like to run Google's datacenter....

Read more ...

Things have changed somewhat since the announcement at I/O of a Spring-powered Java run-time in the App Engine, or was it just developer tools, I couldn't be so clear, but needless to say, Spring's partnership with Google, in the cloud, is significant, for so many reasons....

Read more ...

There is a growing appearance that Microsoft is vulnerable, and much of that success lies on the back of Linux, as it has dislodged Windows and, by extension somewhat, Solaris, in the enterprise, so it is incumbent on Red Hat to find a safe home, and there is no safer home than IBM. Linux on the server, as well as the mobile handset is solidified by the appearance and maintenance of stability. Even Google uses it.

Read more ...

Although I am in the process of advocating for new ownership, I am not going to overlook the tremendous work that has been done by the Glassfish team of product managers and engineers, even though it seems like they ditched product marketing, in favor of developer outreach, they achieved incredible penetration in a saturated marketplace, that most had assumed had solidified around WebSphere, WebLogic, JBoss, and SpringSource. But along came Glassfish, and it upended the economics, as well as the delivery cycle of the Java EE specification, to create a viable contender.

Read more ...

If the entire Glassfish eco-system does come to Google, as I have written about for the past two to three months, the continuation of the clustering work on v. 3.1 is priority one, as the Oracle engineers are doing via Sun management, but that does not say that strong consideration to countering BizTalk does not get addressed in the form of extending JBI, and making the Glassfish ESB, the de-facto standard among integration platforms.

Read more ...

I am in the middle of a job search, and have somewhat come to the conclusion that the only place of employment I could do, outside of working with clients as an independent contractor with Astro Solutions, is to work for Google, as I am committed to seeing their vision of the web, take hold.

Read more ...