[JBoss JIRA] (JBWS-3636) Dismantle jbossws-shared-testsuite
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3636?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3636:
----------------------------------
Summary: Dismantle jbossws-shared-testsuite (was: Dismantle jbossws shared testsuite)
> Dismantle jbossws-shared-testsuite
> ----------------------------------
>
> Key: JBWS-3636
> URL: https://issues.jboss.org/browse/JBWS-3636
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf, productization
> Reporter: Alessio Soldano
> Fix For: jbossws-cxf-4.2
>
>
> With the JBossWS-Native stack having gone since some time, the JAXRPC requirement having been removed from EE7, and the Apache CXF based stack being consolidated, it's time to take apart the jbossws-shared-testsuite project component. The actual testsuite should be moved to the jbossws-cxf stack (possibly a new sub-module of 'modules/testsuite', basically at the same level of 'cxf-tests' and 'cxf-spring-tests'), while the remaining classes and scripts there that are still relevant should be moved to either jbossws-common or again jbossws-cxf.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBWS-3636) Dismantle jbossws shared testsuite
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3636:
-------------------------------------
Summary: Dismantle jbossws shared testsuite
Key: JBWS-3636
URL: https://issues.jboss.org/browse/JBWS-3636
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-cxf, productization
Reporter: Alessio Soldano
Fix For: jbossws-cxf-4.2
With the JBossWS-Native stack having gone since some time, the JAXRPC requirement having been removed from EE7, and the Apache CXF based stack being consolidated, it's time to take apart the jbossws-shared-testsuite project component. The actual testsuite should be moved to the jbossws-cxf stack (possibly a new sub-module of 'modules/testsuite', basically at the same level of 'cxf-tests' and 'cxf-spring-tests'), while the remaining classes and scripts there that are still relevant should be moved to either jbossws-common or again jbossws-cxf.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBWS-3635) soap12:address doesn't appear in WSDL for SOAP 1.2 service
by Tadayoshi Sato (JIRA)
Tadayoshi Sato created JBWS-3635:
------------------------------------
Summary: soap12:address doesn't appear in WSDL for SOAP 1.2 service
Key: JBWS-3635
URL: https://issues.jboss.org/browse/JBWS-3635
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Affects Versions: jbossws-cxf-3.1.2
Reporter: Tadayoshi Sato
WSDL for the following SOAP 1.2 web service displays not {{<soap12:address .../>}} but only {{<soap:address .../>}}.
{code:java}
@WebService
@BindingType(SOAPBinding.SOAP12HTTP_BINDING)
public class HelloWorldService {
@WebMethod
public String sayHello() {
return "Hello World";
}
}
{code}
The root cause must be https://issues.apache.org/jira/browse/CXF-3584 , as this issue seems to be resolved in JBoss WS CXF 4.0.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBWS-3632) Overwrite the webservice @WebContext annotation using XML file
by kiran varanasi (JIRA)
[ https://issues.jboss.org/browse/JBWS-3632?page=com.atlassian.jira.plugin.... ]
kiran varanasi updated JBWS-3632:
---------------------------------
Environment: jbossws-spi.jar,JDK 1.6 and jboss 4.2.3 GA bundle
> Overwrite the webservice @WebContext annotation using XML file
> --------------------------------------------------------------
>
> Key: JBWS-3632
> URL: https://issues.jboss.org/browse/JBWS-3632
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: jbossws-spi.jar,JDK 1.6 and jboss 4.2.3 GA bundle
> Reporter: kiran varanasi
>
> We are using Jboss 4.2.3 GA ,which support JAXWS webservices. Webservice also as Stateless EJB. The deployment path of jar file is under webservices.war->webserviceEJB.jar. Using @webContext annotation the webservice is running on SSL. To avoid code change any XML configuration file is required which can define the @WebContext values for tranport-guarantee attribute.All the websevices has @WebContext with auth-method =BASIC and transport-guarantee =NONE. We need to overwrite the annontation using XML file.
> The idea of using configuration files is Webservices need to be configured in jboss either on http or https. Please reply that jboss 4.2.3GA support @WebContext values in configuration file for SSL and the required dependancy jars.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBWS-3632) Overwrite the webservice @WebContext annotation using XML file
by kiran varanasi (JIRA)
[ https://issues.jboss.org/browse/JBWS-3632?page=com.atlassian.jira.plugin.... ]
kiran varanasi updated JBWS-3632:
---------------------------------
Summary: Overwrite the webservice @WebContext annotation using XML file (was: Overwrite the webservice annotation using XML file)
> Overwrite the webservice @WebContext annotation using XML file
> --------------------------------------------------------------
>
> Key: JBWS-3632
> URL: https://issues.jboss.org/browse/JBWS-3632
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: kiran varanasi
>
> We are using Jboss 4.2.3 GA ,which support JAXWS webservices. Webservice also as Stateless EJB. The deployment path of jar file is under webservices.war->webserviceEJB.jar. Using @webContext annotation the webservice is running on SSL. To avoid code change any XML configuration file is required which can define the @WebContext values for tranport-guarantee attribute.All the websevices has @WebContext with auth-method =BASIC and transport-guarantee =NONE. We need to overwrite the annontation using XML file.
> The idea of using configuration files is Webservices need to be configured in jboss either on http or https. Please reply that jboss 4.2.3GA support @WebContext values in configuration file for SSL and the required dependancy jars.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBWS-3633) web service invocation using Jboss 6 throwing null pointer exception, works fine with jboss 5
by sun_luck V (JIRA)
[ https://issues.jboss.org/browse/JBWS-3633?page=com.atlassian.jira.plugin.... ]
sun_luck V updated JBWS-3633:
-----------------------------
Summary: web service invocation using Jboss 6 throwing null pointer exception, works fine with jboss 5 (was: Jboss 6--- [org.apache.cxf.phase.PhaseInterceptorChain] Interceptor for "Given_service_class" has thrown exception, unwinding now: java.lang.NullPointerException)
> web service invocation using Jboss 6 throwing null pointer exception, works fine with jboss 5
> ---------------------------------------------------------------------------------------------
>
> Key: JBWS-3633
> URL: https://issues.jboss.org/browse/JBWS-3633
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: Jboss 6 Final, Jaxb webservice (based on soap) ,Rich faces 4(JSF 2.0), Spring 3.0, Webservice Jboss 6,
> invocation null pointer exception
> Reporter: sun_luck V
> Labels: Webservice, exception, invocation, jawaCXF, jboss6, null, nullpointerexception, ponter
>
> I am new to webservice and jboss 6 ,earlier I was working with Jboss 5 and my we wervice was working fine but as a part of migration to RichFaces 4 we moved to J boss 6, and now I have started getting this problem.
> While invoking JAXb web service (SOAP) using JBOSS 6 Final I am getting a null pointer Exception: the complete stack Trace is as follows:
> WARN [org.apache.cxf.phase.PhaseInterceptorChain] Interceptor for {http://www.webservice.weservice1/}weservice1#{http://www.webservice.weservice1/}Some_method has thrown exception, unwinding now: java.lang.NullPointerException
> at com.cognizant.epc.webservice.SoapHeaderHandler.handleMessage(SoapHeaderHandler.java:57) [:]
> at com.cognizant.epc.webservice.SoapHeaderHandler.handleMessage(SoapHeaderHandler.java:27) [:]
> at org.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeHandleMessage(HandlerChainInvoker.java:335) [:2.3.1-patch-01]
> at org.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeHandlerChain(HandlerChainInvoker.java:253) [:2.3.1-patch-01]
> at org.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeProtocolHandlers(HandlerChainInvoker.java:131) [:2.3.1-patch-01]
> at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessageInternal(SOAPHandlerInterceptor.java:171) [:2.3.1-patch-01]
> at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:126) [:2.3.1-patch-01]
> at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:71) [:2.3.1-patch-01]
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255) [:2.3.1-patch-01]
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113) [:2.3.1-patch-01]
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97) [:2.3.1-patch-01]
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461) [:2.3.1-patch-01]
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:172) [:3.4.1.GA]
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:57) [:3.4.1.GA]
> at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156) [:3.4.1.GA]
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:90) [:3.4.1.GA]
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179) [:2.3.1-patch-01]
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103) [:2.3.1-patch-01]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [:1.0.0.Final]
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159) [:2.3.1-patch-01]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.1.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final]
> at com.cognizant.epc.filter.ErrorFilter.doFilter(ErrorFilter.java:39) [:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final]
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final]
> at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final]
> at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final]
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final]
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final]
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final]
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final]
> at java.lang.Thread.run(Thread.java:619) [:1.6.0_12]
> Please Provide me a solution to this problem. Thanks in advance!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JBWS-3633) Jboss 6--- [org.apache.cxf.phase.PhaseInterceptorChain] Interceptor for "Given_service_class" has thrown exception, unwinding now: java.lang.NullPointerException
by sun_luck V (JIRA)
sun_luck V created JBWS-3633:
--------------------------------
Summary: Jboss 6--- [org.apache.cxf.phase.PhaseInterceptorChain] Interceptor for "Given_service_class" has thrown exception, unwinding now: java.lang.NullPointerException
Key: JBWS-3633
URL: https://issues.jboss.org/browse/JBWS-3633
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Environment: Jboss 6 Final, Jaxb webservice (based on soap) ,Rich faces 4(JSF 2.0), Spring 3.0, Webservice Jboss 6,
invocation null pointer exception
Reporter: sun_luck V
I am new to webservice and jboss 6 ,earlier I was working with Jboss 5 and my we wervice was working fine but as a part of migration to RichFaces 4 we moved to J boss 6, and now I have started getting this problem.
While invoking JAXb web service (SOAP) using JBOSS 6 Final I am getting a null pointer Exception: the complete stack Trace is as follows:
WARN [org.apache.cxf.phase.PhaseInterceptorChain] Interceptor for {http://www.webservice.weservice1/}weservice1#{http://www.webservice.weservice1/}Some_method has thrown exception, unwinding now: java.lang.NullPointerException
at com.cognizant.epc.webservice.SoapHeaderHandler.handleMessage(SoapHeaderHandler.java:57) [:]
at com.cognizant.epc.webservice.SoapHeaderHandler.handleMessage(SoapHeaderHandler.java:27) [:]
at org.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeHandleMessage(HandlerChainInvoker.java:335) [:2.3.1-patch-01]
at org.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeHandlerChain(HandlerChainInvoker.java:253) [:2.3.1-patch-01]
at org.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeProtocolHandlers(HandlerChainInvoker.java:131) [:2.3.1-patch-01]
at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessageInternal(SOAPHandlerInterceptor.java:171) [:2.3.1-patch-01]
at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:126) [:2.3.1-patch-01]
at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:71) [:2.3.1-patch-01]
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255) [:2.3.1-patch-01]
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113) [:2.3.1-patch-01]
at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97) [:2.3.1-patch-01]
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461) [:2.3.1-patch-01]
at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:172) [:3.4.1.GA]
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:57) [:3.4.1.GA]
at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156) [:3.4.1.GA]
at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:90) [:3.4.1.GA]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179) [:2.3.1-patch-01]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103) [:2.3.1-patch-01]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [:1.0.0.Final]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159) [:2.3.1-patch-01]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.1.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final]
at com.cognizant.epc.filter.ErrorFilter.doFilter(ErrorFilter.java:39) [:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final]
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final]
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final]
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final]
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final]
at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_12]
Please Provide me a solution to this problem. Thanks in advance!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months