April 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3240) Rewrite tests relying on $JBOSS_HOME/server/default/tmp/jbossws folder existence

by Richard Opalka (JIRA)

Rewrite tests relying on $JBOSS_HOME/server/default/tmp/jbossws folder existence -------------------------------------------------------------------------------- Key: JBWS-3240 URL: https://issues.jboss.org/browse/JBWS-3240 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-4.0 junit.framework.AssertionFailedError: Temp dir doesn't exist: /server/default/tmp/jbossws at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.test.ws.jaxws.samples.xop.doclit.XOPBase.testAttachmentpartSwap(XOPBase.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:23) at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98) at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107) at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3199) AbstractServerConfig.toIPv6URLFormat throws java.net.UnknownHostException

by Alessio Soldano (JIRA)

AbstractServerConfig.toIPv6URLFormat throws java.net.UnknownHostException ------------------------------------------------------------------------- Key: JBWS-3199 URL: https://issues.jboss.org/browse/JBWS-3199 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Affects Versions: jbossws-native-3.4.1, jbossws-cxf-3.4.1 Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 After applying the changes for IPv6 support, the AbstractServerConfig::toIPv6URLFormat method does a InetAddress.getByName(host) call that can throws UnknownHostException if the webserviceHost in the configuration can't be lookup. This needs to be changed or at least surrounded by a try-catch block as it's not robust (to be honest nothing even prevents the user from wanting a fancy hostname in there). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3264) Don't use log4j configuration classes in our CXF tools - identify possible workarounds

by Richard Opalka (JIRA)

Don't use log4j configuration classes in our CXF tools - identify possible workarounds -------------------------------------------------------------------------------------- Key: JBWS-3264 URL: https://issues.jboss.org/browse/JBWS-3264 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-cxf-4.0 <opalka> dmlloyd, I found ugly dependency - http://fpaste.org/9UXj/ <stuartdouglas> opalka: I actually hacked up something last night to try and find those problems <opalka> dmlloyd, stuartdouglas this is the call resulting to this dependency - we're using log4j configurators - http://fpaste.org/aKXp/ <dmlloyd> why? <dmlloyd> (a) you shouldn't do that, (b) to fix the problem add "javax.api" to log4j's module dep <opalka> dmlloyd, this is question for alessio. I have no idea? Probably Alessio want's to use log4j config facility <dmlloyd> ok well if we're doing that it's pretty lame because we go through many hoops to avoid using the log4j config facility <opalka> dmlloyd, method javadoc isn't more descriptive as well - http://fpaste.org/DyVx/ I'll need to ask Alessio <opalka> dmlloyd, but just to confirm, we don't want org.apache.logging -> org.w3c.dom dependency in AS7, right ? * opalka don't like this dependency <dmlloyd> no, org.apache.logging is something completely different <dmlloyd> it should be org.apache.log4j -> javax.api <opalka> dmlloyd, and do we want this dependency ? <dmlloyd> yeah, it's fine to add <dmlloyd> but we don't want this manual log4j configuration -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2941) HTTP Proxy authentication for JBossWS-Native Web Service clients

by Thomas Lehmann (JIRA)

HTTP Proxy authentication for JBossWS-Native Web Service clients ---------------------------------------------------------------- Key: JBWS-2941 URL: https://jira.jboss.org/jira/browse/JBWS-2941 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Lehmann We need a possibility to access Web Service endpoints through an HTTP Proxy which needs client authentication. In our case it's BASIC authentication, but there are may other JBoss customers who want to have support for other authentication schemas like DIGEST or NTLM. There must be a way to set the Proxy settings, especially the Proxy credentials used for authentication (username, password), in some sort of meta data (using a Java API). See also support case https://support.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-3271) TODO: Alessio

by Richard Opalka (JIRA)

TODO: Alessio ------------- Key: JBWS-3271 URL: https://issues.jboss.org/browse/JBWS-3271 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-native-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-3105) Review and fix AS IL maven dependencies

by Richard Opalka (JIRA)

Review and fix AS IL maven dependencies --------------------------------------- Key: JBWS-3105 URL: https://jira.jboss.org/browse/JBWS-3105 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.4.1, jbossws-native-3.4.1, jbossws-metro-3.4.1 I found some weirdness related to VirtualFile in AS IL. This blocked me to clean AS IL maven dependencies. We need to review AS IL dependencies and make them explicit i.e. to know which libraries we're exactly depending on. The result of this process should be VirtualFile weirdness fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-3230) Could not find any reference to namespace 'http://schemas.xmlsoap.org/ws/2005/02/rm'

by Richard Opalka (JIRA)

Could not find any reference to namespace 'http://schemas.xmlsoap.org/ws/2005/02/rm' ------------------------------------------------------------------------------------ Key: JBWS-3230 URL: https://issues.jboss.org/browse/JBWS-3230 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-cxf-4.0 13:07:03,626 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-8080-1) Interceptor for {http://www.jboss.org/jbossws/ws-extensions/wsrm}SimpleService has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not find any reference to namespace 'http://schemas.xmlsoap.org/ws/2005/02/rm' in handled message. at org.jboss.test.ws.jaxws.samples.wsrm.service.RMCheckInterceptor.handleMessage(RMCheckInterceptor.java:73) [classe:] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255) [cxf-api.jar:2.3.2] at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113) [cxf-rt-core.jar:2.3.2] at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97) [cxf-rt-transports-http.jar:2.3.2] at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461) [cxf-rt-transports-http.jar:2.3.2] at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:172) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:57) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.cxf.CXFNonSpringServletExt.invoke(CXFNonSpringServletExt.java:90) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179) [cxf-rt-transports-http.jar:2.3.2] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103) [cxf-rt-transports-http.jar:2.3.2] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159) [cxf-rt-transports-http.jar:2.3.2] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta1.jar:7.0.0.Alpha2-SNAPSHOT] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-3137) Support deploying http and jms endpoint in one deployment

