Nexaweb Platform 4.5 and Studio 3.0 released

| by Rob Thornton Follow 0 Followers on Jan 03, 2007. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Nexaweb released version 4.5 of their Nexaweb Platform recently, adding Section 508 Accessibility compliance. Along with the Platform release, Nexaweb Studio, an Eclipse ATF-based IDE for web 2.0 applications, version 3.0 was released.

Nexaweb Platform is composed of two parts, Nexaweb Server and Nexaweb Client. The server piece is a set of Servlets and Listeners that communicates over their proprietary message bus to a rich internet application running on the client. The client supports declarative XML UI definitions and programmatic definitions. It also provides data binding as well as a framework that can be extended with custom UI widgets.

Nexaweb Studio is a set of plugins for Eclipse that provide new Eclipse Perspectives to aid in RIA development. The new perspectives allow for drag and drop of UI components and wizards for event registration.

Nexaweb describes the products:

Delivering the industry's first Enterprise Web 2.0 (EW2.0) solution in compliance with Section 508 Accessibility, the only universal client framework supporting both Ajax and Java, and enhanced integration support with data services and relational databases.

Studio 3.0 is an Eclipse-based Integrated Development Environment (IDE) that offers enterprise Web developers, Ajax, J2EE(TM)/Java(TM) developers and software engineers a standards-based, visual design environment for creating EW2.0 applications. With Version 3.0, developers now have Ajax user interface (UI) capabilities through plug-ins to the Eclipse Ajax Toolkit Framework (ATF) and Web Standard Tools (WST) projects.

Nexaweb focused on Section 508 Accesibility in the Nexaweb Platform because of the needs of enterprises working with the Federal market. Section 508 Accessibility support required numerous changes to allow developers to create accessible widgets.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you