to parse the XML data?
I havn't written any Ajax code, but my colleague Brian Paskin has been doing so. He ran into this problem and found out that Internet Explorer
In hopes that Brian's difficulties may save you some trouble, here are the details.
if (document.implementation && document.implementation.createDocument)
parser = new DOMParser();
xmlDoc = parser.parseFromString("John Johnson", "text/xml");
else if (window.ActiveXObject)
xmlDoc = new ActiveXObject("Microsoft.XMLDOM");
alert("Your browser can\'t handle this script");
So what is Ajax? How do you use it with Java and J2EE? developerWorks has an introduction, and there's a lot more going on.
The next question (for us) is:When is Ajax going to be built into Java?
The simple question may be "never" since Ajax at its heart is just servlets running little services that produce bits of XML data. However, having said that, it'd probably be handy to have some sort of Struts
Looks like some people are already getting a start. Sun has some Ajax Java Blueprints
that include a discussion, "Using JavaServer Faces Technology with AJAX
." Direct Web Remoting
(DWR) is a framework for "easy Ajax for Java." Apache Cocoon
can render Ajax Forms
. Apache MyFaces
has an Ajax DataTable
feature. There's an article, "Ajax using XMLHttpRequest and Struts
." The AjaxTags taglib
is a JSP taglib for Ajax functionality, and an apparently unrelated Sourceforge AjaxTags project
. AJAX-JSF Framework
aims to render any JSF
GUI using Ajax. So far, no one seems to be working on tooling.
Sun has announced two new Java products.JavaFX
is a technology and/or product family built on the JRE
. JavaFX Script
is for developing interactive Web sites. JavaFX Mobile
is for developing applications for mobile phones and PDAs.
Script appears to compete with Ajax
. Mobile appears to compete with J2ME
, but is more of a complete application for mobile devices.
Where you can learn more:
A dude from Dopplr has posted a presentation on how it works.
"Made of Messages
" by Matt Biddulph explains "It's important to think about serverside architecture as an asynchronous system." It then explains how the internals of Dopplr
work very asynchronously. Good stuff.
The part that really caught my attention is slides 6-8, where Matt recommends reading Enterprise Integration Patterns
in order to understand asynchronous programming and messaging better. Matt says, "This is a great book. Really. Ignore the name." (Apparently there's a problem with the name?)
So if you're busy doing everything all Ajax, Web 2.0, mash-up and what all--hey, it turns out that Enterprise Integration Patterns
is still a good book for you, even if you don't think of what you're doing as "enterprise" or "integration." Thanks, Matt. (And thanks to my friend Andy Piper
for letting me know about Matt's presentation.)
Technorati Tags: messaging, asynchronous, enterprise integration patterns || Digg it | Slashdot it | Post to del.icio.us |
IBM is making Web 2.0 secure with SMash (secure mashup).
is a very simple application that takes data and functionality from multiple sources and applications on the Web and combines them together as one source or display of information. The app is very simple because it delegates all of the real work to the existing apps on the Web; therefore mashups can be written very quickly, and when they stop working, you can just throw them away and write new ones. They're a very simple example of how SOA
can make behavior easy to reuse. Every mashup example I've ever heard of combines geographical data, such as the location of coffee cafes, with map data to display where the locations are.
The mashup model basically has no security, which limits its use to only public data (like the location of coffee shops). To make it more useful, it needs security, such as the ability to control who can access data, how it can be used and forwarded, where the data is coming from, keeping the data private, and so on.SMash
(secure mashup) is a technology from IBM to enable the development of mashups that are more secure. IBM is donating the technology to the OpenAjax Alliance
Where you can learn more:
Technorati Tags: smash, ajax, ibm || Digg it | Slashdot it | Post to del.icio.us |
Roland has a new Web 2.0 blog and Project Zero space.
They are the Web 2.0 and Middleware
blog and Project Zero
space, both on developerWorks. They discuss Web 2.0
and Project Zero
respectively. Roland's one of our top people in IBM Software Services for WebSphere
and knows lots about this stuff, so check it out.
Technorati Tags: web 2.0, ajax, project zero, developerWorks, ibm| Digg it | Slashdot it | Post to del.icio.us |
Want to attend Web 2.0 goes to work in Raleigh?Web 2.0 goes to work
, an IBM developerWorks Live! briefing
, will be in Raleigh, North Carolina, USA on Wednesday, September 12th, 2007. As usual, if you're interested in going, please register so they know there's sufficient demand.
Technorati Tags: web 2.0, ajax, research triangle, ibm
There are several feature packs available for WAS 6.1.
I've talked about the WebSphere Software Early Programs
. Those are for all WebSphere products, including stuff like our Java 6 SDK
, but only for feature packs that are in early release (alpha, beta, etc.). There are feature packs that aren't one of the programs any more because they're now GA (generally available).
For the list of all WAS
6.1 feature packs, both early programs and GA, see WebSphere Application Server Feature Packs
. It currently lists four of them:
The beauty of these feature packs is that they give you functionality that's newer than WAS 6.1 without having to wait for the next release of WAS. For example, WAS now has support for MTOM and XOP, which is newer than WAS 6.1 and normally otherwise wouldn't be available until the next release. Also, by making them available as betas/previews, you're able to try them out, report bugs, and request enhancements while there's still time for development to fix and improve them. Who knew IBM could be so responsive?
Technorati Tags: websphere application server, web services, service oriented architecture, service component architecture, ajax, enterprise java beans, ibm
SearchWebServices has an interview with Jerry Cuomo, WebSphere's CTO, on Project Zero.
I've talked about Project Zero
, and Jerry Cuomo's developerWorks interview
on Project Zero. Now he has one on SearchWebServices as well: "WebSphere CTO champions Web SOA on Project Zero
Technorati Tags: project zero, jerry cuomo, websphere, ibm
Jerry Cuomo talks about Project Zero.
Yesterday I talked about Project Zero
, IBM's platform for developing and deploying Web 2.0
apps. Now, in "developerWorks Interviews: Jerry Cuomo on Project Zero
," a developerWorks podcast
, IBM Fellow (the most senior technical level in IBM) and CTO of the whole WebSphere brand Jerry Cuomo talks about the project.
Jerry talks about Zero being about "radical simplification," the idea of an environment that makes programming as simple as possible, yet also powerful enough for writing real apps. Zero really is a new project from the ground up, separate from the other WebSphere products. Rather than try to simplify existing products--although efforts are always continuing to try to make our products easier to use--Zero starts over with the goal of trying to make things as simple as possibe, yet still powerful and useful.
Want to see how we're doing? Check it out at ProjectZero.org
and let us know how we can make it better and more useful for the work you do.[Read More
IBM has launched a new incubator project: Project Zero.Project Zero
) is producing a set of tooling and runtimes to produce Web applications and Web service providers using agile development techniques. Its programming model leverages Web 2.0 technologies: REST, ATOM, JSON, XML, Ajax, etc. The resulting apps will tend to be not so much enterprise apps per se, but mashups and that sort of thing; apps that are quickly produced, perhaps with limited usage and lifetimes.
It endeavors to be low overhead (practically zero!), with a simple programming model and lightweight runtime that make development and deployment quick and easy. IBM (and other middleware vendors, J2EE/Java EE and .NET in general, etc.) has gotten some criticism that its products are too heavyweight, too complex, don't support agile development, etc.; to the extent this may be true, Project Zero supports development at the opposite end of the spectrum.
A lot of initial criticism has focused on the assumption that Project Zero is or should be open source, which it is not. Project Zero intends to develop and sell commercial products, and so does not want to just give the source code away. But in a new model for IBM (and perhaps the industry), Project Zero is following what it calls a Community Driven Commercial Development process. While this process doesn't make the source code available, it does make the proto-products available sooner so perspective customers can try it out and offer feedback. The project hopes to use this feedback to be able to build the products customers want more quickly and accurately than IBM (and other vendors) have been able to do so in the past. The alternative to this approach is a new version of WAS
that takes a year or two to produce and that customers don't see until it's finished and too late for changes.
I see an opportunity for synergy between the traditional IBM software middleware products and the products that will come from Project Zero. Products like WAS
and Process Server
will still be great for hosting service providers that give access to enterprise resources in a reliable, scalable, and secure environment. Then Project Zero products can be used to quickly and easily produce service coordinator
apps that mash up the services. This is Kent Beck's vision of abstractors and elaborators
For more commentary on Project Zero, see:
WebSphere Application Server now has support for Ajax.Ajax for IBM WebSphere Platform
is a beta that is part of the WebSphere Software Early Programs
. I've talked about Ajax and Java
in the past; now they're easier to use together in WAS.[Read More
I've put together a short list of resources for learning about using Ajax and REST together.
I talked about Ajax and REST in REST vs. SOAP/WSDL (pt 2)
. Since then, I've added a short list of Ajax and REST articles to REST vs. SOAP-WSDL
(on my wiki
). The first two articles are by our own Bill Higgins