May 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2593) WSConsume does not generate @XmlJavaTypeAdapter in SEI

by Alessio Soldano (JIRA)

WSConsume does not generate @XmlJavaTypeAdapter in SEI ------------------------------------------------------ Key: JBWS-2593 URL: https://jira.jboss.org/jira/browse/JBWS-2593 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.1.0 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.1.1 The CXF version of WSConsume suffers the issue described at https://issues.apache.org/jira/browse/CXF-2148 . Provide a test case here and a patch for the CXF issue. -- 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

14 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2584) Provider endpoint causes NPE in AbstractPolicyInterceptor

by Alessio Soldano (JIRA)

Provider endpoint causes NPE in AbstractPolicyInterceptor --------------------------------------------------------- Key: JBWS-2584 URL: https://jira.jboss.org/jira/browse/JBWS-2584 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-cxf-3.1.1 Reporter: Alessio Soldano Assignee: Alessio Soldano When running JBWS1815TestCase we get this exception on server side, probably because of policy interceptor being enabled by default starting from CXF 2.2: 2009-03-23 02:16:27,109 INFO [org.apache.cxf.phase.PhaseInterceptorChain] Application has thrown exception, unwinding now java.lang.NullPointerException at org.apache.cxf.ws.policy.AbstractPolicyInterceptor.getBindingFaultInfo(AbstractPolicyInterceptor.java:77) at org.apache.cxf.ws.policy.ServerPolicyOutFaultInterceptor.handle(ServerPolicyOutFaultInterceptor.java:84) at org.apache.cxf.ws.policy.AbstractPolicyInterceptor.handleMessage(AbstractPolicyInterceptor.java:45) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:96) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:283) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:89) at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:337) at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:160) at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61) at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:134) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) -- 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

14 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2528) Missing parameterOrder in portType/operation

by Alessio Soldano (JIRA)

Missing parameterOrder in portType/operation -------------------------------------------- Key: JBWS-2528 URL: https://jira.jboss.org/jira/browse/JBWS-2528 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.1 The cxf java2wsdl seems to fail in generating the wsdl portType/operation element in some cases where soapHeader and IN/OUT parameters are used at the same time. This was revealed by the webparam3 reverse test configuration in the jws tck5 module. In that case we have <wsdl:portType name="webParam3WebService"> <wsdl:operation name="hello3"> <wsdl:input name="hello3" message="tns:hello3"> </wsdl:input> ... instead of <wsdl:portType name="webParam3WebService"> <wsdl:operation name="hello3" parameterOrder="id Name Employee"> <wsdl:input name="hello3" message="tns:hello3"> </wsdl:input> ... -- 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

14 years, 11 months

1
7
0 / 0

[JBoss JIRA] Created: (JBWS-2612) Remove AS 4.2.x support from all stacks

by Richard Opalka (JIRA)

Remove AS 4.2.x support from all stacks --------------------------------------- Key: JBWS-2612 URL: https://jira.jboss.org/jira/browse/JBWS-2612 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0 We're dropping support for AS 4.x series since JBossWS 3.2.0 -- 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

14 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2582) CXF ToolException: -p option cannot be used when wsdl contains mutiple schemas

by Alessio Soldano (JIRA)

CXF ToolException: -p option cannot be used when wsdl contains mutiple schemas ------------------------------------------------------------------------------ Key: JBWS-2582 URL: https://jira.jboss.org/jira/browse/JBWS-2582 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.1.1 Reporter: Alessio Soldano Running wsconsume against the jaxws/complex wsdl we get a org.apache.cxf.tools.common.ToolException: -p option cannot be used when wsdl contains mutiple schemas. This is a new behaviour introduced by CXF 2.2. -- 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

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2629) Transient failures in jaxws module of TCK

by Alessio Soldano (JIRA)

Transient failures in jaxws module of TCK ----------------------------------------- Key: JBWS-2629 URL: https://jira.jboss.org/jira/browse/JBWS-2629 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.0, jbossws-cxf-3.1.2 -- 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

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2628) Upgrade to Apache CXF 2.2.1

by Alessio Soldano (JIRA)

Upgrade to Apache CXF 2.2.1 --------------------------- Key: JBWS-2628 URL: https://jira.jboss.org/jira/browse/JBWS-2628 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.0, jbossws-cxf-3.1.2 -- 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

14 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2106) javax.xml.ws.addressing package not available in JBossWS-CXF

by Andrew Dinn (JIRA)

javax.xml.ws.addressing package not available in JBossWS-CXF ------------------------------------------------------------- Key: JBWS-2106 URL: http://jira.jboss.com/jira/browse/JBWS-2106 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-1.0.1 Reporter: Andrew Dinn The AddressingProperties and related API classes in the javax.xml.ws.addressing package are not available in JBossWS-CXF. These are needed for the Web Services Transactions 1.1 implementation to operate over the CXF stack. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
19
0 / 0

[JBoss JIRA] Created: (JBWS-2657) Provide testcase for common JSR-261 API

by Alessio Soldano (JIRA)

Provide testcase for common JSR-261 API --------------------------------------- Key: JBWS-2657 URL: https://jira.jboss.org/jira/browse/JBWS-2657 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0 -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2577) Update to Apache CXF 2.2

by Alessio Soldano (JIRA)

Update to Apache CXF 2.2 ------------------------ Key: JBWS-2577 URL: https://jira.jboss.org/jira/browse/JBWS-2577 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.1.1 CXF 2.2 is being released these days; once it's out we should update as it has interesting new features (WS-SecurityPolicy fo instance) and many bug fixes (including 3 patches I provided). -- 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

14 years, 11 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 May 2009