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"
(add link to configuration agent) |
m |
||
(34 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
{| border="1" cellpadding="3" cellspacing="0" width="100%" | {| border="1" cellpadding="3" cellspacing="0" width="100%" | ||
− | == User Stories for Service Developers | + | == User Stories for Service Developers == |
− | |- style="background:# | + | |- style="background:#DFF4B3;" |
+ | |width="10*" |'''ID/Bug''' | ||
|width="10*" |'''As an''' | |width="10*" |'''As an''' | ||
|width="10*" |'''I would like to''' | |width="10*" |'''I would like to''' | ||
|width="10*" |'''so that''' | |width="10*" |'''so that''' | ||
− | |width="10*" |link to backlog item(s) | + | |width="10*" |Topic and/or link to backlog item(s) |
+ | |width="10*" |Status | ||
|- | |- | ||
+ | |width="10*" id="S001"| S001 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | '''download''' a released version of Swordfish | + | |width="10*" | use the target platformprovisioning P2 repository to '''download''' a released version of Swordfish, |
− | |width="10*" | I can | + | |width="10*" | I can '''install''' swordfish and set it as target platform.. |
|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*" | <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |width="10*" | S005 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | | + | |width="10*" | '''install''' Swordfish Tools into my existing Eclipse IDE, |
− | |width="10*" | I can | + | |width="10*" | I can start developing services quickly AND continue to use plugins I have already. |
− | |width="10*" | | + | |width="10*" | [[Swordfish_Documentation:_SwordfishPlatform | Set Swordfish as target patform]] |
− | + | |width="10*" | <font b color=green><b> Done </b></font> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | |width="10*" | | + | |
− | + | ||
− | + | ||
− | + | ||
|- | |- | ||
+ | |width="10*" | S010 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | '''run''' a JAX-WS Service Participant | + | |width="10*" | '''run''' a JAX-WS Service Participant within Eclipse Equinox, |
|width="10*" | I can test my code immediately | |width="10*" | I can test my code immediately | ||
|width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | |width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | ||
+ | |width="10*" | <br/> <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |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''', | ||
|width="10*" | I can communicate over the web. | |width="10*" | I can communicate over the web. | ||
|width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | |width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | ||
+ | |width="10*" | <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |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''' | ||
|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*" | [[Swordfish_Documentation:_Registry_Feature | Service Registry Feature]] | |width="10*" | [[Swordfish_Documentation:_Registry_Feature | Service Registry Feature]] | ||
+ | |width="10*" | <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |width="10*" | S025 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''write''' a JAX-WS Service '''using Eclipse''' and '''compile''' it, |
− | |width="10*" | I can | + | |width="10*" | I can get started with Swordfish Service development. |
− | |width="10*" | | + | |width="10*" | [[Swordfish_Documentation:_DevelopCXFSwordfishBundle | Develop JAX-WS Swordfish Bundle]] |
+ | |width="10*" | <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |width="10*" Id="S026"| S026 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''create a Swordfish-CXF service descriptor''' using the Eclipse Wizard , |
− | |width="10*" | I can | + | |width="10*" | so that I can start developing services the way I used to in Eclipse. |
− | |width="10*" | | + | |width="10*" | New CXF service description file wizard |
+ | |width="10*" | <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |width="10*" Id="S027"| S027 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''edit''' a existing Swordfish-CXF service descriptor, |
− | |width="10*" | I can | + | |width="10*" | so that I can add/modify/delete my services declaration without prior Spring knowledge. |
− | |width="10*" | | + | |width="10*" | CXF Service Description Editor |
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" | S030 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''run a JAX-WS Service Bundle in Eclipse''', |
− | |width="10*" | I can | + | |width="10*" | I can check my Service Bundle within the development environment. |
− | |width="10*" | | + | |width="10*" | [[Swordfish_Documentation:_RunCXFSwordfishBundle | Run JAX-WS Swordfish Bundle]] |
+ | |width="10*" | <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |width="10*" id="S035"| S035 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''bundle Business Participant with necessary Swordfish Artefacts''', |
− | |width="10*" | I can | + | |width="10*" | I can work with one single bundle during deployment. |
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |width="10*" | S040 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''run''' a JAX-WS Service Consumer in a Servlet Engine, |
− | |width="10*" | I can test my code | + | |width="10*" | I can test my code immediately |
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" | S045 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | | + | |width="10*" | '''use JAX-WS plugin fragment''' for new Plugin project wizard, |
− | |width="10*" | I can | + | |width="10*" | I can start with my ready-made example. |
− | |width="10*" | | + | |width="10*" | [[Swordfish_Documentation:_CXFBunldeFragment | Use JAX-WS Plugin Fragment]] |
+ | |width="10*" | <br/> <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |width="10*" | S050 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | want to '''be guided through examples/tutorials''' for implemtation and running JAX-WS services with Swordfish, |
− | |width="10*" | | + | |width="10*" | I can get started easily |
− | |width="10*" | | + | |width="10*" | Not a Backlog Item but part of [[Swordfish_Documentation:_Feature_Completenes_Definition |Feature completeness criteria]] |
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" | S055 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''deploy''' a JAX-WS Service Participant into the running Target Platform outside of Eclipse, |
− | |width="10*" | I | + | |width="10*" | I can test my code immediately without needing to restart the target platform (hot deployment). |
− | |width="10*" | | + | |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*" | Open | ||
|- | |- | ||
+ | |width="10*" id="S059"| S059 <br/> <font b color=purple><b> Sprint 5, Rank 3</b></font> | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | have '''an exemplary policy''' which is implemented for service lookup as well as for processing in an interceptor, |
− | |width="10*" | I can | + | |width="10*" | I can understand the complete chain of policy processing. |
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" | S060 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''select the consumer policy''' dynamically, |
− | |width="10*" | I can | + | |width="10*" | I can invoke service calls with different policies from the same consumer |
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" id="S061"| S061 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | I want to use '''authentication''' based on WS-Trust, |
− | |width="10*" | I can | + | |width="10*" | I can use a centralized SAML Token Service. |
− | |width="10*" | | + | |width="10*" | [[Swordfish_Documentation:_Product_Backlog#0300 | Centralized Authentication and Authorization]] |
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" id="S062"| S062 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | I want to use policy controled '''authorization''', |
− | |width="10*" | I can | + | |width="10*" | I can cntrol acess rights for my services. |
− | |width="10*" | | + | |width="10*" | [[Swordfish_Documentation:_Product_Backlog#0300 | Centralized Authentication and Authorization]] |
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" | S065 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | | + | |width="10*" | '''start''' a JAX-WS Service Provider in the Target Platform outside of Eclipse, |
− | |width="10*" | | + | |width="10*" | I can test my code in a distributed environment. |
|width="10*" | TBD | |width="10*" | TBD | ||
− | + | |width="10*" | Open | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | |width="10*" | | + | |
|- | |- | ||
+ | |width="10*" | S070 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''start''' a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse, |
− | |width="10*" | I can | + | |width="10*" | I can test my code in a distributed environment. |
− | |width="10*" | | + | |width="10*" | TBD |
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" id="S075"| S075 <br/>[https://bugs.eclipse.org/271337 #271337] | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''view and save WSDL''' of my newly developed JAS-WS service deployed in Swordfish |
− | |width="10*" | I can | + | |width="10*" | I can use it for testing. |
− | |width="10*" | | + | |width="10*" | TBD |
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" id="S080"| S080 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''debug''' my JAX-WS services related to the SOA infrastructure based on '''clearly understandable, well structured error messages''', |
− | |width="10*" | I | + | |width="10*" | I do not get lost in lengthy meaningless logs. |
− | |width="10*" | | + | |width="10*" | TBD |
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" | S085 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | ''' | + | |width="10*" | '''utilize message streaming''', |
− | |width="10*" | I can | + | |width="10*" | I can provide high performance applications with low roundtrip times even for larger amounts of data transferred. |
− | |width="10*" | | + | |width="10*" | TBD |
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" id="S090" | S090 | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run | + | |width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run in Equinox (J2SE) (WSDL first), |
|width="10*" | I can implement the business logic without taking care about Service Proxy or any other SOA infrastructure releated code. | |width="10*" | I can implement the business logic without taking care about Service Proxy or any other SOA infrastructure releated code. | ||
− | |width="10*" | | + | |width="10*" | May be achieved through existing tools not part of Swordfish |
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" id="S095"| S095 <br/> <font b color=purple><b> Sprint 5, Rank 1</b></font> | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | '''generate''' JAX-WS Service '''Providers from WSDL''' which can run | + | |width="10*" | '''generate''' JAX-WS Service '''Providers from WSDL''' which can run in Equinox (J2SE)(WSDL first). |
|width="10*" | I can implement the business logic without taking care about the Service Skeleton or any other SOA infrastructure releated code. | |width="10*" | I can implement the business logic without taking care about the Service Skeleton or any other SOA infrastructure releated code. | ||
|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*" | <br/> <font b color=green><b> Done </b></font> | ||
|- | |- | ||
+ | |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''', | ||
|width="10*" | I do not need to download and generate in two steps. | |width="10*" | I do not need to download and generate in two steps. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |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, | ||
|width="10*" | I can test my code immediately in a distributed environment. | |width="10*" | I can test my code immediately in a distributed environment. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |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). | ||
− | |width="10*" | I can | + | |width="10*" | I can publish my WSDL easily into Service Registry from implemented code. |
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |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)''', | ||
|width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | |width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |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)''', | ||
|width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | |width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" | S125 | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''use jms as transport protocol''', | ||
+ | |width="10*" | I can provide a reliable transport. | ||
+ | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
+ | |- | ||
+ | |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, | ||
|width="10*" | I can start testing early AND implement consumer and provider independently. | |width="10*" | I can start testing early AND implement consumer and provider independently. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |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, | ||
|width="10*" | I can start testing early AND implement consumer and provider independently. | |width="10*" | I can start testing early AND implement consumer and provider independently. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" | S140 | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''reference message schemas from the WSDL''', | ||
+ | |width="10*" | 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. | ||
+ | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
+ | |- | ||
+ | |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, | ||
|width="10*" | I do not need to download and test in two steps. | |width="10*" | I do not need to download and test in two steps. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |width="10*" | S146 | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''generate''' XML requests on the base of the WSDL and/or schema for test executions, | ||
+ | |width="10*" | I do not need to create the test requests manually. | ||
+ | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
+ | |- | ||
+ | |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, | ||
|width="10*" | I can run basic regression tests of all Service Operations with a variety of transports and policies during progressing implementation. | |width="10*" | I can run basic regression tests of all Service Operations with a variety of transports and policies during progressing implementation. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |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, | ||
|width="10*" | I can ensure my service will run in Swordfish. | |width="10*" | I can ensure my service will run in Swordfish. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |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''', | ||
|width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | |width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
|- | |- | ||
+ | |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''', | ||
|width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | |width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
− | |-} | + | |width="10*" | Open |
+ | |- | ||
+ | |width="10*" | S180 | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''run''' a JAX-WS Service Consumer in a JEE Application Server outside of Eclipse, | ||
+ | |width="10*" | I can test my code in a distributed environment. | ||
+ | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
+ | |- | ||
+ | |width="10*" | S190 | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''start''' a JAX-WS Service Provider in a JEE Application Server | ||
+ | |width="10*" | I can test my code in a distributed JEE environment. | ||
+ | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
+ | |- | ||
+ | |width="10*" | S200 | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''use any other transport protocol offered by ServiceMix''', | ||
+ | |width="10*" | I can integrate easier with legacy Systems. (I am aware that restrictions apply regarding policies influencing the wire format.) | ||
+ | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
+ | |- | ||
+ | |width="10*" | S210 | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''upgrade''' an existing development environment with Swordfish and SOA Tools | ||
+ | |width="10*" | I can use the latest version. | ||
+ | |width="10*" | TBD | ||
+ | |width="10*" | Open | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | |||
+ | See also: [[Swordfish_Documentation:_Product_Backlog| Swordfish Product Backlog]] | ||
+ | |||
+ | ------------------ | ||
+ | Return to [[Swordfish_Documentation:_User_Stories | Swordfish User Stories]] <br/> | ||
+ | Return to [[Swordfish | Swordfish Wiki Home]] |
Latest revision as of 02:53, 3 June 2009
ID/Bug | As an | I would like to | so that | Topic and/or link to backlog item(s) | Status |
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 | Done |
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 | Done |
S010 | Eclipse Service Developer | run a JAX-WS Service Participant within Eclipse Equinox, | I can test my code immediately | Integrate Apache CXF | Done |
S015 | Eclipse Service Developer | use the http and https transport protocols, | I can communicate over the web. | Integrate Apache CXF | Done |
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 | Done |
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 | Done |
S026 | Eclipse Service Developer | create a Swordfish-CXF service descriptor using the Eclipse Wizard , | so that I can start developing services the way I used to in Eclipse. | New CXF service description file wizard | Done |
S027 | Eclipse Service Developer | edit a existing Swordfish-CXF service descriptor, | so that I can add/modify/delete my services declaration without prior Spring knowledge. | CXF Service Description Editor | Open |
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 | Done |
S035 | Eclipse Service Developer | bundle Business Participant with necessary Swordfish Artefacts, | I can work with one single bundle during deployment. | TBD | Done |
S040 | Eclipse Service Developer | run a JAX-WS Service Consumer in a Servlet Engine, | I can test my code immediately | TBD | Open |
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 | Done |
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 | Open |
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 | Open |
S059 Sprint 5, Rank 3 |
Eclipse Service Developer | have an exemplary policy which is implemented for service lookup as well as for processing in an interceptor, | I can understand the complete chain of policy processing. | TBD | Open |
S060 | Eclipse Service Developer | select the consumer policy dynamically, | I can invoke service calls with different policies from the same consumer | TBD | Open |
S061 | Eclipse Service Developer | I want to use authentication based on WS-Trust, | I can use a centralized SAML Token Service. | Centralized Authentication and Authorization | Open |
S062 | Eclipse Service Developer | I want to use policy controled authorization, | I can cntrol acess rights for my services. | Centralized Authentication and Authorization | Open |
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 | Open |
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 | Open |
S075 #271337 |
Eclipse Service Developer | view and save WSDL of my newly developed JAS-WS service deployed in Swordfish | I can use it for testing. | TBD | Open |
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 | Open |
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 | Open |
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. | May be achieved through existing tools not part of Swordfish | Open |
S095 Sprint 5, Rank 1 |
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 | Done |
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 | Open |
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 | Open |
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 | Open |
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 | Open |
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 | Open |
S125 | Eclipse Service Developer | use jms as transport protocol, | I can provide a reliable transport. | TBD | Open |
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 | Open |
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 | Open |
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 | Open |
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 | Open |
S146 | Eclipse Service Developer | generate XML requests on the base of the WSDL and/or schema for test executions, | I do not need to create the test requests manually. | TBD | Open |
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 | Open |
S155 | Eclipse Service Developer | edit Service related spring configuration based on Swordfish semantics, | I can ensure my service will run in Swordfish. | TBD | Open |
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 | Open |
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 | Open |
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 | Open |
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 | Open |
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 | Open |
S210 | Eclipse Service Developer | upgrade an existing development environment with Swordfish and SOA Tools | I can use the latest version. | TBD | Open |
See also: Swordfish Product Backlog
Return to Swordfish User Stories
Return to Swordfish Wiki Home