March 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3409) Support for CXF Continuations

by Daniel Wegener (Created) (JIRA)

Support for CXF Continuations ----------------------------- Key: JBWS-3409 URL: https://issues.jboss.org/browse/JBWS-3409 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.1 Environment: Windows 7 x64, jdk1.6.0_18, JBoss AS 6.1.0.Final (should not matter) Reporter: Daniel Wegener Priority: Minor When using CXF Continuations like in this example (http://stackoverflow.com/questions/8668754/nonblocking-webservice-endpoin...), the whole servlet request crashes with an SuspendedInvocationException. This exception is thrown to interrupt the interceptor chain and should be caught somewhere between the interceptor chain and the underlaying servlet container. -- 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

12 years, 6 months

7
8
0 / 0

[JBoss JIRA] (JBWS-3476) Incorrect url scheme causes hang

by Alex O (JIRA)

Alex O created JBWS-3476: ---------------------------- Summary: Incorrect url scheme causes hang Key: JBWS-3476 URL: https://issues.jboss.org/browse/JBWS-3476 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Environment: jboss 6 final Reporter: Alex O if connecting to a non-ssl url and https:// is the URL prefix, the client hangs indefinitely. Related to JBWS-3445 -- 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

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3287) Deployment descriptor support for declaring jbossws-config-file / jbossws-config-name

by Alessio Soldano (JIRA)

Deployment descriptor support for declaring jbossws-config-file / jbossws-config-name ------------------------------------------------------------------------------------- Key: JBWS-3287 URL: https://issues.jboss.org/browse/JBWS-3287 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.1, jbossws-cxf-4.1 The jaxws endpoint configuration is currently declared through the @EndpointConfig annotation. The jbossws-native used to support declaring the same through context-params in the servlet web.xml. We should allow the same (perhaps even for ejb descriptor). For the jbws-cxf stack that probably implies early looking at the parameters when creating/rewriting the web.xml, as the endpoint publish (which needs those params) happens at bus startup in BusDeploymentAspect (deploy time, not runtime / when the endpoint servlet is first called) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] (JBWS-3463) Remove project generator

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3463: ------------------------------------ Summary: Remove project generator Key: JBWS-3463 URL: https://issues.jboss.org/browse/JBWS-3463 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1, jbossws-cxf-4.1 -- 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

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (JBWS-3383) WS-sec truststore/keystore urls should be obtained from the central security configuration

by Richard Opalka (Created) (JIRA)

WS-sec truststore/keystore urls should be obtained from the central security configuration ------------------------------------------------------------------------------------------ Key: JBWS-3383 URL: https://issues.jboss.org/browse/JBWS-3383 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Anil Saldhana wrote: Ensure that the ws-sec truststore/keystore urls are obtained from the central security configuration. Rely on the from https://docs.jboss.org/author/display/AS7/Security+subsystem+configuration Reporter: Richard Opalka Assignee: Alessio Soldano Fix For: jbossws-native-4.0, 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

12 years, 9 months

3
4
0 / 0

[JBoss JIRA] (JBWS-3456) JBossWS requires AS7 jmx subsystem

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3456: ------------------------------------- Summary: JBossWS requires AS7 jmx subsystem Key: JBWS-3456 URL: https://issues.jboss.org/browse/JBWS-3456 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.1, jbossws-cxf-4.1 Removing jmx subsystem from AS7 causes the following: 14:49:17,269 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.mbean.server (missing) dependents: [service jboss.ws.config, service jboss.ws.registry] Moreover, the WSDL file publishing fails: http://www.fpaste.org/1C7g/ -- 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

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3469) javax.xml.ws.WebServiceException: java.lang.IllegalArgumentException: Resource META-INF/jbossws-entities.properties not found

by Oscar Lewis (JIRA)

