Java Web Services Development Pack
software development kit

The Java Web Services Development Pack (JWSDP) is a free software development kit (SDK) for developing Web Services, Web applications and Java applications with the newest technologies for Java.
Oracle replaced JWSDP with GlassFish. All components of JWSDP are part of GlassFish and WSIT and several are in Java SE 6 ("Mustang"). The source is available under the Open Source Initiative-approved CDDL license.
Java APIs
These are the components and APIs available in the JWSDP 1.6:
Java API for XML Processing (JAXP), v 1.3
Java API for XML Registries (JAXR)
Java Architecture for XML Binding (JAXB), v 1.0 and 2.0
JAX-RPC v 1.1
JAX-WS v 2.0
SAAJ (SOAP with Attachments API for Java)
Web Services Registry
Starting with JWSDP 1.6, the JAX-RPC and JAX-WS implementations support the Fast Infoset standard for the binary encoding of the XML infoset. Earlier versions of JWSDP also included
Java Servlet
JavaServer Pages
JavaServer Faces
Related technologies
There are many other Java implementations of Web Services or XML processors. Some of them support the Java standards, some support other standards or non-standard features.
The public source identifies “Java Web Services Development Pack” as software development kit. This brief keeps that definition visible, then builds a research path around Java, Services and Development.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Java Web Services Development Pack”, the useful work is to connect “software development kit” to the records capable of establishing context and consequence.
Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Dec 23, 2023. The linked authority identifier is Q598151. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.
Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Java Web Services Development Pack”, its source revision and the description used here.
- Expand the search: follow Java Web Services Development Pack primary sources, Java Web Services Development Pack archive and Java research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Java Web Services Development Pack”?
- Which observation, specimen, dataset or publication supports the account?
- Has classification or technical consensus changed since the cited source?
Search terms from this dossier
This entry incorporates text from “Java Web Services Development Pack” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.