TIBCO was one of the first companies to help out Ajaxian, and I remember hanging out with Dylan Scheiman, Kevin Hakman, and Scott Fingerhut to chat Ajax.
Dylan has talked about how the Dojo foundation was happy to bring in a great tool so people don’t have to reinvent the wheel. Over time, we should see nice integration within and outside of Dojo the toolkit itself.
When we posted the last podcast on Aptana Jaxer, someone commented on the fact that Kevin Hakman was there, and “Doesn’t Kevin Hakman work for Tibco? What does he have to do with Aptana?”.
We are excited to announce that Kevin Hakman has joined Aptana to head up marketing and developer community programs. Kevin is a recognized leader in the Ajax community. Long before the term “Ajax” was coined, Kevin was pioneering single page web application concepts via the company he co-founded, General Interface Corp., one of the first enterprise Ajax libraries and visual development tools companies. General Interface Corp. went on to be acquired by TIBCO Software in 2004 as a compliment the company’s service-oriented architecture (SOA) products. Today TIBCO General Interface is used by many Fortune-scale companies for rapid Web application development and deployment atop their XML and SOAP data sources.
In addition to his historic role on the steering committee of the OpenAjax Alliance, Kevin currently chairs the organization’s integrated development environment working group. The OpenAjax Alliance IDE Working Group which includes Adobe, Aptana, the Eclipse Foundation, IBM, Microsoft, Sun, TIBCO and others is now close to delivering a draft specification for a uniform way to describe Ajax libraries and controls and thus streamline the ability to use Ajax libraries within your development tools of choice. Kevin is a frequent speaker at Ajax industry events and is an author to many published articles on Ajax in the enterprise.
I asked Kevin a couple of questions about his move, comparisons between the companies, and the industry in general.
What similarities / differences do you see between pioneering heavy JavaScript on the client w/ GI and JavaScript on the server with Aptana
GI and Aptana’s primary application models are different to serve different purposes similar to the way that Java has multiple presentation tier architectures for differents kinds of apps: Swing, SWT, AWT for application GUIs and JSP, JSF for generating web pages. With GI, the concept in 2001 when we deployed some of the first “Ajax” apps pretty much evolved from a need to migrate software-style GUIs to the Web and a technical approach summarized as “we like Java Swing, but not the JRE dependency, so let’s do something Swing-like in JavaScript with a JavaScript VM of sorts and get data as XML / SOAP via the XML HTTP Request Object — an oh yeah, make it Visual Basic-like easy to visually develop too”. That led to what I call a “Client-Services” architecture where you have a full fledged JavaScript application running in a web page talking to back-end data services plus the WYSIWYG rapid development tools for which GI has been recognized as best in class in enterprise IT journals. With GI, you never really interact with the HTML page or its DOM. Instead there’s a higher abstraction of application concepts and a model of the GUI, called “dual DOM” by some. The result is that the JavaScript applications are deployed into a webpage more like an applet, (except it’s all in the same JavaScript memory space and there’s no JRE dependency of course). This “Client-Services” architecture has been a great fit for many enterprises pursuing service-oriented architecture strategies.
Aptana Studio is clearly among the best-in class for the predominant model of Ajax development called “single DOM” where you work directly in the HTML DOM to describe elements within a page, then apply Ajax and CSS concepts to bring that page to life with interactive features. Aptana Studio meets the needs of Ajax developers working in this model extremely well. Whereas tools for web page development have historically focused on layout, image placement, styling, and JavaScript for roll-over and simple navigational assists, Aptana saw that with Ajax and the popularity of all the single-DOM model Ajax libraries like dojo, Ext, prototype, MooTools, and jQuery, the page was becoming increasingly programmatic in the client and needed tooling optimized for the programmatic page.
What excites you about Aptana
Aptana Jaxer is a very cool concept for all the JavaScript developers out there because they can now go boldly where no JavaScript developer has gone before–to the server-side. Sure Netscape had LiveWire back in the day, but remember there was no real DOM, no real CSS and certainly no XHR object at that time. Aptana Jaxer’s genius is that is takes the same Mozilla engine we know and love in the browser, and puts it inside a server along with a bunch of handy Jaxer methods and properties to do server-side things like interact with databases, web services, session concepts, sockets and more. I personally love the ability to write a script that runs on the server, but call it from the client as if it were running on the client. In this case Jaxer handles all the sync or async communications for you transparently, and soon will provide end-to-end debug capabilities as well. We’re also now working with Joe Walker of the DWR project to extend this kind of capability to remote Java objects as well through Jaxer. We’re also investigating how to best interoperate with Microsoft’s .NET platform.
To some, JavaScript is not a preferred language and that’s where things like GWT and DWR come in real handy. At the same time there’s millions of developers who like the ease and mutability of JavaScript. Aptana Studio, with its JavaScript debug and type inference capabilities, and Aptana Jaxer with its server-side power enable all JavaScript developers to do much more, more quickly in the language we love to work with — JavaScript! Thinking beyond the solid JavaScript programming tools in Aptana Studio today, things like visual WYSIWYG GUI composition and data-binding are clearly natural extensions. Not many people know that the Aptana team contributed to much of the Eclipse Monkey code which enables JavaScript to run within and communicate with Eclipse’s APIs. This means that Aptana is extraordinarily well positioned to execute a first-class solution for WYSIWYG editing — and further streamline the creation of Ajax web pages and full-featured Ajax applications.
Now you have been around JavaScript for awhile, what are you likes and dislikes, and do you have any thoughts on JavaScript 2?
Having been part of Ajax projects where we had single HTML pages running for 9 hours sessions with over 180 separate application modules you could load/unload during that time (and that was in 2001), the GI core team (Luke Birdeau, Michel Peachey, Jessee Costello Good, and myself) has had loads of experience in what it means to make highly scalable, full featured apps in JavaScript. Much of what we had to invent and implement in JS1.5 for the TIBCO GI Framework, things like object orientation for example and better memory management, is on the horizon for future releases of JavaScript. The primary pain of JS though, until recently, has been lack of great debugging, type inference, and code assist capabilities. What few people realize about Aptana Studio is that it not only code assists on the Ajax libraries you’ve loaded, it assist with the Ajax objects, classes, packages, functions and properties that you create too — again a concept borrowed from the Java community, but with less programmatic overhead since its JavaScript.
gi.js is a library to help integrate DWR with TIBCO GI. It is due for official release with DWR 3.0, however it is reasonably stable now, and will probably only undergo performance tweaking before the official 3.0 release.
Since it doesn't have any dependencies on DWR, it can be used without waiting for an official release. The best place to download it is either via a milestone release of DWR (see the java.net download page), or through the FishEye view of the DWR CVS repository. See this direct link to gi.js.
The article walks through a simple example integrating with a fake social network backend:
Luke Birdeau has remixed Craigslist to produce a desktop-esque Ajax application view on the data that adds features such as being able to save your favorites, add notes to them, and even use the app offline (e.g. take your laptop on the road to go see the stuff for sale of meet that blind date). The app combines aspects of 3 libraries – TIBCO GI 3.5 for the interface, plus Dojo (for offline) and Google Maps.
To get started you first pick a locale, then a category, then do a search. You can also add multiple regions and categories too.
Here is a quick demonstration of the app in action:
TIBCO has created an Ajax Challenge where the goal is to build the world's largest mashup over the summer using TIBCO GI.
Your components must:
Must use General Interfaceâ„¢ v3.4.1, an open source Ajax toolkit from TIBCO with over 100 Ajax components and a suite of visual tools.
You may also include other Ajax components and libraries if you wish.
Must be created as a Project using the General Interface visual tools.
Give your project a unique name and set the namespace of the TIBCO General Interface project you create to a unique name. We suggest using the reverse domain name convention.
Must use TIBCO PageBus, an open source Ajax message bus, the core of which was recently contributed to the OpenAjax Alliance.
Must subscribe to at least one of the three messages below
May publish to at least one of the three messages below
Ben and I will be helping out as judges, so we are interested to see what creative ideas come in.
When a large company migrates to open source, it takes time to setup the infrastructure for the project. TIBCO GI 3.4 has been released, and although there are many new features, the most important update is arguably the new home for the product.
The open source home page features the full downloadable source online (SVN and SVN Web), an online bug tracking system (JIRA), and build tools to make it far easier for you to extend GI and create optimized GI libraries for your Ajax application projects.
To further support rapid Ajax application development cycles in the enterprise, TIBCO has released TIBCO General Interface Test Automation Kit, a free, open source kit optimized for functional, unit and regression testing of solutions built with its TIBCO General Interface Ajax toolkit. The testing suite extends the popular Selenium TestRunner open source project with additional libraries and features that streamline the testing cycles for Ajax applications, components, and portlets.
It is a very smart move to take Selenium and add features on top of that, instead of starting from scratch.
In this article you will learn how to create a new Ajax RIA front end to an existing Apache Struts2 .jsp application using TIBCO General Interface (GI), an open source Ajax toolkit with a MVC architecture similar to that of Java Swing. GI is optimized for creating business productivity applications and communicating with XML, SOAP, JSON and other types of services in a SOA.
Specifically we’ll extend the Struts2 CRUD (create, retrieve, update, delete) sample that comes with its installation to expose XML data services optimized for GI interoperation and create the Ajax application that connects the end user with those services though a rich graphical user interface. The intent behind this approach is to demonstrate how you can make incremental changes to existing applications rather than having to rewrite from scratch.
Xignite is a public financial web services application that uses TIBCO GI at its core.
Due to its history, many of the TIBCO GI deployments are behind corporate firewalls, but Xignite is showcasing its financial web services with a great TIBCO GI example. The source code for the Ajax app is availableand it shows what it means to build a full-fledged Ajax application (as opposed to enrich HTML pages with Ajax features).
A side effect feature is also interesting in its own right. You will notice the smart tour guide that can take you for a ride, or watch what you are doing and give you some information. This could be a nice learning tool for your application, as long as you do go as far as Clippy.
Joe Walker has discussed the progress of the OpenAjax Hub. He has participated in a demo of using the OpenAjax Hub with DWR or Lightstreamer. TIBCO GI is the UI side, and it plugs into either backends with no code changes.
With a traditional request/response model, DWR (and Lightstreamer) would be calling GI routines to update. With the pub/sub model the distinction between client and server is gone because the UI publishes things it's interested in back to the hub. There's no reason the UI has to be GI even: any UI that groks the OpenAjax hub can play. We could even have several UI components listening to the same messages on one page.
The OpenAjax Hub is getting close to a 1.0 release, and I'm hoping that DWR will have a server-side version of the OpenAjax hub soon after. This would allow you to transparently co-ordinate remote hubs, and even allow publishing of messages from one browser to another.
I've put the DWR version live so anyone can have a play. It's not exciting, but you can see it in action. Just click on an "Industry Sector" to see messages published to that sector. See the DWR/OpenAjax/GI demo. I hope to move where it is hosted soon, and this is definitely something of a test, so don't be surprised if you get a 404. I hope we can get a demo of the Lightstreamer version live soon too.
TIBCO GI recently had a webinar on Ajax portlets where they discuss various topics revolving around portals, SOA, and Ajax. The content was recorded and is now available for your perusal.
H&R Block Sr. Systems Architect, Dan Cahoon, shares how H&R Block delivered SOA-connected Ajax portlets to its more than 12,000 branch offices to deliver composite workspaces streamlining the staffing operations for the nation's largest seasonal employer. Dan shares his learning from the project and discusses the successful pattern they are reusing to get more solutions to market quickly.
Howard Weingram, Sr. Architect for TIBCO PortalBuilder, shows you how to deploy rich Ajax portlets to JSR-168 and other types of portlet containers and more...
TIBCO has announced that they are doing to sponsor work by the DWR lead (Joe Walker) to integrate DWR and TIBCO GI.
This is good news for both parties:
TIBCO GI users will have a new way to integrate with Java web applications
DWR: The integration work between DWR and TIBCO GI will probably help integrate with other frameworks. Changes made to DWR to work with GI will be exposed for other work. For example, the DWR team will look at automating the currently-hand written server-side version of Scriptaculous Effects.
JBI users may get some tighter integration too, making your life easier. We are excited to see what comes of this.
More details (from the Press Releases)
TIBCO will work with DWR founder, Joe Walker, to provide ready-made integration points between DWR and TIBCO General Interface™, TIBCO’s Ajax Rich Internet Application toolkit for creating rich graphical GUIs in a browser. Additionally, the collaboration will seek to extend DWR so that it can function as a Java Business Integration (JBI) standard service engine and be deployed on TIBCO ActiveMatrix™, the industry’s first service virtualization platform. The complementary components of DWR and General Interface™ will ultimately enable businesses to expand their uses of message and event-based service-oriented architectures.
“We are excited to be working with TIBCO to push adoption of DWR further into the enterprise,†said Joe Walker, DWR founder. “DWR has been a leading Ajax framework for some time but working with TIBCO will help take DWR further into the realm of full Ajax Rich Internet Applications being deployed alongside message and event-driven service platforms.â€
With substantial application modernization efforts underway and a continued trend towards SOA in business, the combined Ajax libraries of General Interface and DWR will provide capabilities that deliver rich user features such as editable grids, real-time events and notifications, and streaming data. By running on Internet technology rather than operating or runtime environment dependent technologies, businesses will experience much lower costs of ownership.
“DWR is a rapid way for Java developers to expose Java objects as simple Ajax services without the need for additional configuration or transformation. We have many customers already using DWR with the General Interface Ajax library,†said Kevin Hakman, director product marketing, TIBCO General Interface. “With DWR’s reverse Ajax capability, messages and events can be pushed from the server to the browser so that Web applications can also have real-time notification and streaming data features.â€
Dion and I have long been impressed with the nifty, robust and very ajaxian UI magic that TIBCO brought to the Web with their GI tool... but we weren't so excited about the nifty, robust price tag nor it being IE-only. As we covered a while back, TIBCO recently open-sourced their product -- and not with one of those "pointless-entry-level-version free, useful version spendy" schemes, either. Given this news, and the recent port to Firefox, we thought it was high time to sit down with the TIBCO guys once again.
TIBCO General Interface 3.2 was released earlier this month under the rather liberal BSD open source license.
The intent behind that release was to enable developers to use and deploy the product at no cost under the terms of the BSD license.
Now TIBCO has taken the next step, bundling the fully commented and unobfuscated JavaScript source with the product download so that it can serve as a reference to those that really want to get in under the hood and see what makes GI tick.
TIBCO also states on the GI download page that implementing a full open source eco-system will occur in phases.
Phase 1: Source code is provided with the download for use as a reference. The product and its source are free to use under a BSD license; Full support, warranty, and more is offered under separate TIBCO agreements.
Phase 2: Source compilation, compression and obfuscation tools will be provided so that you can generate optimized runtime code for multiple platforms from your modifications to the source.
Phase 3: Community contributions under separate contributor agreements for those that want to contribute their good stuff.
Developers wanting to create modifications and extensions to the GI libraries can now do so more easily with access to the fully commented source. However close inspection of the source will reveal that the raw JavaScript source can also be run through a “pre-compiler†that compresses, obfuscates, and generates separate runtimes for each of the supported browsers—and that pre-compiler will not be out until Phase 2 of the open source implementation process. In effect the source code has forks in it for various browser types, but the pre-compiler generates optimized code for a single browser, thus increasing performance and shrinking the footprint while packing in lots of capabilities.
With over 100 Ajax components, it’s pretty amazing all the features the GI team can get into such a small footprint. Taking a peek through the source reveals some of the ways the GI team whose been in the Ajax business for 5 years now, has architected the product to do so much with so little.
You can download GI and its fully-commented JavaScript source @ developer.tibco.com.
