-
Task
-
Resolution: Done
-
Critical
-
None
-
None
- is blocked by
-
JBWS-457 Add support for JSR-181 annotations
-
- Closed
-
-
JBWS-657 ParameterMetaData is passed conflicting class name formats
-
- Closed
-
-
JBWS-661 AnnonationMetaDataBuilder is missing support for exceptions/faults
-
- Closed
-
-
JBWS-662 JSR-181 Custom type properties of custom types fail
-
- Closed
-
-
JBWS-556 Tools generated xml descriptors are missing the xml declaration
-
- Closed
-
-
JBWS-564 Tools generates an invalid schema type for a byte array
-
- Closed
-
-
JBWS-566 Tools generates nillibale="true" on arrays of simple types
-
- Closed
-
-
JBWS-607 SchemaTypesCreator errors when generating wsdl for exceptions
-
- Closed
-
-
JBWS-636 Generated WSDL should not specify namespace in binding for document/literal
-
- Closed
-
-
JBWS-646 Investigate "targetNamespace cannot be http://www.w3.org/2001/XMLSchema" problem
-
- Closed
-
-
JBWS-647 Fix NPE in JavaToWsdlHelper
-
- Closed
-
-
JBWS-649 Tools should not generate wrapper complexTypes for arrays that are bean properties
-
- Closed
-
-
JBWS-651 Tools fails to handle circular references properly
-
- Closed
-
-
JBWS-654 Fix array type name generation in all metadata builders
-
- Closed
-
-
JBWS-665 Package handling in tools is wrong
-
- Closed
-
-
JBWS-648 Ugly whitespace in generated wsdl files
-
- Closed
-
-
JBWS-583 Refactor UMD to eager load data
-
- Closed
-
-
JBWS-584 Autogenerate wrapper types for jsr-181 deployments
-
- Closed
-
-
JBWS-540 Implement a solution for WebParam.targetNamespace on a document/wrapped service
-
- Closed
-
-
JBWS-543 Switch all JSR-181 schema to be fully qualified
-
- Closed
-
-
JBWS-650 Add JSR-181 test coverage for exceptions, arrays, and packages
-
- Closed
-