[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
11 years, 11 months
[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
[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
[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