by Jim Ma (JIRA)

Support deploying http and jms endpoint in one deployment --------------------------------------------------------- Key: JBWS-3137 URL: https://jira.jboss.org/browse/JBWS-3137 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.0.Beta2 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-3.4.1 When the jms endpoints is deployed with http endpoints in one war file, the WsTypeDeployer takes this deployment as "JAXWS_JSE" type . Hence the JMSDeploymentAspects will not be activated and process this mixed type deployment . JMSTransportTestCase is the test for this user case. The jms endpoints is not registered in registry so far. We can review our WSTypeDeployer and other JMSDAs to support this mixed type deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3248) Unable to lookup AuthenticationManager using JNDI - AS7

by Alessio Soldano (JIRA)

Unable to lookup AuthenticationManager using JNDI - AS7 ------------------------------------------------------- Key: JBWS-3248 URL: https://issues.jboss.org/browse/JBWS-3248 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Environment: JBoss AS 7 Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0 org.apache.ws.security.WSSecurityException: The security token could not be authenticated or authorized; nested exception is: org.apache.ws.security.WSSecurityException: Failed Authentication : Subject has not been created; nested exception is: java.lang.SecurityException: Unable to lookup AuthenticationManager using JNDI at org.apache.ws.security.processor.UsernameTokenProcessor.handleUsernameToken(UsernameTokenProcessor.java:173) [wss4j-1.5.11.jar:1.5.11] at org.apache.ws.security.processor.UsernameTokenProcessor.handleToken(UsernameTokenProcessor.java:61) [wss4j-1.5.11.jar:1.5.11] at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:328) [wss4j-1.5.11.jar:1.5.11] at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:245) [wss4j-1.5.11.jar:1.5.11] at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:218) [cxf-rt-ws-security.jar:2.3.4-SNAPSHOT] at org.apache.cxf.ws.security.wss4j.AbstractUsernameTokenAuthenticatingInterceptor.handleMessage(AbstractUsernameTokenAuthenticatingInterceptor.java:96) [cxf-rt-ws-security.jar:2.3.4-SNAPSHOT] at org.apache.cxf.ws.security.wss4j.AbstractUsernameTokenAuthenticatingInterceptor.handleMessage(AbstractUsernameTokenAuthenticatingInterceptor.java:67) [cxf-rt-ws-security.jar:2.3.4-SNAPSHOT] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255) [cxf-api.jar:2.3.4-SNAPSHOT] at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113) [cxf-rt-core.jar:2.3.4-SNAPSHOT] at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:105) [cxf-rt-transports-http.jar:2.3.4-SNAPSHOT] at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461) [cxf-rt-transports-http.jar:2.3.4-SNAPSHOT] at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:172) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:57) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:90) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179) [cxf-rt-transports-http.jar:2.3.4-SNAPSHOT] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103) [cxf-rt-transports-http.jar:2.3.4-SNAPSHOT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159) [cxf-rt-transports-http.jar:2.3.4-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: org.apache.ws.security.WSSecurityException: Failed Authentication : Subject has not been created; nested exception is: java.lang.SecurityException: Unable to lookup AuthenticationManager using JNDI at org.apache.cxf.ws.security.wss4j.AbstractUsernameTokenAuthenticatingInterceptor.setSubject(AbstractUsernameTokenAuthenticatingInterceptor.java:147) [cxf-rt-ws-security.jar:2.3.4-SNAPSHOT] at org.apache.cxf.ws.security.wss4j.AbstractUsernameTokenAuthenticatingInterceptor$SubjectCreatingCallbackHandler.handleCallback(AbstractUsernameTokenAuthenticatingInterceptor.java:228) [cxf-rt-ws-security.jar:2.3.4-SNAPSHOT] at org.apache.cxf.ws.security.wss4j.DelegatingCallbackHandler.handle(DelegatingCallbackHandler.java:38) [cxf-rt-ws-security.jar:2.3.4-SNAPSHOT] at org.apache.ws.security.processor.UsernameTokenProcessor.handleUsernameToken(UsernameTokenProcessor.java:168) [wss4j-1.5.11.jar:1.5.11] ... 30 more Caused by: java.lang.SecurityException: Unable to lookup AuthenticationManager using JNDI at org.jboss.wsf.stack.cxf.security.authentication.AuthenticationManagerLoader.getManager(AuthenticationManagerLoader.java:48) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.cxf.security.authentication.SubjectCreatingInterceptor.createSubject(SubjectCreatingInterceptor.java:110) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.apache.cxf.ws.security.wss4j.AbstractUsernameTokenAuthenticatingInterceptor.setSubject(AbstractUsernameTokenAuthenticatingInterceptor.java:143) [cxf-rt-ws-security.jar:2.3.4-SNAPSHOT] ... 33 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-3269) WSA implementation does not throw wsa:InvalidCardinality exception when there is a greater than expected number of the specified header.

by Jim Ma (JIRA)

WSA implementation does not throw wsa:InvalidCardinality exception when there is a greater than expected number of the specified header. ---------------------------------------------------------------------------------------------------------------------------------------- Key: JBWS-3269 URL: https://issues.jboss.org/browse/JBWS-3269 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.1 Reporter: Jim Ma Fix For: jbossws-cxf-4.0 As per WSA soap binding spec: 6.4.1.3 wsa:InvalidCardinality Specifies that there was a greater than expected number of the specified header. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2011