IBM buys Gluecode
karvind writes "After acquisition of Ascential, Big Blue has bought the application management firm Gluecode. From the article: IBM plans to allow its customers to download Gluecode software, develop their own application server software, and begin using it -- all at no cost. IBM also said it will become an active contributor to the Apache Geronimo open source project and will expand the existing community of developers."
I got diabetes from too much glucode.
Next up from IBM -- they mail you sand, which you can use to develop advanced microprocessors and chipsets, and begin using them, all at no cost!
Followed by their patented 4k GIF reading "WORK FASTER," intended for use to develop your own source code control system, and begin using it -- all at no cost!
For the coup de grace, an online whiteboard, allowing you to jot arbitrary equations and thus evewntually develop amazing new branches of quantum physics, revolutionizing modern thought. All for just two percent of royalties (plus naming rights)!
Thanks, IBM!
Editors: articles are increasingly lacking context. Please editorialize a bit more.
The company's web site and Product overview for Gluecode SE would help next time.
2bits.com, Inc: Drupal, WordPress, and LAMP performance tuning.
This is part of their overall plan to return to profitability: Give stuff away and make it up on volume.
For all of those who didn't know, it's a J2EE server.
Apache Geronimo Homepage
I knew of [apache jakarta] tomcat, but not geronimo. Sorry, I guess I've been living under a comfy rock for too long.
///<sig
I know. We should all just use JBoss and ignore any other attempt to make an open source Java application server. Competition is a terrible thing to have in any market, and should be discouraged at every opportunity.
Charles
The more I learn about the Internet, the more amazed I am that it works at all.
Of course they would support Apache Geronimo. It's in IBM's best financial interest to protect WebSphere, and protecting WebSphere means not allowing JBoss to become the de facto open-source AppServer standard. At the same time time, they want to appear friendly to open-source to attract developers.
So, they support Apache Geronimo to compete with JBoss.
IBM has campaining for open source J2SE.
When Classpath is turning almost compliant, Apache tries to help it's accepance by requesting
them to move the code to the Apache Licence.
The man behind it is a VP at Gluecode.
IBM buys Gluecode.
Also there was a rumor on jpackage about an undisclose three letter company that
was getting them to test a free j2se impementation.
IBM plans to allow its customers to download Gluecode software, develop their own application server software, and begin using it -- all at no cost.
Does that mean there's a lot of cutting and pasting involved?
Larry Wall sold Perl?!?!
Yup... they're bugs b/c they're documented to work one way, and actually work another. However the class-loading heirachy is very clear (until you start deploying applications that do their own class-loading as well ala Sun Portal Server).
Any application server that, when it doesn't find the class it's looking for in your deployed application, goes looking for class files in other deployed applications (& yes, I know you can turn this behaviour off, but recall experiencing other problems when I did).
i think the specs are farily clear regarding the application container provider's responsibilities regarding classloaders.
Actually, the spec is very loose when it comes to class loading. It does state that applications shouldn't assume that classes will be loaded by a different classloader, but doesn't state that the servers shouldn't work this way.
By convention amongst the major vendors, it seems you get a heirachy of classloaders, where your application can only load classes deployed with itself or its ancestors. JBoss by comparison flattens it out, so you can load things from other applications.
Clear specification, rather than phrases like "should not assume that each component is loaded in a separate class loader and has a separate namespace" and "Typically this will require the use of a separate class loader for each application.", where the classloading behaviour/heirachy is mandated would be preferable in my books. & while I'm ranting, so would getting rid of app server specific deployment descriptors.
if you read the jboss docs/examples, you'll see that there's a simple ant execution to setup multiple server instances without port conflicts.
I'm obviously running a different version to you, as I've not seen this in the docs. Instead, I've found that I have to enable the bindmanager (which isn't used by default in 3.2.x), then grep the rest of the server structure for all the ports it could possibly be using (hasingleton comes to mind as one offender). This is as per the instructions on the jboss.org website. Possibly it's changed in the latest versions. Unfortunately my corp clients don't like rapid upgrade cycles.