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"
m |
(merged and reprioritized. added Upgrade, and WSDL from deployed service stories) |
||
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:#DFF4B3;" | |- style="background:#DFF4B3;" | ||
|width="10*" |'''As an''' | |width="10*" |'''As an''' | ||
Line 13: | Line 13: | ||
|- | |- | ||
|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 continue to use plugins I have already. |
− | |width="10*" | | + | |width="10*" | [[Swordfish_Documentation:_SwordfishPlatform | Set Swordfish as target patform]] |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
Line 44: | Line 33: | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | '''run''' a JAX-WS Service Consumer in a Servlet Engine | + | |width="10*" | '''write''' a JAX-WS Service '''using Eclipse''' and '''compile''' it, |
+ | |width="10*" | I can get started with Swordfish Service development. | ||
+ | |width="10*" | [[Swordfish_Documentation:_DevelopCXFSwordfishBundle | Develop JAX-WS Swordfish Bundle]] | ||
+ | |- | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''run a JAX-WS Service Bundle in Eclipse''', | ||
+ | |width="10*" | I can check my Service Bundle within the development environment. | ||
+ | |width="10*" | [[Swordfish_Documentation:_RunCXFSwordfishBundle | Run JAX-WS Swordfish Bundle]] | ||
+ | |- | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''bundle Business Participant with necessary Swordfish Artefacts''', | ||
+ | |width="10*" | I can work with one single bundle during deployment. | ||
+ | |width="10*" | TBD | ||
+ | |- | ||
+ | |width="10*" | Eclipse Service Developer | ||
+ | |width="10*" | '''run''' a JAX-WS Service Consumer in a Servlet Engine, | ||
|width="10*" | I can test my code immediately | |width="10*" | I can test my code immediately | ||
|width="10*" | TBD | |width="10*" | TBD | ||
+ | |- | ||
+ | |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*" | I can get started easily | ||
+ | |width="10*" | Not a Backlog Item but part of [[Swordfish_Documentation:_Feature_Completenes_Definition |Feature completeness criteria]] | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
Line 74: | Line 83: | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | | + | |width="10*" | Get thw WSDL from a URL of a deployed service |
− | |width="10*" | I can | + | |width="10*" | I can save it into my local workspace. |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
Line 91: | Line 95: | ||
|width="10*" | '''utilize message streaming''', | |width="10*" | '''utilize message streaming''', | ||
|width="10*" | I can provide high performance applications with low roundtrip times even for larger amounts of data transferred. | |width="10*" | I can provide high performance applications with low roundtrip times even for larger amounts of data transferred. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
Line 156: | Line 108: | ||
|- | |- | ||
|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*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | |width="10*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | ||
|- | |- | ||
|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]] | ||
Line 188: | Line 140: | ||
|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*" | 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*" | TBD | ||
|- | |- | ||
Line 223: | Line 180: | ||
|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*" | 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*" | 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*" | 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*" | Eclipse Service Developer | ||
+ | |width="10*" | '''upgrade''' an existing development environment with Swordfis and SOA Tools | ||
+ | |width="10*" | I can use the latest version. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- |
Revision as of 16:29, 2 April 2009
As an | I would like to | so that | link to backlog item(s) |
Eclipse Service Developer | download a released version of Swordfish form the Eclipse Download site, | I can use the usual eclipse mechanism for getting new versions and installling them. | Swordfish Eclipse Features from download site |
Eclipse Service Developer | install Swordfish Tools into my existing Eclipse IDE, | I can continue to use plugins I have already. | Set Swordfish as target patform |
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 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 | write a JAX-WS Service using Eclipse and compile it, | I can get started with Swordfish Service development. | Develop JAX-WS Swordfish Bundle |
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 |
Eclipse Service Developer | bundle Business Participant with necessary Swordfish Artefacts, | I can work with one single bundle during deployment. | TBD |
Eclipse Service Developer | run a JAX-WS Service Consumer in a Servlet Engine, | I can test my code immediately | TBD |
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 |
Eclipse Service Developer | use jms as transport protocol, | I can provide a reliable transport. | 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). | See also user story for deployment in tooling list below. For dynamic configuration: OSGi configuration Agent |
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 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 | Get thw WSDL from a URL of a deployed service | I can save it into my local workspace. | TBD |
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 |
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 | export my CXF Swordfish bundle as JAR file, | I can deploy it into different environments. | Export JAX-WS Swordfish Bundle as JAR |
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 |
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 |
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 |
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 |
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 |
Eclipse Service Developer | generate WSDL for a JAX-WS Service from code(code first generation). | I can implement the Service without needing to create the WSDL manually. | TBD |
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 |
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 |
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 | test my Service Consumer whithout having implemented a Service Provider, | I can start testing early AND implement consumer and provider independently. | TBD |
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 |
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 |
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 |
Eclipse Service Developer | edit Service related spring configuration based on Swordfish semantics, | I can ensure my service will run in Swordfish. | TBD |
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 |
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 |
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 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 | 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