|
Size: 2965
Comment:
|
Size: 4505
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| Line 9: | Line 8: |
| Assigned:: TSH | Assigned:: BAM + JRG |
| Line 14: | Line 13: |
| Prev assigned:: | Prev assigned:: ABR (description) |
| Line 20: | Line 19: |
| Tasks adressed:: ["TaskX/1"] | Tasks adressed:: ["TaskB.5"] |
| Line 26: | Line 25: |
| Time estimated:: not done | Time estimated:: 3md |
| Line 32: | Line 31: |
| Time used:: 0md |
Time used:: 6h |
| Line 43: | Line 41: |
| Status:: Not described |
Status:: In progress |
| Line 59: | Line 55: |
| == The Problem == | |
| Line 60: | Line 57: |
| The interface to DOMS is exclusively through SOAP-based webservices. These webservices must have a uniform and documented interface, that is not dependent on any particular client lanquage. For that purpose we have decided to use WSDL. For all the webservices in DOMS, we must write a wsdl, which should be used to generate the rest of the service from. Change testbed to give copies of these WSDLs rather than genrating new ones. For the already completed services, we could autogenerate one from the java interfaces, but it must subsequently be reformatted and documented. This is a general note, the wsdls must use documentation tags whenever they are appropriate. They are the interface to the outside, and must contain explicit documentation. All wsdls must use the binding style "document" and the "literal" use. If possible, use the wrapped style, but this does not allow for overloaded operations. Avoid passing complex objects as input, but complex objects will be passed as output. Document these objects extensively. == Progress == The webservices in question: || Service || Status || Notes || || Bitstorage || documented wsdl done || review done || || Filecharacterizer || documented wsdl done || review needed || || Pidgenerator || documented wsdl done || review done || || Search || dunno || || We are also missing the wsdl2Java functionality. And the 'provide documented wsdl' functionality. Currently the automatically generated wsdl is provided. == Conclusion == |
Action WSDL2Java
- Assigned
- BAM + JRG
- Prev assigned
- ABR (description)
- Tasks adressed
- ["TaskB.5"]
- Time estimated
- 3md
- Time used
- 6h
- Priority
- 3
- Status
- In progress
- Iteration
- 13
- Notes
The Problem
The interface to DOMS is exclusively through SOAP-based webservices. These webservices must have a uniform and documented interface, that is not dependent on any particular client lanquage. For that purpose we have decided to use WSDL.
For all the webservices in DOMS, we must write a wsdl, which should be used to generate the rest of the service from. Change testbed to give copies of these WSDLs rather than genrating new ones.
For the already completed services, we could autogenerate one from the java interfaces, but it must subsequently be reformatted and documented. This is a general note, the wsdls must use documentation tags whenever they are appropriate. They are the interface to the outside, and must contain explicit documentation.
All wsdls must use the binding style "document" and the "literal" use. If possible, use the wrapped style, but this does not allow for overloaded operations. Avoid passing complex objects as input, but complex objects will be passed as output. Document these objects extensively.
Progress
The webservices in question:
Service |
Status |
Notes |
Bitstorage |
documented wsdl done |
review done |
Filecharacterizer |
documented wsdl done |
review needed |
Pidgenerator |
documented wsdl done |
review done |
Search |
dunno |
|
We are also missing the wsdl2Java functionality.
And the 'provide documented wsdl' functionality. Currently the automatically generated wsdl is provided.
Conclusion
Checklist For Working On An Action
The Life Cycle of an Action:
Assign people for action definition: Done at start of iteration status meeting. Fill out Assigned
Define the action: Describe information about what is to be done and how. Fill out Tasks Addressed and Time Estimated.
Review the definition: Get another project group member to review the action definition, and update it.
Assign people for action implementation: Done by project manager, usually the same persons who wrote the definition. Fill out Assigned and Prev assigned if new persons are assigned.
Implement the action: See details below
Review the action: Get another project group member to review what is implemented (code and documentation), and update it.
Finish the action: Change the status to "Finished" and update the "time used" field on the action page.
Please make sure that you address the below issues, when working on an action:
- Update the state of the action to "In Progress" when you start working on it.
- Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.
Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. Hint: Continually updating the "Time used" field will make it easier for you.
- Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.