Bug 997380 - Anonymous types in an exception aren't generated in WSDL
Summary: Anonymous types in an exception aren't generated in WSDL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Services
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Alessio Soldano
QA Contact: Rostislav Svoboda
Russell Dickenson
Depends On:
TreeView+ depends on / blocked
Reported: 2013-08-15 11:02 UTC by Tadayoshi Sato
Modified: 2018-12-03 19:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-06-05 10:15:48 UTC
Type: Bug

Attachments (Terms of Use)
Reproducer (4.65 KB, application/zip)
2013-08-15 11:02 UTC, Tadayoshi Sato
no flags Details

System ID Private Priority Status Summary Last Updated
Apache JIRA CXF-5208 0 None None None Never
Red Hat Issue Tracker JBWS-3682 0 Major Closed Anonymous types in an exception aren't generated in WSDL 2015-04-25 20:30:14 UTC

Description Tadayoshi Sato 2013-08-15 11:02:24 UTC
Created attachment 786888 [details]

Platform BZ for https://issues.jboss.org/browse/JBWS-3682

Anonymous types (annotated with @XmlType(name = "")) in an exception class aren't generated at all in WSDL.

Web service classes:
public class GreetingService {
  public void hello() throws MyException {}

public class MyException extends Exception {
  private String     str;
  private MyAnonType myAnonObj;

  public String getStr() { return str; }
  public void setStr(String str) { this.str = str; }

  public MyAnonType getMyAnonObj() { return myAnonObj; }
  public void setMyAnonObj(MyAnonType myAnonObj) { this.myAnonObj = myAnonObj; }

@XmlType(name = "")
public class MyAnonType { ...

Generated WSDL:
<xs:schema ...>
  <xs:complexType name="MyException">
      <xs:element name="str" nillable="true" type="xs:string"/>

Note that the same type (MyAnonType) is generated in WSDL if the @XmlType(name = "") annotation is removed.

Comment 1 JBoss JIRA Server 2014-06-05 10:12:39 UTC
Tadayoshi Sato <tadayosi@gmail.com> updated the status of jira JBWS-3682 to Resolved

Comment 2 Tadayoshi Sato 2014-06-05 10:15:48 UTC
Closed as a correct way to fix the issue is provided. See Grzegorz' comment at CXF-5208 for how to fix it.

Comment 4 JBoss JIRA Server 2015-04-25 20:30:16 UTC
Alessio Soldano <asoldano@redhat.com> updated the status of jira JBWS-3682 to Closed

Note You need to log in before you can comment on or make changes to this bug.