Skip to main content
Jump to: navigation, search

Difference between revisions of "New Help for Old Friends III"

(WebServices and WSDL)
(JPT - Dali JPA Tools)
Line 50: Line 50:
**Context model for tying this artifact information into a cohesive representation of the JPA metadata.
**Context model for tying this artifact information into a cohesive representation of the JPA metadata.
*Updates to the Platform
*Updates to the Platform
[[Category:Eclipse Web Tools Platform Project]]

Revision as of 17:08, 15 November 2007

This page to to collect miscellaneous notes and pointers to changes coming up in the WTP 3.0 (Ganymede) release. Its purpose it to be a central "jump off" point for those adopters of WTP 2.0, that are moving to WTP 3.0. Most of this information may be already contained in various mailing lists and bugzilla's, but ... we thought it best if there as a central place to get people started.

Adopters: if you run into trouble or notice things that are not covered here, please let us know ( is a good place). This will not only help us keep this list up to date, but will help us better learn, over time, the discipline of "platform development" and help make sure we learn to provide compatible API's, migration instructions, etc., in the future. [ It isn't always easy, but our intent is to make it as simple and painless as possible for adopters to use WTP as a true platform.

One thing we've learned in the past is that some don't adopt every version ... some early adopters went from 0.7 directly to 1.5, for example. Unfortunately, it's hard for us to present the information in that way, covering perhaps multiple changes, but hopefully as we develop these for each release, they will all flow together to aide adopters.

Note: as these notes develop and grow in number, they may occasionally be re-organized into categories, etc.

Common Components

  • The facet wizard page is no longer in the project creation wizards. It is now accessible as a popup (click the modify button next to the configurations drop-down) rather than as a second page in all of the WTP wizards. Please See the following resource for more information. Link

XML/JSP Components

  • Version changes for the following plugins:
The org.eclipse.wst.sse.ui plugin increased its version from 1.0.400 to 1.1.0

Server Component

WebServices and WSDL

  • Web service pop-up category is moved from to the plugin. Please see bugzilla 202303 for details. This is done to support the move of the Web Services Explorer plugin from the JST to the WST install package.
Adopters will need to change the Web services popop menu path.
As a result, the following 2 WTP plugins have their version changed to 1.1.0:
  • A new service policy framework has been introduced to create an extensible framework for extenders to specify the quality of service that would effect different tools such as wizards, editor and validators (see 196997).
The new framework can be found in the two new plugins:
The "Profile Compliance and Validation" preference page has been refactored. WSDL Validation preferences have been moved to a new "Wizard Validation" preference page, and WS-I profile compliance preferences moved to a new "Service Policies" preference page. No migration is required for preferences defined in previous versions of WTP- these preferences are still honored. If you choose to enable project specific preferences, default values are taken from the current workspace values, i.e. project specific default values follow the workspace preference as in previous versions of WTP.
Continue to use in plug-in to query WS-I profile compliance preference settings as before. Alternatively you can use and to query and work with the preferences settings. The WS-I profile compliance related operation and policy ids are defined in\plugin.xml and\plugin.xml respectively.
Extenders can add preferences to the Service Polices preference page using 2 new extension points (see associated schemas, ServicePolicyPlatform, and ServicePolicyPlatformUI for more details):



JPT - Dali JPA Tools

  • New Context/Resource model
    • Resource model for capturing and managing raw JPA artifact data (Java source and XML Mapping Files).
      • XML content managed via EMF XML Translators, Java Annotations manged via Dali's Annotation Adapters.
    • Context model for tying this artifact information into a cohesive representation of the JPA metadata.
  • Updates to the Platform

Back to the top