News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 
Download Current Issue
ISSUE 3/15/2010 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
blogs tab
Google Code turns 5
Google Code Turns 5, and adds a Paxos Algorithm to make the system more stable and reliable.
03/17/2010 11:16 AM EST

Test your Visual Studio 2010 know-how
Microsoft is offering free beta certification exams for Visual Studio 2010.
03/17/2010 11:08 AM EST

Microsoft lifts the hood on IE9
Microsoft is previewing IE9.
03/16/2010 01:10 PM EST

 

Events calendar tab
3/22/2010 to 3/25/2010
Santa Clara, Calif.
The Eclipse Foundation

4/12/2010 to 4/14/2010
Las Vegas
Penton Media

4/12/2010 to 4/15/2010
Santa Clara, Calif.
O'Reilly Media

4/19/2010
New York City
Flagg Management

4/25/2010 to 4/28/2010
Overland Park, Kans.
IIUG


 
Most Read Latest News Blog Resources

Red Hat Gives Green Light To JBoss Projects


Following acquisition, Ram Venkataram says all systems are go



September 15, 2006 — 
Half a year after being scooped up by Red Hat, it’s business as usual for JBoss.

Entwined in numerous open-source projects at the time of its acquisition in April, JBoss continues to work undeterred on its popular Java application server, as well as its Eclipse-based IDE and Seam, its development framework that blends SOA, AJAX, JSF and EJB 3 to simplify Java development.

SD Times spoke with Ram Venkataram, director of product management for core products at JBoss, about recent changes that have simplified Java development, and how JBoss is seeking to further simplify the process with advances to its Seam framework.

SD Times: How has Seam 1.0 been received?

Ram Venkataram: Seam has been received extremely well. We’re getting almost 5,000 downloads [of Seam] a month right now. It has been submitted as a JSR [JSR 299] at Sun. It’s basically a simplified standards-based programming and component model that unifies and integrates the application development process, from browser-based stateless applications to larger stateful applications.

J2EE’s complexity has remained steadily high. With Java EE 5, it kind of simplifies the complexity. We’ve tried to keep the complexity level [of Seam] very low by providing a simple unified component model for building stateful applications. When you write a component, it can be accessed from different access points: rich clients, Web services clients and browsers, for example. It shouldn’t matter how the component is accessed. We wanted to have one simple way for components to access and be accessed by other files. It unifies EJB 3 and JSF business process management.

Where is Seam going?

I think you will see more and more integration into our SOA side and more tooling on the tooling side. We’re going to fill out the road map for building all sorts of applications, whether they’re Web, SOA or rich client applications. For example, you can already build AJAX-based applications using Seam.

When is the next version of the JBoss IDE arriving?

We’re releasing our 2.0 version of the JBoss IDE in October. We have new pieces of code in there: Our JDP plug-in has been in beta for a while now, as has a whole new application server connector. It is an Eclipse-based IDE, and we provide plug-ins for customers to download and run as part of the Eclipse backbone.

How is the JBoss Application Server doing?

We’re looking to release our second release this year. We’ve had all our pieces working in the community for a very long time. Our Web services stack has been there for almost 10 months now. The pieces of the puzzle have already been there in the community for a long time, so that’s a huge test base.

I think we’ve done an exceptionally good job in future-proofing the infrastructure in building a micro-kernel based architecture. We have been able to build an infrastructure that’s plug-and-play; you can choose pieces and build your own footprint. For us, it’s a mix-and-match environment, and that makes it very easy for us to adapt to the marketplace.

What sort of tools do your internal developers use?

JBoss developers typically use a variety of tools. It’s NetBeans and Vi and text editors and Notepad. Our hardcore infrastructure developers are typically not IDE-based. It depends on the kind of developers. If you look at the IT world, probably the usage of Vi is very, very low, but in the infrastructure companies, use is very high. I think it’s because these guys have a background in the Unix heritage and they are very comfortable with Vi.

On the other side, people would use Notepad or a text editor. I used to program a lot until recently, and I used Vi. We also use several types of testing tools, such as JUnit and TestNG. On the load-testing side, it’s Jmeter or Grinder.

What would you like to see changed in the Java language?

What I’d really like to see is scripting. There’s already an emphasis on scripting technology in Java SE 6. It’s very useful for developers building business applications.

Also, Java EE technology needs to go to the next level of simplicity. We need to lower the barrier for simplicity even further. And [I’d like to see] more tooling. I think a lot of the stuff done on the Eclipse side has helped bring Java into the enterprise environment. And hopefully [we will have] an open-source JVM at some point.


Share this link: http://www.sdtimes.com/link/29590
 

Add comment


Name*
Email*  
Country     


  • Comment
  • Preview
Loading