eclipse-ee4j / eclipse-ee4j/metro-wsit
These docs need update
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
1.[https://wsit-docs.dev.java.net/releases/1.2/install.html](https://wsit-docs.dev.java.net/releases/1.2/install.html) requires complete
overhauling. Need a new section for installing metro on V3
2\. Can someone change this page to reflect correct versions?
[https://metro.dev.java.net/guide/Metro_Specifications.html](https://metro.dev.java.net/guide/Metro_Specifications.html)
3\. Chapter 5 "HTTP Cookies" issues found here . The section 5.3.2 says "TODO".
No content is seen in this section .
4\. [https://metro.dev.java.net/guide/Large_Attachments.html](https://metro.dev.java.net/guide/Large_Attachments.html) says "The programming
model is based on MTOM and DataHandler. You want to send large data as a SOAP
attachment, see for more details. Also .." in the second para. Its confusing as
users wouldnt know what see. Need some clarification here.
5.
[https://wsit.dev.java.net/source/browse/*checkout*/wsit/wsit/status-notes/status-notes-1-4-FCS.html](https://wsit.dev.java.net/source/browse/*checkout*/wsit/wsit/status-notes/status-notes-1-4-FCS.html)
is not present
6\. [https://metro.dev.java.net/guide/Building_and_Deploying_the_Web_Service.html](https://metro.dev.java.net/guide/Building_and_Deploying_the_Web_Service.html)
Comment: use of word WSIT vs. Metro ?U
ses the word WSIT, should be using Metro?
i.e. "Once configured, you can build and deploy a WSIT-enabled web
service ..." should it be "Once configured, you can build and deploy a
Metro-enabled web service ..." or is this fine as is? i.e. WSIT is a
sub-component of Metro stack?
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[1.4]
Source: [https://github.com/javaee/metro-wsit/issues/1050](https://github.com/javaee/metro-wsit/issues/1050)
Author: glassfishrobot
Contributor guide
Research direction
Review the linked installation, Metro Specifications, HTTP Cookies, Large Attachments, status-notes, and Building and Deploying the Web Service pages first. Verify which pages still exist and which versions and terminology are current, then define the missing or corrected documentation for each listed issue. Done means all six referenced documentation problems are resolved and the affected pages are consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100