Attachment 71210 Details for Bug 192502 – Patch to fox broken links

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

[patch] Patch to fox broken links

patch.txt (text/plain), 20.20 KB, created by Denis Roy

on 2007-06-13 13:56:19 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: Denis Roy

Created: 2007-06-13 13:56:19 EDT

Size: 20.20 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P www
>Index: proposals/stp/index.php
>===================================================================
>RCS file: /cvsroot/org.eclipse/www/proposals/stp/index.php,v
>retrieving revision 1.6
>diff -u -r1.6 index.php
>--- proposals/stp/index.php	21 Dec 2005 19:55:08 -0000	1.6
>+++ proposals/stp/index.php	13 Jun 2007 17:55:54 -0000
>@@ -25,13 +25,13 @@
> news://news.eclipse.org/eclipse.stp.</a>
> 
> <h2>Overview</h2>
>-ï¿½SOA Toolsï¿½ is a vast domain, however there are a set of key requirements that run across the domain. The goal of this proposed project is to put the fundamentals in-place so that an extensible tool set made of components and exemplary tools for constructing SOA applications is created. STP will leverage the existing work of the other projects like Data Tools and Web Tools Platform projects.
>+ï¿½SOA Toolsï¿½ is a vast domain, however there are a set of key requirements that run across the domain. The goal of this proposed project is to put the fundamentals in-place so that an extensible tool set made of components and exemplary tools for constructing SOA applications is created. STP will leverage the existing work of the other projects like Data Tools and Web Tools Platform projects.
> 
> A developer using the proposed SOA Tooling project is interested in an environment that is easy to use -- one in which the challenges of application development are due to the problem domain, not the complexity of the tools employed. To this end, the project will strive to create a highly usable and consistent environment that works well with associated technologies, whether being used by a developer working/creating a service, an administrator maintaining or monitoring a production system, or constructing a larger SOA Network.
> 
> Such an environment starts with key frameworks designed both for use and extensibility. Examples include the location or creation of a service consumer or provider, the consumption of these services, the configuration of the physical attributes (transport, message format) and the policies required to access or consume the like (security policy, access control, transactional, availability). Further the ability to locate and add services to the SOA interactions like transformation, routing, for process orchestration to a broker or end-point needs to be addressed.
> 
>-Finally the creation of Artifacts that can be used to deploy, enforce or manage said SOA participantsï¿½ needs to be created from the Eclipse tooling in an extensible way.
>+Finally the creation of Artifacts that can be used to deploy, enforce or manage said SOA participantsï¿½ needs to be created from the Eclipse tooling in an extensible way.
> 
> The proposed project will not try to attempt to define every type of service in a SOA but to define the contracts to unify them into a SOA through an extensible framework and model the policies and interactions with an abstraction so that multiple specific vendor implementations can be supported from the vendor independent models of <a href="http://www.w3.org/TR/wsdl" target="_blank">WSDL</a> and other web service standards.
> 
>@@ -41,7 +41,7 @@
> The SOA Tools Platform (STP) project will include extensible frameworks and exemplary tools, enabling a diverse set of plug-in offerings specific to particular SOA participant technologies and supported by the STP ecosystem. In the spirit of Eclipse, the project will be guided by the following values:
> 
> <ul>
>- <li>Vendor neutrality: We intend to provide SOA service construction, policy and service interaction frameworks and tools not biased toward any vendor. Our intention is that STP be leveraged to provide the Eclipse community with the widest range of choices possible. To this end, we seek <a href="/projects/dev_processes/validation-phase.php">community involvement</a> in formulating key framework interfaces, so that the largest possible constituency is represented.</li>
>+ <li>Vendor neutrality: We intend to provide SOA service construction, policy and service interaction frameworks and tools not biased toward any vendor. Our intention is that STP be leveraged to provide the Eclipse community with the widest range of choices possible. To this end, we seek <a href="/projects/dev_process/validation-phase.php">community involvement</a> in formulating key framework interfaces, so that the largest possible constituency is represented.</li>
> <li>Extensibility: We recognize both the common need for SOA tooling infrastructure and the desire to extend the offerings in new and innovative ways. To support these efforts, our components will be designed for, and make good use of, extensibility mechanisms supported by Eclipse. 
> 
> 		 
>@@ -49,9 +49,9 @@
> 
> <li>Standards-based innovation: This proposed project will 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. Where standards exist, we will adhere to them. At least, at first, where standards are emerging, we will wait for them to emerge; this can be re-evaluated later according to user needs and contributor availability. Where multiple technologies are widely used for a given functional need, we will attempt to support each, subject only to technical feasibility and our goal of providing the most capable and extensible foundation long term.</li>
> 
>-<li>Community Involvement: Success for STP, as with other eclipse.org projects, is as much a factor of community involvement as the technical merit of its components. We strongly believe that STP will achieve its full potential only as the result of deep and broad cooperation with the Eclipse membership-at-large. Thus, we will make every effort to accommodate collaboration, reach acceptable compromises, and provide a project management infrastructure that includes all contributors, regardless of their affiliation, location, interests, or level of involvement. Regular meetings covering all aspects of STP, open communication channels, and equal access to process will be key areas in driving successful <a href="/projects/dev_processes/validation-phase.php">community</a> involvement.</li>
>+<li>Community Involvement: Success for STP, as with other eclipse.org projects, is as much a factor of community involvement as the technical merit of its components. We strongly believe that STP will achieve its full potential only as the result of deep and broad cooperation with the Eclipse membership-at-large. Thus, we will make every effort to accommodate collaboration, reach acceptable compromises, and provide a project management infrastructure that includes all contributors, regardless of their affiliation, location, interests, or level of involvement. Regular meetings covering all aspects of STP, open communication channels, and equal access to process will be key areas in driving successful <a href="/projects/dev_process/validation-phase.php">community</a> involvement.</li>
> 
>-<li>Transparency: As with all projects under the eclipse.org banner, key information and discussions at every level ï¿½ such as requirements, design, implementation, and testing ï¿½ will be easily accessible to the Eclipse membership-at-large.</li>
>+<li>Transparency: As with all projects under the eclipse.org banner, key information and discussions at every level ï¿½ such as requirements, design, implementation, and testing ï¿½ will be easily accessible to the Eclipse membership-at-large.</li>
> 
> <li>Agile development: We will strive to incorporate into our planning process innovations that arise once a project is underway, and the feedback from our user community on our achievements to date. We think an agile planning and development process, in which progress is incremental, near-term deliverables are focused, and long-term planning is flexible, will be the best way to achieve this.</li></ul>
> 		
>@@ -75,7 +75,7 @@
> <li>The WSDL editing capabilities will be extended to provide the ability to support multiple physical bindings but not limited to JMS, MQ, Tibco, CORBA, and the ability for vendors to easily provide extensions for specific transports, for example Celtix, WSIF, or Synapse.</li>
> <li>The creation of and configuration of bindings (WSDL) for additional message formats for legacy integration in the SOAN, for example tooling to represent Cobol copy books one the wire or G2++, or CSV records</li>
> <li>The association of runtime policy with said service participants, for example the ability to mark a service provider as secure, load balanced, state-full/stateless, or transactional. This information is then used to create deployment artifacts and model interaction between service consumers and providers. (See SOAN Deployment subproject for list of policies targeted)</li>
>- <li>Exemplary implementation support for Normalized Message (<a href="http://www.jcp.org/en/jsr/detail?id=208" target="_blank">JBI ï¿½ JSR208</a>) bindings and transports (WSDL) for collocated or JBI/JVM interactions. The collocated interactions will not be limited to JBI, but JBI will be used as one of the exemplary tool implementations. Thus the editors required to create a JBI plugin, consume JBI services and model interactions with JBI components will be integrated into the relevant editors</li>
>+ <li>Exemplary implementation support for Normalized Message (<a href="http://www.jcp.org/en/jsr/detail?id=208" target="_blank">JBI ï¿½ JSR208</a>) bindings and transports (WSDL) for collocated or JBI/JVM interactions. The collocated interactions will not be limited to JBI, but JBI will be used as one of the exemplary tool implementations. Thus the editors required to create a JBI plugin, consume JBI services and model interactions with JBI components will be integrated into the relevant editors</li>
> <li>The creation of an extensible framework for plugging in additional extensions for configuring bindings, transports and policies. For examples of these see (b,c, and d).</li>
> <li>The WTP validation tools used and extended to validate said contacts/policies</li>
> <li>The development tools will be able to support additional extensions providing extension points into the editor as well as the schema validator to allow developers to validate their WSDL against the schema which defines that extension.</li>
>@@ -85,7 +85,7 @@
> SOAN Deployment subproject
> 
> 
>-Ideally when a SOAN is created, a separation of Resources, Components, Business Services, and Presentation is desired. Most people donï¿½t agree on the exact terms, but all agree on the patterns for creating a re-useable network of both application and infrastructure participants. The STP platform will focus on providing the tooling required to tie these entities together based on their contracts and policies.
>+Ideally when a SOAN is created, a separation of Resources, Components, Business Services, and Presentation is desired. Most people donï¿½t agree on the exact terms, but all agree on the patterns for creating a re-useable network of both application and infrastructure participants. The STP platform will focus on providing the tooling required to tie these entities together based on their contracts and policies.
> 
> 
> Explicitly,
>@@ -95,23 +95,23 @@
> <li>An abstract model (EMF) will be created to describe service policies. The initial policies targeted include, message reliability, addressing, contract retrieval, location services, transactional, load balancing, high availability, state-full/stateless, security, SLAs(max response time), governance (how it is audited), message attributes (compression)</li>
> <li>Readers and writers will be provided for <a href="http://www.xml.com/" target="_blank">XML</a> & <a href="http://specs.xmlsoap.org/ws/2004/09/policy/ws-policy.pdf" target="_blank">WS-policy</a> description of these policies. Extensions can be added for additional readers and writers</li>
> <li>Validation and matching of services will be provided (for example, are the consumer and provider policies compatible)</li>
>- <li>Specific policy patterns will be implemented for <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss" target="_blank">WS-Security</a>, role based access control, transaction (<a href="http://www.oasis-open.org/committees/%20tc_home.php?wg_abbrev=ws-caf" target="_blank">WS-C and WS-AT</a> implementation), location services (repository policy for contacts and references).</li>
>+ <li>Specific policy patterns will be implemented for <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss" target="_blank">WS-Security</a>, role based access control, transaction (<a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-caf" target="_blank">WS-C and WS-AT</a> implementation), location services (repository policy for contacts and references).</li>
> <li>Policies extensions may also be used to describe policies like message compression, encryption, and Service usage and response time contacts. Samples of some of these will be provided as implementation examples. A base model for policies will be provided together with the models of the specific policies. A default editor will be dynamically created based on the model. However specific editors can be substituted for a specific policy model by providing an extension to edit that policy. All policies will have a default dynamic XML generator, and it is expected that implementations will be provided for specific runtimes. An exemplary implementation will be provided for Celtix, under the Celtix Tools Project subproject.</li>
> <li>The definition of the deployment requirements for a service policies, i.e. the service can be collocated, requires JEE, JSE etc, so that deployable configurations can be modeled. This definition is then used by the extension to create the relevant deployment artifacts for that support the specific runtime. For example create a WAR file with security enabled and deploy as a proxy server.</li>
> </ol>
> 
> 
> 
>-This section is NOT attempting to handle service orchestration with <a href="http://www.oasis-open.org/committees/%20tc_home.php?wg_abbrev=wsbpel" target="_blank">BPEL</a>. That is viewed as the scope of a services participant, and will be an internal detail on one of the services in SOAN.
>+This section is NOT attempting to handle service orchestration with <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel" target="_blank">BPEL</a>. That is viewed as the scope of a services participant, and will be an internal detail on one of the services in SOAN.
> 
> Expected Runtime specific extensions subprojects
>-Exemplary implementations can be provided for specific tooling of runtimes, provided they are built on the extensions and are pluggable for the specific vendor or open source implementations so that the extensible framework is not compromised. Thus extensions to support ESBï¿½s, Repositories, Brokers, Containers and Data Access services, etc should be built as Runtime extension subprojects.
>-Over and above the participants there are some key enabling technologies in a SOAN. These include ESBï¿½s, Repositories, Brokers, Containers and Data Access, which are present in every SOA deployment. These specific participants will be also tackled in the initial scope. Additional services can be tackled with the addition of members to this project. These subprojects build on the concepts and deliverables from the above two subproject in addition to the DTP (Data Tools Platform) project. 
>+Exemplary implementations can be provided for specific tooling of runtimes, provided they are built on the extensions and are pluggable for the specific vendor or open source implementations so that the extensible framework is not compromised. Thus extensions to support ESBï¿½s, Repositories, Brokers, Containers and Data Access services, etc should be built as Runtime extension subprojects.
>+Over and above the participants there are some key enabling technologies in a SOAN. These include ESBï¿½s, Repositories, Brokers, Containers and Data Access, which are present in every SOA deployment. These specific participants will be also tackled in the initial scope. Additional services can be tackled with the addition of members to this project. These subprojects build on the concepts and deliverables from the above two subproject in addition to the DTP (Data Tools Platform) project. 
> 
> 
> Celtix Tools Project 
> 
>-This proposed project will explicitly tackle the tooling of specific implementations of ESBï¿½s, Repositories, Brokers, Containers and Data Access. Thus the abstraction layers created by the above projects will be used to create extensions to tool the Celtix, ServiceMix, or used with any other JBI container. This forms both an example and exemplary tool implementation for the end-end usage of the Tools provided include
>+This proposed project will explicitly tackle the tooling of specific implementations of ESBï¿½s, Repositories, Brokers, Containers and Data Access. Thus the abstraction layers created by the above projects will be used to create extensions to tool the Celtix, ServiceMix, or used with any other JBI container. This forms both an example and exemplary tool implementation for the end-end usage of the Tools provided include
> 
> 
> 
>@@ -140,7 +140,7 @@
> 
> 
> 
>-In a SOA network the Quality of Service is one of the key characteristics, this includes High Availability, security, response times, transactional, management and logging, for example ARM. These dynamics define the ï¿½valueï¿½ of the network to deliver on a service contract SLA (service level agreements). The modeling and tooling of each of these are out of scope of the initial proposal, but the visualization of these attributes and design based on them is in scope, together with interaction with them in the SOAN to provide or enforce the SLAï¿½s.
>+In a SOA network the Quality of Service is one of the key characteristics, this includes High Availability, security, response times, transactional, management and logging, for example ARM. These dynamics define the ï¿½valueï¿½ of the network to deliver on a service contract SLA (service level agreements). The modeling and tooling of each of these are out of scope of the initial proposal, but the visualization of these attributes and design based on them is in scope, together with interaction with them in the SOAN to provide or enforce the SLAï¿½s.
> 
> 
> 
>@@ -171,7 +171,7 @@
> <li>Management Screens to look at the deployed solution, start / stop / pause services etc.</li>
> </ol>
> 
>-The very top of the layer is the SOAN level, a view of the policies and interrelations of the services and Quality of Service (QoS) provided but the SOAN. This layer will be used to view inter service policies, connect ï¿½compatibleï¿½ services together, etc. For example polices can be set prior to creating of contracts, settings security levels and even identify key repositories that will be used by the developer. The SOAN layer provides the ï¿½businessï¿½ view of the SOA Network.
>+The very top of the layer is the SOAN level, a view of the policies and interrelations of the services and Quality of Service (QoS) provided but the SOAN. This layer will be used to view inter service policies, connect ï¿½compatibleï¿½ services together, etc. For example polices can be set prior to creating of contracts, settings security levels and even identify key repositories that will be used by the developer. The SOAN layer provides the ï¿½businessï¿½ view of the SOA Network.
> 
> <h2>Projects</h2>
> 
>@@ -200,7 +200,7 @@
> <li>Erica Mitchell, IONA</li>
> <li>Fiona Kennedy, IONA</li>
> <li>Freeman Fang, IONA</li>
>- <li>Gaï¿½l Blondelle, EBM WebSourcing</li>
>+ <li>Gaï¿½l Blondelle, EBM WebSourcing</li>
> <li>Howard Gao, IONA</li>
> <li>James Strachan, LogicBlaze</li>
> <li>Jean-Pierre Laisne, ObjectWeb / Bull</li>

Actions: View | Diff

Attachments on bug 192502: 71210