March 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3618) Add wstx dependency to org.apache.cxf module

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3618: ------------------------------------- Summary: Add wstx dependency to org.apache.cxf module Key: JBWS-3618 URL: https://issues.jboss.org/browse/JBWS-3618 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2 Latest snapshot of Apache CXF has direct dependency on woodstox, so we need to update the jboss modules dependencies accordingly. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3617) Quick/easy setup of ws projects

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3617: ------------------------------------- Summary: Quick/easy setup of ws projects Key: JBWS-3617 URL: https://issues.jboss.org/browse/JBWS-3617 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano We'd need a solution / tool for quick/easy setup of ws projects (Maven archetype? extension to JBoss Forge?) -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3615) Hudson / Jenkins update on jbossws.jboss.org

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3615?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3615: ---------------------------------- Issue Type: Task (was: Feature Request) > Hudson / Jenkins update on jbossws.jboss.org > -------------------------------------------- > > Key: JBWS-3615 > URL: https://issues.jboss.org/browse/JBWS-3615 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: productization > Reporter: Alessio Soldano > > The CI tool at http://jbossws.jboss.org:8180/hudson needs to be updated, most likely by moving to a recent Jenkins version. > The currently used Hudson version does not run on JDK7 btw... > This task possibly includes producing new jobs as the current xml configurations might not work on the new version. Jobs conf has to go on living on scm in any case. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3616) Review reflection usage in JBossWS and Apache CXF

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3616?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3616: ---------------------------------- Issue Type: Task (was: Feature Request) > Review reflection usage in JBossWS and Apache CXF > ------------------------------------------------- > > Key: JBWS-3616 > URL: https://issues.jboss.org/browse/JBWS-3616 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > > Both in JBossWS (jbws-common, jbws-cxf) and in Apache CXF, we do have code doing Class::getAnnotations() and in general relying on reflection / introspection. The impact (deployment and runtime) of that should be measured / evaluated and depending on the result we could evaluate providing an abstraction for relying on the jandex index of AS7/8. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3616) Review reflection usage in JBossWS and Apache CXF

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3616: ------------------------------------- Summary: Review reflection usage in JBossWS and Apache CXF Key: JBWS-3616 URL: https://issues.jboss.org/browse/JBWS-3616 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Both in JBossWS (jbws-common, jbws-cxf) and in Apache CXF, we do have code doing Class::getAnnotations() and in general relying on reflection / introspection. The impact (deployment and runtime) of that should be measured / evaluated and depending on the result we could evaluate providing an abstraction for relying on the jandex index of AS7/8. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3581) org.jboss.ws.WSException: Target endpoint address not set

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3581?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3581: --------------------------------------- The jbossws-native stack has reached EOL and is hence not supported anymore in community versions. Please check if this is an outstanding issue with current jbossws-cxf stack, otherwise this will simply be closed. Thanks. > org.jboss.ws.WSException: Target endpoint address not set > --------------------------------------------------------- > > Key: JBWS-3581 > URL: https://issues.jboss.org/browse/JBWS-3581 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.1.2 > Environment: windows xp,Sun JDK1.6, jboss-eap-5.1.2 > Reporter: ma yong > Labels: jboss > > 16:14:32,562 WARN [ServiceDelegateImpl] Cannot access wsdlURL: https://127.0.0.1/GHQInfoService?WSDL > 16:14:37,500 WARN [ServiceDelegateImpl] Cannot get port meta data for: {http://127.0.0.1/ghd/target/GHQInfoService}GHQInfoServicePort > 16:14:39,094 ERROR [CommonClient] Exception caught while (preparing for) performing the invocation: > org.jboss.ws.WSException: Target endpoint address not set > at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:350) > at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:232) > at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:171) > at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:157) -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3584) Cannot configure timeout when reading WSDL creating javax.xml.ws.Service

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3584?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3584: ---------------------------------- Fix Version/s: community contributions > Cannot configure timeout when reading WSDL creating javax.xml.ws.Service > ------------------------------------------------------------------------ > > Key: JBWS-3584 > URL: https://issues.jboss.org/browse/JBWS-3584 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.1.2 > Reporter: Rafael Sisto > Fix For: community contributions > > > When creating a new WS client using: > new javax.xml.ws.Service(URL wsdlLocation, QName serviceName) > If the URL successfully connects to the server holding the WSDL resource, when trying to read the file the WS client may hang waiting for the resource. > The only way to avoid this is configuring the system property: sun.net.client.defaultReadTimeout (-1 by default, no timeout), which may affect other functionalities. > This can be avoided storing the WSDL locally. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3601) SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3601?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3601: --------------------------------------- >From a community point of view, the fix for this is coming in next CXF version. Scheduling for jbossws-cxf-4.2 > SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF > -------------------------------------------------------------- > > Key: JBWS-3601 > URL: https://issues.jboss.org/browse/JBWS-3601 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBoss Enterprise Application Platform 6 > Reporter: Tadayoshi Sato > Assignee: Alessio Soldano > Labels: cxf > Fix For: jbossws-cxf-4.2 > > > Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render {{<soapenv:Subcode>}}. > {code} > import javax.xml.soap.SOAPConstants; > import javax.xml.soap.SOAPFactory; > import javax.xml.soap.SOAPFault; > import javax.xml.ws.soap.SOAPFaultException; > ... > SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); > SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); > fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); > ... > throw new SOAPFaultException(fault); > {code} -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3601) SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3601?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3601: ---------------------------------- Assignee: Alessio Soldano > SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF > -------------------------------------------------------------- > > Key: JBWS-3601 > URL: https://issues.jboss.org/browse/JBWS-3601 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBoss Enterprise Application Platform 6 > Reporter: Tadayoshi Sato > Assignee: Alessio Soldano > Labels: cxf > Fix For: jbossws-cxf-4.2 > > > Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render {{<soapenv:Subcode>}}. > {code} > import javax.xml.soap.SOAPConstants; > import javax.xml.soap.SOAPFactory; > import javax.xml.soap.SOAPFault; > import javax.xml.ws.soap.SOAPFaultException; > ... > SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); > SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); > fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); > ... > throw new SOAPFaultException(fault); > {code} -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3601) SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3601?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3601: ---------------------------------- Fix Version/s: jbossws-cxf-4.2 > SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF > -------------------------------------------------------------- > > Key: JBWS-3601 > URL: https://issues.jboss.org/browse/JBWS-3601 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBoss Enterprise Application Platform 6 > Reporter: Tadayoshi Sato > Labels: cxf > Fix For: jbossws-cxf-4.2 > > > Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render {{<soapenv:Subcode>}}. > {code} > import javax.xml.soap.SOAPConstants; > import javax.xml.soap.SOAPFactory; > import javax.xml.soap.SOAPFault; > import javax.xml.ws.soap.SOAPFaultException; > ... > SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); > SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); > fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); > ... > throw new SOAPFaultException(fault); > {code} -- 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

11 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 2013