[
https://issues.jboss.org/browse/JBWS-3403?page=com.atlassian.jira.plugin....
]
Alessio Soldano edited comment on JBWS-3403 at 12/22/11 3:50 AM:
-----------------------------------------------------------------
AS700
- [CXF-1519] Explicitly set the namespace of a WebFault
- [CXF-2006] RespectBinding feature and not understood required extensibility elements
- [EJBTHREE-1152] service-ref in ejb-jar.xml is ignored
- [JBWS-2561] XOP request not properly inlined
- [JBWS-2480] Soap attachments are dropped on server response
- [JBWS-2397] Fix jbws1797 testcase
- [JBAS-8363] Virtual host issue in JBossWeb
- [JBAS-9188] Implement support for nested EJBs & WARs in .sar archives
- [JBWS-3367] EJB3 endpoints in war archive should follow context root override rules
- [AS7-1605] jboss-web.xml ignored for web service root
- [JBWS-3276] Implement support for POJO endpoints with no web.xml in archive
- [JBAS-9188] On AS7 We don't support nested EJB & WAR archives neither in .sar
nor in .jar archives
- [JBWS-3322] Ensure proper creation of WebMD for EJBs present in web archive
- [AS7-1101] Parser error when processing security-identity/description ejb-jar.xml
element
- [JBWS-3232] javax.naming.NameNotFoundException: Name 'service' not found in
context 'env'
- [AS7-1338] Remote JNDI support for AS7
- [JBWS-3225] jbossws console not yet available
- [JBWS-3227] handlers config file not found on classpath
- [JBWS-3249] Restore UsernameAuthorizationCustomFileTestCase on AS7
- [AS7-1322] Provide service for starting/stop a POJO WS endpoint
- [AS7-2961] Context lookup fails during WebService constructor
FIXME: [CXF-1310] Generated WSDL for an WS-RM endpoint does not contain RM policies
FIXME: [CXF-1507] CXF client handler cannot set mime header
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding
FIXME: [JBWS-3262] fix issue in CXF so the following test will start passing
FIXME: [JBWS-3079] Add support for https protocol
was (Author: asoldano):
AS700
- [CXF-1519] Explicitly set the namespace of a WebFault
- [CXF-2006] RespectBinding feature and not understood required extensibility elements
- [EJBTHREE-1152] service-ref in ejb-jar.xml is ignored
- [JBWS-2561] XOP request not properly inlined
- [JBWS-2480] Soap attachments are dropped on server response
- [JBWS-2397] Fix jbws1797 testcase
- [JBAS-8363] Virtual host issue in JBossWeb
- [JBAS-9188] Implement support for nested EJBs & WARs in .sar archives
- [JBWS-3367] EJB3 endpoints in war archive should follow context root override rules
- [AS7-1605] jboss-web.xml ignored for web service root
- [JBWS-3276] Implement support for POJO endpoints with no web.xml in archive
- [JBAS-9188] On AS7 We don't support nested EJB & WAR archives neither in .sar
nor in .jar archives
- [JBWS-3322] Ensure proper creation of WebMD for EJBs present in web archive
- [AS7-1101] Parser error when processing security-identity/description ejb-jar.xml
element
- [JBWS-3232] javax.naming.NameNotFoundException: Name 'service' not found in
context 'env'
- [AS7-1338] Remote JNDI support for AS7
- [JBWS-3225] jbossws console not yet available
- [JBWS-3227] handlers config file not found on classpath
- [JBWS-3249] Restore UsernameAuthorizationCustomFileTestCase on AS7
- [AS7-1322] Provide service for starting/stop a POJO WS endpoint
- [AS7-2961] Context lookup fails during WebService constructor
FIXME: [CXF-1310] Generated WSDL for an WS-RM endpoint does not contain RM policies
FIXME: [CXF-1507] CXF client handler cannot set mime header
FIXME: [CXF-1519] Explicitely set the namespace of a WebFault
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding
FIXME: [JBWS-3262] fix issue in CXF so the following test will start passing
FIXME: [JBWS-3079] Add support for https protocol
JBossWS-CXF 4.0.0.GA Errata
---------------------------
Key: JBWS-3403
URL:
https://issues.jboss.org/browse/JBWS-3403
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: Alessio Soldano
Assignee: Richard Opalka
Fix For: jbossws-cxf-4.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira