This week's giveaway is in the Java/Jakarta EE forum. We're giving away four copies of Java EE 8 High Performance and have Romain Manni-Bucau on-line! See java is with languages. I do think it will be a big part in the future of the internet, and it's already playing a big part. XML is pretty much portable already, that is why it can be used by a variety of programming languages. [ June 30, 2004: Message edited by: Angel Dobbs-Sciortino ]
Java is a platform independent programming language. XML is a platform neutral data. They're 2 different entity. Pretty much like an apple and orange.
XML had already found its way in many applications & part of the computing world. There're XML database around (Software AG), WebLogic Server uses XML as its config file, Web Services uses XML too, etc...
XML is the present and should continue to its future
Of course, XML is widely used everywhere at the present and it will be used in the future for long... Not only in the enterprise-sized application, but also in the tiny J2ME application, XML is used mostly as data storage, data delivery and so on...
Meanwhile, Java is everywhere and Java make use of XML in most of the Java applications for portability and interoperability...
So I do believe that the combination of Java and XML will be in the golden age in the future... Of course, the present is the golden age for them as well...
Co-author of SCMAD Exam Guide, Author of JMADPlus SCJP1.2, CCNA, SCWCD1.4, SCBCD1.3, SCMAD1.0, SCJA1.0, SCJP6.0
I think XML needs to be embraced by the data base community before it can take the place that many people think it should have. When more and more databases provide easy to use tools with XML, then it might take off.
However, I also think that the days of one "super language" or even "super data-manipulation tool" like XML, are over. COBOL was the last of those big-time stars.
IMO XML is way overused and abused for things it's completely wrong for. Many people and companies (up to and especially including multinationals) are using XML for the sake of using XML, not because it's relevant to their problem domain or the proper solution for the problem at hand.
We're all guilty of it to some extent, wanting to use the latest tech just to see what it can do, but most of us then decide to use something older if it turns out that the new tech isn't the best solution. With XML it appears like people forget that mantra and will bend over backwards in order to produce a solution using XML no matter what it takes.
As an example, I used to work for a major international bank. Mid 1999 we were told by the board (what the hell has the board to do with IT implementation strategy???) that ALL projects from that point on MUST use XML and existing projects under development were to be reworked to use XML.
XML databases are a prime example. Being able to store XML documents in a database is all good and well, but why the heck make a fuss about it? We stored XML in Sybase and Oracle long before anyone had ever heard of XML databases...
Java provides the big advantage of being platform independent and so excellent for the Internet where there are various PCs running different platforms.
On the other hand XML is excellent to markup ANY DATA in a format-independent way. Example: If one entity needs to send data to another entity, when these entities use different Database Schemas, the entity receiving the data will have difficulties in "understanding" the data. By formatting the data in XML and sent it in a defined format, this uniformity of data allows any entity to understand it and use the received data.
XML is extremely important in Web Services where data is open for various entities (who don't have to worry about the database they use thanks to XML). The data in fact will be made available in XML format.
Java and XML are slowly taking hold as industry is learning more on how XML works and how to use it within the industry. Remember that corporations within an industry must settle on a standard XML tag set otherwise XML is of little use. It takes time for corporations to agree, but once they do then the whole infrastruture of a company moves to XML. This is the case in the publishing industry. As for web services, this is very slow getting started espeically now when companies are concerned about security. My impression is that web services is more difficult for non-techies in a company to understand than XML. Therefore, they're not likely to be in a rush to approve money for those projects yet. I cover in detail how to implement XML and web services in my J2EE, The Complete Reference book.
We don't have time for this. We've gotta save the moon! Or check this out: