January 2002 Archives

Steve Anglin

AddThis Social Bookmark Button

Related link: http://www.theserverside.com/resources/article.jsp?l=SunInterview

TheServerSide.com’s Floyd Marinescu asks, “What is Sun’s point of view in the debate over whether J2EE licensing restricts open source J2EE products?” Find out about Sun’s reply to this question as excerpted from this TheServerSide.com interview on J2EE with Sun’s Bill Shannon, a Sun Distinguished Engineer and Spec Lead for the Java 2 Platform, Enterprise Edition, and Karen Tegan, Director of J2EE Compatibility and Platform Services for Sun Microsystems.

Marinescu: What is Sun’s point of view in the debate over whether J2EE licensing restricts open source J2EE products?

Shannon: Sun participates in open source because it helps spark innovation, improve software quality, and fosters
community. The source code for the J2EE reference implementation is made available publicly as part of the Sun
Community Source Licensing program.

Sun supports open source developers because their efforts are consistent with Sun’s own computing vision which uses open
standards and non-proprietary interfaces. Sun’s goal is to make our software as open as possible while ensuring portability
and WORA.

Tegan: At the same time, having a strong brand and compatibility standards are important to the development of a robust
market for J2EE platform products, tools, and components. The J2EE Compatible brand has achieved significant momentum
over the past two years, and we want to make sure that any open source efforts don’t impact the viability of that
effort.

What do you think?

Steve Anglin

AddThis Social Bookmark Button

Related link: http://java.sun.com/webservices/webservicespack.html

Sun has released the Java Web Services Developer Pack (WSDP) EA1 to provide access to early versions of the standard Java APIs for XML processing and Web Services being developed through the JCP process. The new release includes early releases of base XML technology (JAXP 1.2, including XML schema support), SOAP based RPC (JAX-RPC), SOAP-based messaging (JAXM), and registry client support (JAXR). It really should’ve been called JAWS (Java API for Web Services), though. Oh well, it’s Sun’s call.

What do you think: Java WSDP or JAWS?

Marc Hedlund

AddThis Social Bookmark Button

Related link: http://www.washingtonpost.com/wp-srv/national/longterm/watergate/deept.htm

This past summer I spent some time “between jobs,” and my mind went on vacation. I recently found something I wrote during that time, which today seems amusing, archaeologically if nothing else. It was composed as a letter to some friends; I chickened out and never sent it because I suspected even then that it was ridiculous. But what is a Weblog if not a relentless form of self-abuse? So here, for your amusement, is (some of) What I Did During My Summer Vacation.



I recently read Leonard Garment’s In Search of Deep Throat: The
Greatest Political Mystery of Our Time
. Garment was in
the Nixon administration Counsel’s Office, and uses his personal
knowledge of many of the Deep Throat candidates to investigate the
mystery of the leaker’s true identity.

Garment’s book is horrible. Sure, he’s not a bad writer and relates
some interesting anecdotes. As a work of investigation, however, the
book is quite simply the most inept piece of nonfiction I can ever
remember reading. Nearly all of the people he eliminates from
consideration could not be Deep Throat, he says, because they are “not
the type” to be creeping around in garages after midnight. He
eliminates the entirety of the FBI because Deep Throat’s quotes “don’t
sound like” an FBI insider to him. One candidate leaves the list when
Garment’s wife, meeting the candidate’s wife, whispers to her husband,
“that is not Deep Throat’s wife!” If there is anything at all
we should have learned from Watergate, isn’t it that a person twice
elected President was nonetheless
commiting base criminal acts in office, and that we should never judge
solely by appearances?

Reading the book gave me a “personal itch” analogous to Eric Raymond’s
first prerequisite for an open source project. I didn’t like the book
– I hated it. I wanted to read a better book on the topic, and none
existed. I started contemplating a database of candidates crossed
with characteristics, flights to D.C. to grill Bob Woodward on the
Deep Throat clues he’s dropped over the years, days spent in the
Washington Post archives — and then I remembered I was unemployed.

Some time later, I was thinking about the case of Kaycee Nicole (see
this page for background). The Kaycee
story, where a woman used Web sites and email to fake the illness and
eventual death of a supposed daughter, brings up many interesting
questions for me. How can you know what is true on the Web? How do
the interactions people have on the Web fall through to “Real Life”?
What brings people together on the Web, and what can they accomplish
when they get together? One interesting part of the Kaycee Nicole
story was that her story was discovered to be untrue by a
collaboration of strangers, using the Web to investigate and
coordinate their understanding of the story. This strikes me as
something like an open source journalism project — rather than
reading a printed story (buying a software package), the story is
created by Web users (developers) who both contribute to and consume
the story (software), and make their results available for free on the
Web.

Where I’m headed with this is probably obvious — I’d like to apply
the Kaycee Nicole investigation model to the question of Deep Throat’s
identity. Ben Bradlee, editor of The Washington Post and supposedly one of the
four people who knows Deep Throat’s identity, has said, “I have always
thought it should be possible to identify Deep Throat simply by
entering all the information about him in All the President’s Men
into a computer, and then entering as much as possible about all the
various suspects.” His nod to artificial intelligence aside, this
seems like a pretty good idea to me. Bob Woodward has said Deep
Throat has been publicly identified and has denied being Deep Throat.
Figure out when Woodward first said that, and then figure out who
denied a Deep Throat fingering between the publication date of All
The President’s Men
and the date of Woodward’s statement, and you
have a candidate list. Collect all of Woodward and Bernstein’s
descriptions of Deep Throat, from their book and since, and you have a
set of fitness tests. Ask contributors from all over the Internet to
search out, document, and verify information to determine a
candidate’s fitness, and you have a collaborative, open-research
investigative reporting project. With an enlisted army of online
investigators, perhaps we could paraphrase Linus’ Law and say instead,
“Given enough eyeballs, all leaks are shallow.”

This model opens horrible, wonderful potential pitfalls. Watergate
reporting was filled with anonymous sources — this model takes things
a step further, to anonymous reporters. How do we know what they
report is true? What do we accept as documentation? Will the
participants immediately start flamewars that drive away the more
thoughtful would-be participants? Will the nature of the topic
attract legions of conspiracy theorists and wackos? With no deadline,
no publication, and no editorial reputation, would the product come
out as chaos? While these may seem severe problems, open source
projects always have some variant of these dangers, and none of them
seem insurmountable. Facts could be “checked in” by a group of
“committers,” and one criteria for “release” could be the number of
verifications (like platform testing) for each claim.

Maybe the project is impossible, maybe the medium is poorly suited to
the task. Maybe it is presumptuous to think a million Internet
monkeys sitting at a million keyboards would ever produce Deep Throat
when so many have failed before. I choose to think not — I’d like to
believe that, more like RC5 cracking, a collaborative group on the
Internet might be able to achieve something otherwise considered
impossible.


For the record, I am now employed again — in the technology industry, not as an investigative reporter!

Steve Anglin

AddThis Social Bookmark Button

.NET primarily provides and implements a Web services framework that Windows as well as Linux and other developers use. Web services is essentially comprised of these already existing technologies and standards (W3C, etc.): XML, SOAP, WSDL and UDDI, which can (should) be found on O’Reilly & Associates’ (ORA) XML.com. O’Reilly Network’s .NET DevCenter covers these as they are specifically implemented using the .NET framework.

The .NET framework also includes Web services interfacing with server-side logic and access to database and Legacy systems. Of course, Microsoft gives .NET developers C#, FCL (i.e., ASP.NET, ADO.NET, etc.) as well as a revamped Visual Basic .NET language and supporting IDE developer toolset, Visual Studio .NET (Visual C++, VB .NET, JScript, etc.). Additionally, there’s a CLR that serves as Win32/64 virtual machine for compiling/processing. While of course Microsoft prefers that you use this for Windows Web services development, it’s not prerequisite. That’s because .NET includes the IDL (Interface Definition Language).

For example, if you’re servers are Linux-based, you may want or need to use Java as part of your server-side-based Web services component (EJB), servlets and JSP development in your, perhaps, dominant .NET environment. Another possible example includes open source .NET projects such as ActiveState’s Perl.NET and Python.NET. With the .NET IDL, Perl and Python may be used instead of the C# and Java programming languages and their respective components. If you want to learn about the specific open source .NET projects and implementations, the .NET DevCenter is your source for this as interest in these endeavors continues to evolve.

