JBoss-IDE Roadmap

Introduction

This roadmap describes the current thinking about the future directions for JBoss-IDE. There is no target schedule because it depends heavily on the contribution of developers. Nonetheless, it is a good overview of what is coming next and what will be the future of JBoss-IDE.

The list below is not exhaustive. Some of the subjects are currently being worked on, while others are still under consideration.

For an overview of the plugin namespace, see the JBoss-IDE architecture map.

Roadmap

This roadmap is still in progress.

Note: Eclipse 2.x compatibility has been dropped in all releases past 1.3.30. Eclipse 3.0 is now stable and will be the target platform of JBoss-IDE.

-

JBossAOP Integration

Description

The goal of the JBossAOP plugin is to facilitate development and visualization of Aspect Oriented Programming paradigms.  Support will be included for standalone as well as server-based deployments.

Plugins

The plugin namespace reserved is :

• org.jboss.ide.eclipse.jdt.aop.core

• org.jboss.ide.eclipse.jdt.aop.ui

Functionality

• Visual crosscutting structure cues.

• Standalone bytecode weaving and execution.

• Automatic jboss-aop.xml (or similar) creation and updating.

Right-click utilities

• Logical gui facilitation.

• Non-pointcuttable rule adherance.

• Assign or update Interceptors - execution, field, callers, etc.

-

JSP/HTML editor

Description

The most important feature of a JSP editor is showing whether the JSP will compile without having to deploy it in a Servlet container. Therefore, the Java project offers a way to set up the compilation context for the local JSP engine (classpath, taglib definition, etc.).

Plugins

The plugin namespace reserved is :

• org.jboss.ide.eclipse.jdt.core

• org.jboss.ide.eclipse.jdt.ui

Functionality

• Ability to edit a JSP file

• (Optional) auto-completion for both HTML and Java syntax

• Ability to compile on-the-fly the JSP

• Ability to report warning and errors in the Problem View

• Ability to mark warning and errors in the JSP Editor view

-

JSP debugger through JSR 45

Description

What is JSR 45 ? Take a complete brief about JSR 45. Since JBoss server 3.2.4, the default JSP/Servlet engine is Tomcat 5.0, which embeds support for JSR45. It is now possible to offer full debugging (JSP and classes) when using JBoss 3.2.4 as a development server.

Plugins

The plugin namespace reserved is :

• org.jboss.ide.eclipse.jdt.debug.core

• org.jboss.ide.eclipse.jdt.debug.ui

Functionality

• Ability to set up breakpoints in JSP source files

• Ability to step through JSP code, just like stepping through a Java source file

• Ability to save/restore breakpoints through Eclipse workspace sessions

-

EJB3/Persistence

Description

JBoss-IDE hopes to be the first development tool to integrate the new features of Enterprise Java Beans 3 (JSR-220). The initial release will be based on the EJB3 Specification, and any new revisions that happen between now and its final release.

Plugins

The plugin namespace reserved is:

• org.jboss.ide.eclipse.jdt.ejb3.core

• org.jboss.ide.eclipse.jdt.ejb3.ui

Functionality

• EJBQL Execution, and Result Set inspection

• Content assist for EJB3/JDK1.5 Annotations

• Automated Entity Bean creation from a Table

• Session Facade templates + Code Generation

• Bean relationship tree

-

JSR-88 Deployment

JSR-88 is a standard for cross-container deployment of  enterprise applications. The JSR-88 implementation will improve upon the current deployment features of JBoss-IDE.

Plugins

The plugin namespace reserved is:

• org.jboss.ide.eclipse.deployer.jsr88.core

• org.jboss.ide.eclipse.deployer.jsr88.ui

Functionality

The JBoss-IDE specific JSR-88 functionality will be decided soon.