Eclipse WTP. The Eclipse Web Tools Platform Project Dominique De Vito – Thales IS ([email protected]) A top-level project with coleadership, BEA and the ObjectWeb Consortium. What is this project about?. A new top level project at Eclipse.org t o build - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
a generic, extensible and standards-based tool platform upon which software providers can create specialized, differentiated offerings for J2EE and Web-centric application development.
Key objectives to combine product innovation with adherence to vendor-neutral
standards and technologies, while delivering practical solutions to real development concerns.
build on the Eclipse Project, and other core Eclipse technologies,
to provide a common foundation of frameworks and services for tooling products.
To deliver tooling products both for exemplary purposes and to validate the underlying foundation.
Extension of the Eclipse value proposition To follow the high standard for technical excellence set by the Eclipse project
functional innovation and overall extensibility within the Java IDE domain.
Vendor ecosystem vs. commoditization To support a vital application development market rather than to "commoditize" viable
commercial product spaces with an open source alternative. Vendor neutrality
To encourage Eclipse participation and drive Eclipse market acceptance by strengthening the long-term product value propositions of the widest possible range of application development vendors.
Standards-based innovation To deliver an extensible, standards-based tooling foundation on which the widest
possible range of vendors can create value-added development products for their customers and end-users.
Agile development Agile development and planning process, incremental progress, focused near-term
deliverables, and flexible long-term planning. Inclusiveness & diversity
To assimilate the best ideas from the largest number of participants representing the needs of the widest range of end-users (market and geographical domains) .
Not in scope : JCP standards => JDT or J2EE Standard Tools subprojects, other technologies => future (?) subprojects
ComponentsModels: Project, Editor, Web Artifacts, ServerTools: supporting the base standards and extensible (e.g. an
extensible HTML editor to support HTML-based template languages such as PHP and JSP)
Examples of Tools : source editors (HTML, JavaScript), graphical editors (SQL, WSDL/XSD), XML utitilies, server tools, web service explorer, builders, validators and EMF models…
Goal : to build IDE + toolset that leverages the Apache Beehive application framework (Beehive makes J2EE easier by building a simple object model on J2EE and Struts – use of JSR-175 metadata annotations to reduce J2EE coding)
Pollinate includes :NetUI PageFlows – These are built on top of struts, and allow easier
tooling as well as automatic updating of struts config files with the use of metadata.
Controls – These are a lightweight component framework that helps programmers build components that incorporate metadata into their programming model. [Apache Beehive] will come with a few pre-made controls as well.
Web Services – This will be the Reference Implementation of JSR-181, which is an annotation driven programming model for Web Services.
Simply put : Pollinate will provide an IDE that enables developers to visually build and assemble enterprise-scale web applications, JSPs, web services, and leverage the Java controls framework for creating and consuming J2EE components; optimized for a service-oriented architecture