Therefore, look for the following top 5 trends to be covered on the .NET DevCenter:

1. .NET programming language interoperability using IDL (in theory and practice)
2. .NET Web services interoperability (in practice)
3. Open Source .NET projects such as Python.NET and Perl.NET.
4. Visual Studio .NET, Hailstorm and Passport security
5. Taking .NET to wireless and embedded devices.

What do you think? Please share your thoughts on the top five .NET technology trends, stories and/or issues for 2002.

Steve Anglin

AddThis Social Bookmark Button

Looking ahead, here are the top 5 trends, issues and/or potential stories to expect from Java this year:

1. JAWS (Java API for Web Services) platform, which may include the JAX APIs, JXTA, jUDDI/UDDI, jSOAP/SOAP, and more yet to be determined.

2. JAX Pack continues its evolution: JAXP, JAXM, JAXB, JAXR, JAX-RPC, as well as possibly JAXT (Java API for XML Transformations) and JAXW (Java API for Wireless XML(WML)).

3. J2EE v.1.4 with its focus on Web services, along with the development of EJB 2.1 and the next versions of Servlets, JSP and more.

4. J2EE API for wireless Java (J2ME), including JSP and MIDlets, etc.

5. J2EE for the Mac OS X, if Mac OS X becomes accepted as a server-side OS.

What do you think of these top 5? If you think there are others to consider, feel free to share.

Steve Anglin

AddThis Social Bookmark Button

Related link: http://www.idg.net/ic_788338_6134_1-3523.html

No. According to IDG, “DEBATE IS GROWING over how completely Web services can span competing software platforms, as enterprises grapple with bridging the interoperability gap between J2EE and Microsoft .NET.” This highlights the importance of interoperability for today’s developers in increasing heterogeneous environments.

What do you think? Do you find interoperability and resources to help you learn interoperability helpful? Please share your thoughts.

Steve Anglin

AddThis Social Bookmark Button

Related link: http://www.webservicesarchitect.com/content/articles/hanson01.asp

According to Web Services Architect, “With the hype surrounding .NET Web Services, and Sun bringing together an offering for Web Services, it’s time we took a look at what’s happening. In this article, we compare the two approaches to Web Services, along with examining why you might want to use one method or the other.”

What do you think?

Steve Anglin

AddThis Social Bookmark Button

Related link: http://www.winnetmag.com/Articles/Index.cfm?ArticleID=23288

According to Windows & .NET Magazine, “For wide adoption in the enterprise, .NET must run on Linux too.” Of course, this is something O’Reilly & Associates advocates to insure interoperability and adherence to open source set and developing standards like XML, SOAP, WSDL and UDDI. For more on open source .NET, visit our Open Source .NET Directory.

Share your thoughts.

Steve Anglin

AddThis Social Bookmark Button

Related link: http://www.sdtimes.com/news/045/story7.htm

According to SD Times, “A major revision to the J2EE platform that included the much-anticipated EJB 2.0 specification dominated the news in Java development this past year. But disappointment over a lack of standards for Web services, an apparent decline in participation in the Java Community Process, and a continued consolidation of the application server market are issues that continue to plague Sun Microsystems Inc.”

While there’s disappointment over lack of Web services standards, Sun has indicated that this may be addressed as part of a focus for the upcoming J2EE 1.4 release, scheduled for late this year.

JCP is a concern, but my main concern is the continued consolidation of the application server market. This will continue to promote proprietary or vendor specific API and implementations. To help combat this, open source Java Web application servers and containers such as JBoss and other projects will be key to providing competitive influence as the year 2002 unfolds.

What do you think?

Steve Anglin

AddThis Social Bookmark Button

Related link: http://www.sdtimes.com/news/045/story1.htm

“Recent decisions by major J2EE app server vendors to extend J2EE in proprietary directions has made official what has been known for a long time…the promise of Java is now dead,” according to SD Times. I don’t necessarily agree with this in general, as long as there are open source J2EE containers such as JBoss, etc. What do you think?

Share your thoughts.

Advertisement