Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Craig Salter/Chuck Bridgham Eclipse WTP Project Common Tools Open House

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Contents ■ Contributors ■ Function ■ Plugins ■ API ■ Development ■ Appendices

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Contributors ■ Craig Salter (IBM) –Committer / XML Web Services Component lead ■ Chuck Bridgham (IBM) –Committer / J2EE Component lead ■ Vijay Bhadriraju (IBM) –Committer –Validation framework ■ Michael Elder (IBM) –Common Navigator –Flexible Project ■ Jason Sholl (IBM) –Common Datamodel ■ Jeffrey Liu (IBM) –Committer ■ John Lanuti (IBM) –Annotations ■ Naci Dai (Eterations) –Annotations ■ Chris Brealey (IBM) –Committer / Java Web Services Component lead ■ Peter Moogk (IBM) –Environment framework ■ Nitin Dahyabhai (IBM) –Committer –Snippets ■ Many more…

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - What Is The Common Component? Actually, its three components – wst.common, jst.common, wst.command "The common components contain plugins that provide generic functionality that are applicable in several different contexts. Plugins in the common component should not have dependencies on plugins outside of the Eclipse base.” Some conceptual tests to decide what should go into common… ■ Is it destined for API ? –if it has no API story, its should be moved into a different component specific to those who need it ■ Should it ultimately live in base Eclipse ? –common is often used as a temporary staging ground for generic function that will eventually be absorbed into base Eclipse ■ What are the dependencies? –if the function has dependencies on more than base eclipse, that’s a red flag that it might not be ‘common’ ■ Is it generic? –Is this function generically applicable to multiple domains in practice (not just theory)

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Common - Evolution ■ Existing plugins may migrate to base Eclipse (or other projects) –tabbed properties sheet –project navigator ■ Existing plugins may not be ‘common’ enough –in practice function is less ‘common’ than we initial thought … who’s actually using it? We need to collectively scrutinize the ‘common’ components to ensure things lives in the right place

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Function – Common Tools ■ Common UI, Tabbed property sheet ■ URI Resolver ■ Snippets ■ Validation Framework * ■ EMF Extensions ■ Datamodel extensible commands/wizards ■ Environment Command/Wizard Framework ■ Flexible Project (Detail in J2EE session) ■ Common Navigator ■ Dependency Checker

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Common UI ■ Generic UI components –Tabbed properties sheet (to be moved into Eclipse base) –Extended file selection dialogs, views –Drag and Drop helper classes –‘Navigable’ Table Viewer (table with improved keyboard navigation)

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - URI Resolver ■ Lots of different artifact ‘types’ have references to other artifacts –HTML –JSP –XML –XML Schema ■ Common –Typically resolution is very similar for all artifact types Resolution should be consistent across artifacts –Different tools user different parsers, models, implementations Resolution should be consistent across tools ■ Extensible –Often tools want to ‘tap into’ the resolution mechanism –i.e. XML Catalog, Internet Cache, Project specific resolution strategies?

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - URI Resolver (cnt’d) ■ Some clients of the resolver –editors, validators, models –JSP, Taglibs, HTML, DTD, XML, XSD, WSDL

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Snippets ■ org.eclipse.wst.common.snippets ■ Adds notion of a template “toolbox” to Eclipse –User can define and manage reusable pieces of source code –Source code snippets can have sections defined as variable using place holding markers –Framework for contributing new snippets with custom drag and drop and double-click insertion behavior ■ Depends on Eclipse & GEF (& SSE currently) ■ API status : provisional –Reasonably well documented, but subject to change before M5 given existing feedback and stated milestone goals

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Snippets (cnt’d) ■ Current Work Items –Reworking of drag and drop No longer rely on SSE drop action framework Possibly support non-text editor scenarios –Separate into Core and UI plug-ins Should allow for non-GEF UI (but not to be implemented) –Investigate adopting Eclipse Templates as underlying model –Investigate adopting Template insertion behavior as our own on double-click ■ Want more info? –Brief overview exists on the WTP website at ets/overview.html

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Validation Framework ■ Component in WST –Validation ■ Functional Overview –The framework provides a means for validators built using the framework to validate resources in a project manually or automatically. ■ Links – Overview.htmlhttp:// Overview.html ■ API –Currently there are no defined API in the framework and have been defined as provisional internal API for WTP 0.7 release. –A fully defined API for the framework is planned for WTP 1.0

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Validation Framework ■ Future Enhancements The enhancements are geared towards performance improvements on running validators built using the framework ► Provide mechanism for individual validators to run asynchronously ► Change Global and Project level validation preferences to give users more control to turn validators on and off on a build and manual validation. ■ Test Scenarios –The overall framework test scenario can be found at – n/scenarios/validation_framework_testplan.htmlhttp:// n/scenarios/validation_framework_testplan.html

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Datamodel Framework ■ Mechanism for tracking related data for operations & wizards (coming soon) –Properties get/set default/valid values validation/enablement –Know how to run themselves using operations –Nesting/Extendable –Wizards (coming soon) DataModels know how to build their wizards Easy to build wizards on top of wizards Extendable

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Environment Framework ■ For writing components for multiple environments. Eg: –Eclipse GUI –Eclipse headless –Java command line –Ant task / JUnit / Batch –Web service ■ Aspects –Progress monitoring –Status handling –URI-based resource access –Command stack management ■ Integrates with “the” command framework (today there are three!) ■ Eclipse GUI Environment –Dynamic Wizard Framework for highly non-deterministic wizards –Complete separation from command-pattern based engine code ■ Convergence TBD with DataModel, IUndoableOperation, etc.

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Common Navigator ■ Extensible mini-platform for integrated tree viewers ■ Enables tight integration between different kinds of content ■ Will be integrated into Eclipse Platform/UI in 3.2 (so no Official WTP API)

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Common Navigator Core

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Plugins – WST ■ common –org.eclipse.wst.common.dependencychecker –org.eclipse.wst.common.emf –org.eclipse.wst.common.emfworkbench.integration –org.eclipse.wst.common.frameworks –org.eclipse.wst.common.frameworks.ui –org.eclipse.wst.common.modulecore –org.eclipse.wst.common.navigator.views –org.eclipse.wst.common.navigator.workbench –org.eclipse.wst.common.snippets –org.eclipse.wst.common.ui –org.eclipse.wst.common.ui.properties –org.eclipse.wst.common.uriresolver –org.eclipse.wst.validation –org.eclipse.wst.validation.ui ■ command –org.eclipse.wst.command.env.core –org.eclipse.wst.command.env –org.eclipse.wst.command.env.ui ■ Content –EMF copy utils/XML translators etc.. –Editmodel/Validate edit/etc… –Datamodel/Function group –Datamodel wizard –Flexible project provisional API –Common Navigator Framework –Resource Extension (Groups, Filters) –Snippet framework –Core validation framework –Preference pages –Core environment framework –Eclipse headless environment –Eclipse GUI / wizard environment

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Plugins - JST ■ common –org.eclipse.jst.common.annotations.controller –org.eclipse.jst.common.annotations.core –org.eclipse.jst.common.annotations.ui –org.eclipse.jst.common.frameworks –org.eclipse.jst.common.frameworks.ui –org.eclipse.jst.common.launcher.ant –org.eclipse.jst.common.navigator.java ■ Content…. –TagSet/TagSpec/TagRegistry –Tag comments/EMF adapters –Tag completion/proposal –Java project/Working copy extensions –JavaInsertion/Editor extensions –Ant launcher –Java extensions/Working sets

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Plugins - Dependencies ■ Eclipse –Platform JDT,Resource –JEM Java Model (Reflective EMF Model) EMF Extensions (Shared by JEM and WTP) ► Project scoped Resources ► RefResource –EMF Primary metamodel framework EMF.edit

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - API - Status ■ Provisional API –Flexible Project API –Validation –Data model wizard/commands –Environment framework –Common Navigator ■ Internal frameworks –EMF extensions – base function shared with JEM to be pushed to EMF –Proposed API is relatively young ■ Links – –

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Bugzilla - Queries –Query for wst.common, wst.validation: =advanced&product=Web+Tools&component=wst.co mmon&component=wst.validation&bug_status=NEW &bug_status=ASSIGNED&bug_status=REOPENED –Query for wst.command: =advanced&product=Web+Tools&component=wst.co mmand&bug_status=NEW&bug_status=ASSIGNED &bug_status=REOPENED

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Development - WTP 0.7 ■ Stabilization –Bug fixes –Functional requests –JUnit testcase development ■ Provisional frameworks (Continuing to refine API) –Flexible project –Validation –Datamodel –Environment –Common Navigator ■ Details are in various milestone plans (sse,xml,ws,j2ee) wst.ws: wst.j2ee: wst.xml: wst.sse: wst.command:

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Development - WTP 1.0 ■ One of our main goals in the common area is to “Work with the platform” to help integrate existing frameworks delivered by both projects. –Common Navigator (Move down to Platform/UI in 3.2) –Undoable commands (Integrate, and push down requirements) –Converged environment / command / data frameworks –Flexible Projects (Integrate, Drive requirements) –Logical resources (Integrate) –Tabbed properties sheet (Move down)

Content provided under the terms and conditions of the Eclipse Public License Version June Eclipse Foundation - Development - Help! ■ Clean up warnings (e.g. use of deprecated symbols) ■ Contribute to online help content ■ Contribute to JavaDoc/API cleanup – Feedback!