Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Swordfish Documentation: User Stories: Service Developer"
(reprioritized) |
(Add ID's) |
||
| Line 2: | Line 2: | ||
== User Stories for Service Developers == | == User Stories for Service Developers == | ||
|- style="background:#DFF4B3;" | |- style="background:#DFF4B3;" | ||
| + | |width="10*" |'''ID''' | ||
|width="10*" |'''As an''' | |width="10*" |'''As an''' | ||
|width="10*" |'''I would like to''' | |width="10*" |'''I would like to''' | ||
| Line 7: | Line 8: | ||
|width="10*" |link to backlog item(s) | |width="10*" |link to backlog item(s) | ||
|- | |- | ||
| + | |width="10*" | S001 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | use the target platformprovisioning P2 repository to '''download''' a released version of Swordfish, | |width="10*" | use the target platformprovisioning P2 repository to '''download''' a released version of Swordfish, | ||
| Line 12: | Line 14: | ||
|width="10*" | [[Swordfish_Documentation:_Build_Eclipse_Feature | Swordfish Eclipse Features from download site]] | |width="10*" | [[Swordfish_Documentation:_Build_Eclipse_Feature | Swordfish Eclipse Features from download site]] | ||
|- | |- | ||
| + | |width="10*" | S005 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''install''' Swordfish Tools into my existing Eclipse IDE, | |width="10*" | '''install''' Swordfish Tools into my existing Eclipse IDE, | ||
| Line 17: | Line 20: | ||
|width="10*" | [[Swordfish_Documentation:_SwordfishPlatform | Set Swordfish as target patform]] | |width="10*" | [[Swordfish_Documentation:_SwordfishPlatform | Set Swordfish as target patform]] | ||
|- | |- | ||
| + | |width="10*" | S010 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''run''' a JAX-WS Service Participant within Eclipse Equinox, | |width="10*" | '''run''' a JAX-WS Service Participant within Eclipse Equinox, | ||
| Line 22: | Line 26: | ||
|width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | |width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | ||
|- | |- | ||
| + | |width="10*" | S015 | ||
|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''', | ||
| Line 27: | Line 32: | ||
|width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | |width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | ||
|- | |- | ||
| + | |width="10*" | S020 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''use dynamic policy based Service lookup''' | |width="10*" | '''use dynamic policy based Service lookup''' | ||
| Line 32: | Line 38: | ||
|width="10*" | [[Swordfish_Documentation:_Registry_Feature | Service Registry Feature]] | |width="10*" | [[Swordfish_Documentation:_Registry_Feature | Service Registry Feature]] | ||
|- | |- | ||
| + | |width="10*" | S025 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''write''' a JAX-WS Service '''using Eclipse''' and '''compile''' it, | |width="10*" | '''write''' a JAX-WS Service '''using Eclipse''' and '''compile''' it, | ||
| Line 37: | Line 44: | ||
|width="10*" | [[Swordfish_Documentation:_DevelopCXFSwordfishBundle | Develop JAX-WS Swordfish Bundle]] | |width="10*" | [[Swordfish_Documentation:_DevelopCXFSwordfishBundle | Develop JAX-WS Swordfish Bundle]] | ||
|- | |- | ||
| + | |width="10*" | S030 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''run a JAX-WS Service Bundle in Eclipse''', | |width="10*" | '''run a JAX-WS Service Bundle in Eclipse''', | ||
| Line 42: | Line 50: | ||
|width="10*" | [[Swordfish_Documentation:_RunCXFSwordfishBundle | Run JAX-WS Swordfish Bundle]] | |width="10*" | [[Swordfish_Documentation:_RunCXFSwordfishBundle | Run JAX-WS Swordfish Bundle]] | ||
|- | |- | ||
| + | |width="10*" | S035 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''bundle Business Participant with necessary Swordfish Artefacts''', | |width="10*" | '''bundle Business Participant with necessary Swordfish Artefacts''', | ||
| Line 47: | Line 56: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S040 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''run''' a JAX-WS Service Consumer in a Servlet Engine, | |width="10*" | '''run''' a JAX-WS Service Consumer in a Servlet Engine, | ||
| Line 52: | Line 62: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S045 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''use JAX-WS plugin fragment''' for new Plugin project wizard, | |width="10*" | '''use JAX-WS plugin fragment''' for new Plugin project wizard, | ||
| Line 57: | Line 68: | ||
|width="10*" | [[Swordfish_Documentation:_CXFBunldeFragment | Use JAX-WS Plugin Fragment]] | |width="10*" | [[Swordfish_Documentation:_CXFBunldeFragment | Use JAX-WS Plugin Fragment]] | ||
|- | |- | ||
| + | |width="10*" | S050 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | want to '''be guided through examples/tutorials''' for implemtation and running JAX-WS services with Swordfish, | |width="10*" | want to '''be guided through examples/tutorials''' for implemtation and running JAX-WS services with Swordfish, | ||
| Line 62: | Line 74: | ||
|width="10*" | Not a Backlog Item but part of [[Swordfish_Documentation:_Feature_Completenes_Definition |Feature completeness criteria]] | |width="10*" | Not a Backlog Item but part of [[Swordfish_Documentation:_Feature_Completenes_Definition |Feature completeness criteria]] | ||
|- | |- | ||
| + | |width="10*" | S055 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''deploy''' a JAX-WS Service Participant into the running Target Platform outside of Eclipse, | |width="10*" | '''deploy''' a JAX-WS Service Participant into the running Target Platform outside of Eclipse, | ||
| Line 67: | Line 80: | ||
|width="10*" | See also user story for deployment in tooling list below. For dynamic configuration: [[Swordfish_Documentation:_OSGi_Configuration_Agent | OSGi configuration Agent]] | |width="10*" | See also user story for deployment in tooling list below. For dynamic configuration: [[Swordfish_Documentation:_OSGi_Configuration_Agent | OSGi configuration Agent]] | ||
|- | |- | ||
| + | |width="10*" | S060 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''select the consumer policy''' dynamically, | |width="10*" | '''select the consumer policy''' dynamically, | ||
| Line 72: | Line 86: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S065 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''start''' a JAX-WS Service Provider in the Target Platform outside of Eclipse, | |width="10*" | '''start''' a JAX-WS Service Provider in the Target Platform outside of Eclipse, | ||
| Line 77: | Line 92: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S070 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''start''' a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse, | |width="10*" | '''start''' a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse, | ||
| Line 82: | Line 98: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S075 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | Get thw WSDL from a URL of a deployed service | |width="10*" | Get thw WSDL from a URL of a deployed service | ||
| Line 87: | Line 104: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S080 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''debug''' my JAX-WS services related to the SOA infrastructure based on '''clearly understandable, well structured error messages''', | |width="10*" | '''debug''' my JAX-WS services related to the SOA infrastructure based on '''clearly understandable, well structured error messages''', | ||
| Line 92: | Line 110: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S085 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''utilize message streaming''', | |width="10*" | '''utilize message streaming''', | ||
| Line 97: | Line 116: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S090 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run in Equinox (J2SE) (WSDL first), | |width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run in Equinox (J2SE) (WSDL first), | ||
| Line 102: | Line 122: | ||
|width="10*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | |width="10*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | ||
|- | |- | ||
| + | |width="10*" | S095 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''generate''' JAX-WS Service '''Providers from WSDL''' which can run in Equinox (J2SE)(WSDL first). | |width="10*" | '''generate''' JAX-WS Service '''Providers from WSDL''' which can run in Equinox (J2SE)(WSDL first). | ||
| Line 107: | Line 128: | ||
|width="10*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | |width="10*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | ||
|- | |- | ||
| + | |width="10*" | S100 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''retrieve''' the WSDL for Code generation out of Eclipse from the '''Service Registry''', | |width="10*" | '''retrieve''' the WSDL for Code generation out of Eclipse from the '''Service Registry''', | ||
| Line 112: | Line 134: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S105 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''deploy''' a J2SE JAX-WS Service Participant from my Eclipse Workspace into the Target Platform outside of Eclipse, | |width="10*" | '''deploy''' a J2SE JAX-WS Service Participant from my Eclipse Workspace into the Target Platform outside of Eclipse, | ||
| Line 117: | Line 140: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S110 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''generate WSDL''' for a JAX-WS Service '''from code'''(code first generation). | |width="10*" | '''generate WSDL''' for a JAX-WS Service '''from code'''(code first generation). | ||
| Line 122: | Line 146: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S115 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run in a '''Servlet Container (Web)''', | |width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run in a '''Servlet Container (Web)''', | ||
| Line 127: | Line 152: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S120 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''generate''' JAX-WS Service '''Provider from WSDL''' which can run in a '''Servlet Container (Web)''', | |width="10*" | '''generate''' JAX-WS Service '''Provider from WSDL''' which can run in a '''Servlet Container (Web)''', | ||
| Line 132: | Line 158: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S125 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''use jms as transport protocol''', | |width="10*" | '''use jms as transport protocol''', | ||
| Line 137: | Line 164: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S130 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''test''' my Service Consumer whithout having implemented a Service Provider, | |width="10*" | '''test''' my Service Consumer whithout having implemented a Service Provider, | ||
| Line 142: | Line 170: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S135 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''test''' my Service Provider whithout having implemented a Service Consumer, | |width="10*" | '''test''' my Service Provider whithout having implemented a Service Consumer, | ||
| Line 147: | Line 176: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S140 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''reference message schemas from the WSDL''', | |width="10*" | '''reference message schemas from the WSDL''', | ||
| Line 152: | Line 182: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S145 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''retreive''' Service artifacts (Service Description, Policy) '''from Service Registry''' for test executions, | |width="10*" | '''retreive''' Service artifacts (Service Description, Policy) '''from Service Registry''' for test executions, | ||
| Line 157: | Line 188: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S150 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''develop simple test scripts''' for my service, | |width="10*" | '''develop simple test scripts''' for my service, | ||
| Line 162: | Line 194: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S155 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''edit''' Service related spring configuration based on Swordfish semantics, | |width="10*" | '''edit''' Service related spring configuration based on Swordfish semantics, | ||
| Line 167: | Line 200: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S160 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run in an '''JEE Application Server''', | |width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run in an '''JEE Application Server''', | ||
| Line 172: | Line 206: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S170 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''generate''' JAX-WS Service '''Provider from WSDL''' which can run in an '''JEE Application Server''', | |width="10*" | '''generate''' JAX-WS Service '''Provider from WSDL''' which can run in an '''JEE Application Server''', | ||
| Line 177: | Line 212: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S180 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''run''' a JAX-WS Service Consumer in a JEE Application Server outside of Eclipse, | |width="10*" | '''run''' a JAX-WS Service Consumer in a JEE Application Server outside of Eclipse, | ||
| Line 182: | Line 218: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S190 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''start''' a JAX-WS Service Provider in a JEE Application Server | |width="10*" | '''start''' a JAX-WS Service Provider in a JEE Application Server | ||
| Line 187: | Line 224: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S200 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''use any other transport protocol offered by ServiceMix''', | |width="10*" | '''use any other transport protocol offered by ServiceMix''', | ||
| Line 192: | Line 230: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
| + | |width="10*" | S210 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''upgrade''' an existing development environment with Swordfis and SOA Tools | |width="10*" | '''upgrade''' an existing development environment with Swordfis and SOA Tools | ||
Revision as of 02:35, 3 April 2009
| ID | As an | I would like to | so that | link to backlog item(s) |
| S001 | Eclipse Service Developer | use the target platformprovisioning P2 repository to download a released version of Swordfish, | I can install swordfish and set it as target platform.. | Swordfish Eclipse Features from download site |
| S005 | Eclipse Service Developer | install Swordfish Tools into my existing Eclipse IDE, | I can start developing services quickly AND continue to use plugins I have already. | Set Swordfish as target patform |
| S010 | Eclipse Service Developer | run a JAX-WS Service Participant within Eclipse Equinox, | I can test my code immediately | Integrate Apache CXF |
| S015 | Eclipse Service Developer | use the http and https transport protocols, | I can communicate over the web. | Integrate Apache CXF |
| S020 | 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 |
| S025 | Eclipse Service Developer | write a JAX-WS Service using Eclipse and compile it, | I can get started with Swordfish Service development. | Develop JAX-WS Swordfish Bundle |
| S030 | Eclipse Service Developer | run a JAX-WS Service Bundle in Eclipse, | I can check my Service Bundle within the development environment. | Run JAX-WS Swordfish Bundle |
| S035 | Eclipse Service Developer | bundle Business Participant with necessary Swordfish Artefacts, | I can work with one single bundle during deployment. | TBD |
| S040 | Eclipse Service Developer | run a JAX-WS Service Consumer in a Servlet Engine, | I can test my code immediately | TBD |
| S045 | Eclipse Service Developer | use JAX-WS plugin fragment for new Plugin project wizard, | I can start with my ready-made example. | Use JAX-WS Plugin Fragment |
| S050 | Eclipse Service Developer | want to be guided through examples/tutorials for implemtation and running JAX-WS services with Swordfish, | I can get started easily | Not a Backlog Item but part of Feature completeness criteria |
| S055 | Eclipse Service Developer | deploy a 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). | See also user story for deployment in tooling list below. For dynamic configuration: OSGi configuration Agent |
| S060 | Eclipse Service Developer | select the consumer policy dynamically, | I can invoke service calls with different policies from the same consumer | TBD |
| S065 | Eclipse Service Developer | start a JAX-WS Service Provider in the Target Platform outside of Eclipse, | I can test my code in a distributed environment. | TBD |
| S070 | 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 |
| S075 | Eclipse Service Developer | Get thw WSDL from a URL of a deployed service | I can save it into my local workspace. | TBD |
| S080 | Eclipse Service Developer | debug my JAX-WS services related to the SOA infrastructure based on clearly understandable, well structured error messages, | I do not get lost in lengthy meaningless logs. | TBD |
| S085 | Eclipse Service Developer | utilize message streaming, | I can provide high performance applications with low roundtrip times even for larger amounts of data transferred. | TBD |
| S090 | Eclipse Service Developer | generate JAX-WS Service Consumers from WSDL which can run in Equinox (J2SE) (WSDL first), | I can implement the business logic without taking care about Service Proxy or any other SOA infrastructure releated code. | JAX-WS Code Generation |
| S095 | Eclipse Service Developer | generate JAX-WS Service Providers from WSDL which can run in Equinox (J2SE)(WSDL first). | I can implement the business logic without taking care about the Service Skeleton or any other SOA infrastructure releated code. | JAX-WS Code Generation |
| S100 | Eclipse Service Developer | retrieve the WSDL for Code generation out of Eclipse from the Service Registry, | I do not need to download and generate in two steps. | TBD |
| S105 | Eclipse Service Developer | deploy a J2SE JAX-WS Service Participant from my Eclipse Workspace into the Target Platform outside of Eclipse, | I can test my code immediately in a distributed environment. | TBD |
| S110 | Eclipse Service Developer | generate WSDL for a JAX-WS Service from code(code first generation). | I can publish my WSDL easily into Service Registry from implemented code. | TBD |
| S115 | Eclipse Service Developer | generate JAX-WS Service Consumers from WSDL which can run in a Servlet Container (Web), | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | TBD |
| S120 | Eclipse Service Developer | generate JAX-WS Service Provider from WSDL which can run in a Servlet Container (Web), | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | TBD |
| S125 | Eclipse Service Developer | use jms as transport protocol, | I can provide a reliable transport. | TBD |
| S130 | Eclipse Service Developer | test my Service Consumer whithout having implemented a Service Provider, | I can start testing early AND implement consumer and provider independently. | TBD |
| S135 | Eclipse Service Developer | test my Service Provider whithout having implemented a Service Consumer, | I can start testing early AND implement consumer and provider independently. | TBD |
| S140 | 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 |
| S145 | Eclipse Service Developer | retreive Service artifacts (Service Description, Policy) from Service Registry for test executions, | I do not need to download and test in two steps. | TBD |
| S150 | Eclipse Service Developer | develop simple test scripts for my service, | I can run basic regression tests of all Service Operations with a variety of transports and policies during progressing implementation. | TBD |
| S155 | Eclipse Service Developer | edit Service related spring configuration based on Swordfish semantics, | I can ensure my service will run in Swordfish. | TBD |
| S160 | Eclipse Service Developer | generate JAX-WS Service Consumers from WSDL which can run in an JEE Application Server, | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | TBD |
| S170 | Eclipse Service Developer | generate JAX-WS Service Provider from WSDL which can run in an JEE Application Server, | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | TBD |
| S180 | 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 |
| S190 | 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 |
| S200 | 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 |
| S210 | Eclipse Service Developer | upgrade an existing development environment with Swordfis and SOA Tools | I can use the latest version. | TBD |
See also: Swordfish Product Backlog
Return to Swordfish User Stories
Return to Swordfish Wiki Home