Is TheServerSide Java Symposium de-emphasizing Java?
A show producer acknowledged on Thursday that the event was covering other areas besides Java, but stressed that Java is still the focus.
"I think it's still very much Java," said Nitin Bharti, editorial director for TheServerSide.com. "We're trying to address larger enterprise issues," such as SOA and grid, he said.
"These are all sort of concerns that Java architects have today, including AJAX," Bharti said.
"We're trying to address the entire gamut of technologies and topics," Bharti said. "The reality is, it’s a heterogeneous environment out there."
Speakers at the show are pioneers in enterprise Java, he said.
The lunchtime presentation on Wednesday, for its part, was given by Karen Tegan-Pedir, vice president of the Enterprise Java Platforms Group at Sun Microsystems. She said Java has generated a $120 billion industry.
"The Java community is more vibrant than ever," she said.
Elsewhere at the symposium, a panel on SOA featured a mockery of the WS-* (pronounced WS-star) specifications for Web services standardization. An IT consultant, Neal Ford of ThoughtWorks, called them "ws death star."
Ford argued that the WS-* specifications were being overused and that there are too many of them. Some of the WS-* specifications include specifications such as WS-Security. WS-* efforts have been led by companies such as Microsoft.
"A lot of the standards that ws death star is trying to implement are for communication outside your firewall," said Ford, who is an application architect at ThoughtWorks. But users are implementing these inside their firewall, creating overhead, Ford said in an interview after the panel session.
REST and "plain old XML" can be used inside the firewall, he said.
"You don't need federated security inside your own firewall. If you do, you have the slowest SOA ever conceived by man," he said.
As far as his use of the term, ws death star, Ford chalked this up to the plethora of WS-* standards that have been developed, which has seemed excessive.
"It seems like every time they have a meeting, they're required to generate more acronyms," said Ford.
Regarding SOA, Ford argued it was an architectural style.
"It's all about getting the disparate pieces of your architecture talking to each other in a nice, clean way," Ford said.