Oscar Lewis created JBWS-3469: --------------------------------- Summary: javax.xml.ws.WebServiceException: java.lang.IllegalArgumentException: Resource META-INF/jbossws-entities.properties not found Key: JBWS-3469 URL: https://issues.jboss.org/browse/JBWS-3469 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-4.0.2 Environment: Linux Reporter: Oscar Lewis javax.xml.ws.WebServiceException: java.lang.IllegalArgumentException: Resource META-INF/jbossws-entities.properties not found 16:20:08,905 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:123) 16:20:08,906 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:131) 16:20:08,906 ERROR [stderr] (http--0.0.0.0-8080-1) at javax.xml.ws.Service.<init>(Service.java:57) 16:20:08,906 ERROR [stderr] (http--0.0.0.0-8080-1) at com.usaepay.api.jaxws.UsaepayService.<init>(UsaepayService.java:44) 16:20:08,906 ERROR [stderr] (http--0.0.0.0-8080-1) at com.usaepay.api.jaxws.usaepay.getClient(usaepay.java:91) 16:20:08,907 ERROR [stderr] (http--0.0.0.0-8080-1) at auth.Server.Payment.PaymentVeriCheck.ExecuteeCheck(PaymentVeriCheck.java:84) 16:20:08,907 ERROR [stderr] (http--0.0.0.0-8080-1) at auth.Server.Payment.PaymentVeriCheck.Execute(PaymentVeriCheck.java:31) 16:20:08,907 ERROR [stderr] (http--0.0.0.0-8080-1) at auth.server.routines.MobilePayment.TermBank(MobilePayment.java:1097) 16:20:08,907 ERROR [stderr] (http--0.0.0.0-8080-1) at auth.server.routines.MobilePayment.Driver(MobilePayment.java:130) 16:20:08,908 ERROR [stderr] (http--0.0.0.0-8080-1) at auth.server.routines.MobileRequest.processRequest(MobileRequest.java:137) 16:20:08,908 ERROR [stderr] (http--0.0.0.0-8080-1) at auth.server.routines.MobileRequest.doGet(MobileRequest.java:186) 16:20:08,908 ERROR [stderr] (http--0.0.0.0-8080-1) at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) 16:20:08,909 ERROR [stderr] (http--0.0.0.0-8080-1) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) 16:20:08,909 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) 16:20:08,909 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) 16:20:08,909 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) 16:20:08,910 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) 16:20:08,910 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) 16:20:08,910 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) 16:20:08,910 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) 16:20:08,911 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 16:20:08,911 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 16:20:08,911 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) 16:20:08,911 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) 16:20:08,912 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) 16:20:08,912 ERROR [stderr] (http--0.0.0.0-8080-1) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) 16:20:08,912 ERROR [stderr] (http--0.0.0.0-8080-1) at java.lang.Thread.run(Thread.java:679) 16:20:08,913 ERROR [stderr] (http--0.0.0.0-8080-1) Caused by: java.lang.IllegalArgumentException: Resource META-INF/jbossws-entities.properties not found 16:20:08,913 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.common.utils.JBossWSEntityResolver$1.run(JBossWSEntityResolver.java:129) 16:20:08,913 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.common.utils.JBossWSEntityResolver$1.run(JBossWSEntityResolver.java:120) 16:20:08,913 ERROR [stderr] (http--0.0.0.0-8080-1) at java.security.AccessController.doPrivileged(Native Method) 16:20:08,914 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.common.utils.JBossWSEntityResolver.loadEntitiesMappingFromClasspath(JBossWSEntityResolver.java:119) 16:20:08,914 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.common.utils.JBossWSEntityResolver.<init>(JBossWSEntityResolver.java:100) 16:20:08,914 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.common.utils.JBossWSEntityResolver.<init>(JBossWSEntityResolver.java:72) 16:20:08,915 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.common.utils.JBossWSEntityResolver.<init>(JBossWSEntityResolver.java:67) 16:20:08,915 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:107) 16:20:08,915 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:296) 16:20:08,916 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:98) 16:20:08,916 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:77) 16:20:08,916 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:157) 16:20:08,916 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:128) 16:20:08,917 ERROR [stderr] (http--0.0.0.0-8080-1) at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:117) 16:20:08,917 ERROR [stderr] (http--0.0.0.0-8080-1) ... 26 more -- 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

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] (JBWS-3443) Add configurable per client SSL parameters

by Alex O (JIRA)

Alex O created JBWS-3443: ---------------------------- Summary: Add configurable per client SSL parameters Key: JBWS-3443 URL: https://issues.jboss.org/browse/JBWS-3443 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Reporter: Alex O Currently, when web service clients exist inside a Jboss deployment (war, ear, etc), they explicitly rely on SSL settings from javax.ssl in the System.Properties() collection. This is global and affects all web service clients in the container. This can be problematic for obvious reasons, different clients calling different endpoints, possibly with different truststores. In addition, for web service clients that rely on HTTP client-cert for authentication, different certificates can be used for each client. We're specifically talking only about transport security here. -- 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

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3475) SOAP-over-JMS tests require test queue on target AS

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3475: ------------------------------------- Summary: SOAP-over-JMS tests require test queue on target AS Key: JBWS-3475 URL: https://issues.jboss.org/browse/JBWS-3475 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.1 The SOAP-over-JMS tests require test queue on target AS. Unfortunately, the testQueue we've been using on AS 7.1.1.Final has been removed on current AS7 master (building to 7.1.2.Final-SNAPSHOT ATM). So we either need to run a custom standalone-full.xml version or extend the jbossws testsuite facilities to allow creating a queue on the server before running the test (and eventually remove it after the test). -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3474) Remove JAX-WS support

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3474: ------------------------------------ Summary: Remove JAX-WS support Key: JBWS-3474 URL: https://issues.jboss.org/browse/JBWS-3474 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1 -- 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

12 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2012