-
Bug
-
Resolution: Done
-
Major
-
None
-
None
This is a aggregating issue for JBWS project bug fixes that are incorporated into 4.0.3.
- incorporates
-
JBWS-317 Wrap document style request/respose structure
- Closed
-
JBWS-309 Authorization Error using JBossWS together with JACC
- Closed
-
JBWS-415 DOM2Utils isn't thread safe
- Closed
-
JBWS-419 Thread safety issues in WSDLRequestHandler
- Closed
-
JBWS-163 Problems mapping between xsd:unsignedLong and javax.xml.rpc.holders.BigIntegerHolder
- Closed
-
JBWS-165 Deployment sharing the same servlet context
- Closed
-
JBWS-168 soap response does not respect minOccurs=0
- Closed
-
JBWS-181 Custom exception containing an array
- Closed
-
JBWS-187 WebService isn't called through ServiceFactory on jdk5
- Closed
-
JBWS-222 Is JBossEntityResolver being used in ServiceDeployerJSE?
- Closed
-
JBWS-223 Cannot convert SAX to DOM attributes
- Closed
-
JBWS-225 ManagedMemoryDataSource prematurely removes tmp files
- Closed
-
JBWS-226 DataContentHandler for text/xml expects Source objects
- Closed
-
JBWS-254 JBAS897TestCase fails
- Closed
-
JBWS-255 JBWS84TestCase fails
- Closed
-
JBWS-256 ServerSideEJBSecTestCase fails
- Closed
-
JBWS-337 Fix SimpleClientSecureTestCase
- Closed
-
JBWS-420 JBoss 4.x ws clients do not upload a propper version number
- Closed
-
JBWS-435 SSL properties on a proxy are not reused across multiple invocations
- Closed
-
JBWS-167 SAAJ implementation does not add soapAction header
- Closed
-
JBWS-217 simpletype primitives fails to deploy
- Closed
-
JBWS-186 Setup tests that use the SSL transport
- Closed
-
JBWS-218 Continuous webservice refactoring and build breakages.
- Closed
-
JBWS-224 Support per Call and per Proxy specific SSL settings
- Closed
-
JBWS-253 global <webservices> element in jboss.xml
- Closed
-
JBWS-237 SOAP Fault Details are not output unless the AxisFault has a detail exception
- Closed