-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
Before releasing we should check if some of the issue we created @Oracle have been solved, so that the corresponding JBossWS issue can be solved.
- relates to
-
JBWS-2131 NoSuchElementException during wsdl generation at deploy
- Closed
-
JBWS-2206 WSDL imports are not replaced with absolute path
- Closed
-
JBWS-2317 $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
- Closed
-
JBWS-2479 @XmlJavaTypeAdapter on SEI causes exception
- Closed
-
JBWS-2633 wscompile fails to create valid package name where namespace contains capitalised reserved keyword
- Closed
-
JBWS-2682 Incorrect Parsing of Badly Formed int
- Closed
-
JBWS-2686 Parsing errors fail to terminate unmarshalling
- Closed
-
JBWS-2165 Fix xop tests with maven build
- Closed