Difference between revisions of "Swordfish Documentation: User Stories"

From Eclipsepedia

Jump to: navigation, search
Line 1: Line 1:
 
Under construction!
 
Under construction!
  
== Eclipse SOA Runtime ==
+
We have identified user stories for the following roles
 +
 
 +
[[Swordfish:_User_Stories:_Service_Developer | Eclipse Service Developer]]
 +
 
 +
See also [[Swordfish_Documentation:_Product_Backlog | Swordfish Product Backlog]]
  
 
{| border="1" cellpadding="3" cellspacing="0" width="100%"
 
{| border="1" cellpadding="3" cellspacing="0" width="100%"
Line 15: Line 19:
 
|width="10*" | '''run''' a JAX-WS Service Participant standalone within Eclipse,
 
|width="10*" | '''run''' a JAX-WS Service Participant standalone within Eclipse,
 
|width="10*" | I can test my code immediately
 
|width="10*" | I can test my code immediately
|width="10*" | TBD
+
|width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]]
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | '''use the http and https transport protocols''',
 
|width="10*" | '''use the http and https transport protocols''',
 
|width="10*" | I can communicate over the web.
 
|width="10*" | I can communicate over the web.
|width="10*" | TBD
+
|width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]]
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
Line 30: Line 34:
 
|width="10*" | '''use dynamic policy based Service lookup'''
 
|width="10*" | '''use dynamic policy based Service lookup'''
 
|width="10*" | I can utilize QOS with different service levels for the Same service i.e. different security levels.
 
|width="10*" | I can utilize QOS with different service levels for the Same service i.e. different security levels.
|width="10*" | TBD
+
|width="10*" | [[Swordfish_Documentation:_Registry_Feature | Service Registry Feature]]
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
Line 97: Line 101:
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 +
 +
== ==
 +
See also [[Swordfish_Documentation:_Product_Backlog | Swordfish Product Backlog]]
 +
-------------------------
 +
Return to [[Swordfish | Swordfish Wiki Home]]
 +
Go to [[Swordfish_Documentation | Swordfish Documentation]]
 +
Go to [[Swordfish_Documentation:_Sprint_Plan | Swordfish Galileo (Planning)]]

Revision as of 08:51, 27 March 2009

Under construction!

We have identified user stories for the following roles

Eclipse Service Developer

See also Swordfish Product Backlog

See also Swordfish Product Backlog


Return to Swordfish Wiki Home Go to Swordfish Documentation Go to Swordfish Galileo (Planning)

User Stories
As an I would like to so that link to backlog item(s)
Eclipse Service Developer run a JAX-WS Service Participant standalone within Eclipse, I can test my code immediately Integrate Apache CXF
Eclipse Service Developer use the http and https transport protocols, I can communicate over the web. Integrate Apache CXF
Eclipse Service Developer use jms as transport protocol, I can provide a reliable transport. TBD
Eclipse Service Developer use dynamic policy based Service lookup I can utilize QOS with different service levels for the Same service i.e. different security levels. Service Registry Feature
Eclipse Service Developer use http and https as transport protocol, I can communicate over the Web. TBD
Eclipse Service Developer run a JAX-WS Service Consumer in a Servlet Engine within Eclipse, I can test my code immediately TBD
Eclipse Service Developer deploy a standalone JAX-WS Service Participant into the running Target Platform outside of Eclipse, I can test my code immediately without needing to restart the target platform (hot deployment). TBD
Eclipse Service Developer select the consumer policy dynamically, I can invoke service calls with different policies from the same consumer TBD
Eclipse Service Developer start a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse, I can test my code in a distributed environment. TBD
Eclipse Service Developer run a JAX-WS Service Consumer in a JEE Application Server outside of Eclipse, I can test my code in a distributed environment. TBD
Eclipse Service Developer start a standalone JAX-WS Service Provider in the Target Platform outside of Eclipse, I can test my code in a distributed environment. TBD
Eclipse Service Developer start a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse, I can test my code in a distributed environment. TBD
Eclipse Service Developer reference message schemas from the WSDL, I do not need to modify the WSDL when something in the message schemas changes AND I can reuse the same schemas for multiple WSDLs. TBD
Eclipse Service Developer utilize message streaming, I can provide high performance applications with low roundtrip times even for larger amounts of data transferred. TBD
Eclipse Service Developer start a JAX-WS Service Provider in a JEE Application Server I can test my code in a distributed JEE environment. TBD
Eclipse Service Developer use any other transport protocol offered by ServiceMix, I can integrate easier with legacy Systems. (I am aware that restrictions apply regarding policies influencing the wire format.) TBD
Eclipse Service Developer TBD