[ 
https://issues.apache.org/jira/browse/AXIS2-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Lazarski updated AXIS2-6102:
-----------------------------------
    Description: 
Resolution: Fixed (5 commits)

  WSDL 2.0 was a W3C specification published in 2007 that the industry
  rejected. No major platform adopted it. WSDL 1.1 won. Apache Woden
  itself never reached a final 1.0 release in 19 years (still at
  1.0M10). Removing it reduces the kernel dependency footprint and
  eliminates reliance on a library headed for the Apache Attic.

  What was removed:
  - WSDL20ToAxisServiceBuilder.java (1,403 lines)
  - WSDL20ToAllAxisServicesBuilder.java (110 lines)
  - WSDL20Util.java (150 lines)
  - WSDL20SupplierTemplate.java (130 lines)
  - TestWSDL20Supplier.java, TestWSDL20SupplierTemplate.java (test
  classes)
  - 4 WSDL 2.0 test methods from WSDLSupplierTest and
  WSDLToAllServicesBuilderTest
  - woden-core dependency from kernel pom.xml
  - WSDL 2.0 branches in AxisService, ArchiveReader,
  CodeGenConfiguration
  - Woden URIResolver interface from AARBasedWSDLLocator and
  WarBasedWSDLLocator

  What was kept:
  - WSDL2Constants.java — pure string constants (MEP URIs, etc.) still
  used by WSDL 1.1 codegen
  - WSDL20DefaultValueHolder.java — default value constants, no woden
  imports
  - WSDL 1.1 support is fully intact


  was:
  WSDL 2.0 was a W3C specification that the industry rejected. It was
  published in 2007 and no major platform adopted it. WSDL 1.1 won. Even
   the W3C acknowledged this — WSDL 2.0 is effectively dead. Apache
  Woden itself is at version 1.0M10 (milestone 10) — it never reached a
  final 1.0 release in 19 years.

  Removal approach:
  1. Make woden-core <optional>true</optional> in kernel pom
  2. Guard the 2 imports in AxisService.java with try/catch
  ClassNotFoundException or move them to a separate class
  3. Move WSDL20ToAxisServiceBuilder and friends to a separate
  axis2-wsdl20 module (or just leave them in kernel — they won't load if
   woden isn't on classpath)
  4. The WSDL2Constants.java file is Axis2's own — it has no woden
  imports, just string constants. Keep it.

  Impact: Zero for JSON-RPC/MCP users. Zero for SOAP 1.1 users. Only
  affects the theoretical WSDL 2.0 user who doesn't exist.



> Woden (WSDL 2.0) Removal
> ------------------------
>
>                 Key: AXIS2-6102
>                 URL: https://issues.apache.org/jira/browse/AXIS2-6102
>             Project: Axis2
>          Issue Type: Task
>            Reporter: Robert Lazarski
>            Assignee: Robert Lazarski
>            Priority: Major
>             Fix For: 2.0.1
>
>
> Resolution: Fixed (5 commits)
>   WSDL 2.0 was a W3C specification published in 2007 that the industry
>   rejected. No major platform adopted it. WSDL 1.1 won. Apache Woden
>   itself never reached a final 1.0 release in 19 years (still at
>   1.0M10). Removing it reduces the kernel dependency footprint and
>   eliminates reliance on a library headed for the Apache Attic.
>   What was removed:
>   - WSDL20ToAxisServiceBuilder.java (1,403 lines)
>   - WSDL20ToAllAxisServicesBuilder.java (110 lines)
>   - WSDL20Util.java (150 lines)
>   - WSDL20SupplierTemplate.java (130 lines)
>   - TestWSDL20Supplier.java, TestWSDL20SupplierTemplate.java (test
>   classes)
>   - 4 WSDL 2.0 test methods from WSDLSupplierTest and
>   WSDLToAllServicesBuilderTest
>   - woden-core dependency from kernel pom.xml
>   - WSDL 2.0 branches in AxisService, ArchiveReader,
>   CodeGenConfiguration
>   - Woden URIResolver interface from AARBasedWSDLLocator and
>   WarBasedWSDLLocator
>   What was kept:
>   - WSDL2Constants.java — pure string constants (MEP URIs, etc.) still
>   used by WSDL 1.1 codegen
>   - WSDL20DefaultValueHolder.java — default value constants, no woden
>   imports
>   - WSDL 1.1 support is fully intact



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to