Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Dali/Indigo/DBWS"

< Dali‎ | Indigo
(New page: = Functional Specification: Dali DBWS Support = [https://bugs.eclipse.org/bugs/show_bug.cgi?id=330503 Bug 330503] == Document History == {|{{BMTableStyle}} |-{{BMTHStyle}} ! Date ! A...)
 
(Open Issues)
 
(5 intermediate revisions by 2 users not shown)
Line 18: Line 18:
  
 
EclipseLink DBWS allows for quick generation of web services to expose data from a relational database.  Dali can provide tooling for this database web services functionality with integration into the Eclipse IDE.
 
EclipseLink DBWS allows for quick generation of web services to expose data from a relational database.  Dali can provide tooling for this database web services functionality with integration into the Eclipse IDE.
 +
 +
Short term goals:
 +
* Integrate with the DBWS Builder to generate artifacts based on a dbws-builder.xml configuration file
  
 
Long term goals:
 
Long term goals:
* Integrate with the DBWS Builder to generate artifacts based on a bdws-builder.xml configuration file
 
 
* Ability to create the dbws-builder.xml file
 
* Ability to create the dbws-builder.xml file
 
* Full editor for dbws-builder.xml file
 
* Full editor for dbws-builder.xml file
 
* Target server specific generation
 
* Target server specific generation
 +
* DBWS Facet and Project
  
== Concepts ==
+
== References ==
 
+
 
+
 
+
===References===
+
  
 
[http://www.eclipse.org/eclipselink/dbws.php EclipseLink DBWS home]
 
[http://www.eclipse.org/eclipselink/dbws.php EclipseLink DBWS home]
Line 35: Line 34:
 
== Requirements / Functionality ==
 
== Requirements / Functionality ==
  
===Phase 1===
+
=== Phase 1 ===
  
 
==== DBWS Builder integration ====
 
==== DBWS Builder integration ====
 +
 +
===== Use cases =====
 +
 +
Case 1: Generate DBWS artifacts via dbws-build.xml file for Java EE deployment
 +
* User create new dynamic web project
 +
* User creates and populates dbws-build.xml in the dynamic web project
 +
* User right-clicks on dbws-build.xml file and selects the Web Services->Generate database web service
 +
* User selects Java EE deploment (See open issue #1)
 +
* User selects finish and is warned by a prompt that existing dynamic web content in this project will be overwritten
 +
 +
 +
Case 2: Generate DBWS artifacts via dbws-build.xml file for Java SE Endpoint deployment
 +
* User creates Java project or uses existing Java project
 +
* User creates and populates dbws-build.xml in the project
 +
* User right-clicks on dbws-build.xml file and selects the Web Services->Generate database web service
 +
* User selects Java SE Endpoint deploment (See open issue #1)
 +
* User selects finish and is warned by a prompt that existing dynamic web content in this project will be overwritten
 +
 +
Assumptions:
 +
* Will require dynamic web project for creation of Java EE output
 +
* Only enable wizard menu item when the content type is of the dbws-build.xml file
 +
 +
=== UI Design ===
 +
 +
==== Wizard ====
 +
 +
[Wizard screen shots go here]
 +
 +
=== Phase 2 ===
 +
 +
Currently undefined
 +
 +
== Open Issues ==
 +
 +
* Java SE based DBWS support is not yet planned, and may require changes to the DBWS Builder
 +
* Need to determine which menus and what labels will be used for DBWS actions
 +
* Need to determine whether connection needs to be in DTP, and whether we should re-use that connection for Builder

Latest revision as of 17:25, 3 December 2010

Functional Specification: Dali DBWS Support

Bug 330503

Document History

Date Author Version Description & Notes
11-23-2010 Neil Hauge Draft

Feature overview

EclipseLink DBWS allows for quick generation of web services to expose data from a relational database. Dali can provide tooling for this database web services functionality with integration into the Eclipse IDE.

Short term goals:

  • Integrate with the DBWS Builder to generate artifacts based on a dbws-builder.xml configuration file

Long term goals:

  • Ability to create the dbws-builder.xml file
  • Full editor for dbws-builder.xml file
  • Target server specific generation
  • DBWS Facet and Project

References

EclipseLink DBWS home

Requirements / Functionality

Phase 1

DBWS Builder integration

Use cases

Case 1: Generate DBWS artifacts via dbws-build.xml file for Java EE deployment

  • User create new dynamic web project
  • User creates and populates dbws-build.xml in the dynamic web project
  • User right-clicks on dbws-build.xml file and selects the Web Services->Generate database web service
  • User selects Java EE deploment (See open issue #1)
  • User selects finish and is warned by a prompt that existing dynamic web content in this project will be overwritten


Case 2: Generate DBWS artifacts via dbws-build.xml file for Java SE Endpoint deployment

  • User creates Java project or uses existing Java project
  • User creates and populates dbws-build.xml in the project
  • User right-clicks on dbws-build.xml file and selects the Web Services->Generate database web service
  • User selects Java SE Endpoint deploment (See open issue #1)
  • User selects finish and is warned by a prompt that existing dynamic web content in this project will be overwritten

Assumptions:

  • Will require dynamic web project for creation of Java EE output
  • Only enable wizard menu item when the content type is of the dbws-build.xml file

UI Design

Wizard

[Wizard screen shots go here]

Phase 2

Currently undefined

Open Issues

  • Java SE based DBWS support is not yet planned, and may require changes to the DBWS Builder
  • Need to determine which menus and what labels will be used for DBWS actions
  • Need to determine whether connection needs to be in DTP, and whether we should re-use that connection for Builder

Back to the top