November 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2828) Update to Apache CXF 2.2.5

by Alessio Soldano (JIRA)

Update to Apache CXF 2.2.5 -------------------------- Key: JBWS-2828 URL: https://jira.jboss.org/jira/browse/JBWS-2828 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.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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2827) Update all stack to use comman-1.3.0-SNAPSHOT

by Jim Ma (JIRA)

Update all stack to use comman-1.3.0-SNAPSHOT --------------------------------------------- Key: JBWS-2827 URL: https://jira.jboss.org/jira/browse/JBWS-2827 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-native-3.2.1 Reporter: Jim Ma Fix For: jbossws-metro-3.2.2, jbossws-cxf-3.2.2, jbossws-native-3.2.2 Since the issue JBWS-2826 is fixed, we need to update all stacks to use 1.3.0-snapshot to ship that fix. -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2826) Give more time to copy the process inputstream and error stream in JBossWSTest

by Jim Ma (JIRA)

Give more time to copy the process inputstream and error stream in JBossWSTest ------------------------------------------------------------------------------ Key: JBWS-2826 URL: https://jira.jboss.org/jira/browse/JBWS-2826 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-metro-3.2.2, jbossws-cxf-3.2.2, jbossws-native-3.2.2 When executeCommand finish , the CopyJob thread will be killed immediately . It does not have time to copy the command execution result content . -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2647) Reference to jboss-xml-binding.jar in ws scripts should be changed to match name in repository.

by Paul Gier (JIRA)

Reference to jboss-xml-binding.jar in ws scripts should be changed to match name in repository. ----------------------------------------------------------------------------------------------- Key: JBWS-2647 URL: https://jira.jboss.org/jira/browse/JBWS-2647 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Gier Currently the webservices startup scripts refer to the jar "jboss-xml-binding.jar". These should be changed to match the name of the jar in the repository "jbossxb.jar" -- 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, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2775) WSRM Client does apply WS-Addressing correctly

by Hans Guldager Knudsen (JIRA)

WSRM Client does apply WS-Addressing correctly ---------------------------------------------- Key: JBWS-2775 URL: https://jira.jboss.org/jira/browse/JBWS-2775 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.0 Reporter: Hans Guldager Knudsen Hi! I tried to use the JBoss-native WS-RM client - but it seems that WS Addressing is not applied correctly. I tried following the tuturial at : http://www.jboss.org/community/wiki/JBossWS-NativeWS-ReliableMessagingTut... also present as testcase in modules/testsuite/native-tests/src/test/java/org/jboss/test/ws/jaxws/samples/wsrm I will attach logs from my HTTP monitor from JBoss + SUN's Metro - to show the differences. -- 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, 5 months

2
12
0 / 0

[JBoss JIRA] Created: (JBWS-2825) Remove dependency on cxf-anttasks

by Alessio Soldano (JIRA)

Remove dependency on cxf-anttasks --------------------------------- Key: JBWS-2825 URL: https://jira.jboss.org/jira/browse/JBWS-2825 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.2.2 This should not be required -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2654) NumberFormatException when using StubExt.PROPERTY_CLIENT_TIMEOUT

by Pras P (JIRA)

NumberFormatException when using StubExt.PROPERTY_CLIENT_TIMEOUT ---------------------------------------------------------------- Key: JBWS-2654 URL: https://jira.jboss.org/jira/browse/JBWS-2654 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.5 Environment: RHEL Reporter: Pras P This bug is similar to https://jira.jboss.org/jira/browse/JBWS-1410 however, it still exists in 3.0.5 when used with soapAddress which looks like http://10.10.10.204:8557 and a timeout is set using StubExt.PROPERTY_CLIENT_TIMEOUT Looks like there is a parsing error where the port is also carried over (8557 in the exception below is a port) 2009-05-20 21:50:02,181 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception java.lang.NumberFormatException: For input string: "8557?timeout=60000" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:456) at java.lang.Integer.parseInt(Integer.java:497) at org.jboss.remoting.InvokerLocator.<init>(InvokerLocator.java:191) at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:206) at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) The exception does not occur when a soapAddress is of the following format http://10.10.10.204:8557/adm/admWS -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2746) ClassCastException because SOAPEnvelopeImpl blindly casts to o.j.ws.core.soap.SOAPElementImpl

by Jürgen Hoffmann (JIRA)

ClassCastException because SOAPEnvelopeImpl blindly casts to o.j.ws.core.soap.SOAPElementImpl --------------------------------------------------------------------------------------------- Key: JBWS-2746 URL: https://jira.jboss.org/jira/browse/JBWS-2746 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.0 Environment: Windows Vista Ultimate, java6, Axis2 Reporter: Jürgen Hoffmann Priority: Critical Recently I've started working with JBoss, and I think I've located a problem in JBossWS. The constructor of org.jboss.ws.core.soap.SOAPEnvelopeImpl blindly casts a given implementation of javax.xml.soap.SOAPElement to org.jboss.ws.core.soap.SOAPElementImpl, which results in a ClassCastException in the application I'm working on. public SOAPEnvelopeImpl(SOAPPartImpl soapPart, SOAPElement element, boolean addHeaderAndBody) throws SOAPException { super((SOAPElementImpl)element); This constructor is used in org.jboss.ws.core.soap.EnvelopeBuilderDOM: SOAPEnvelopeImpl soapEnv = new SOAPEnvelopeImpl(soapPart, soapFactory.createElement(domEnv, false), false); The Method org.jboss.ws.core.soap.SOAPFactoryImpl.createElement(Element,boolean) does not necessarily return an instance of org.jboss.ws.core.soap.SOAPElementImpl, but might return any other class which implements javax.xml.soap.SOAPElement, because it does not use its own method createElement(String,String,String) to create the SOAPElement, but rather obtains a different Object which also extends javax.xml.soap.SOAPFactory and delegated to that other subclass of javax.xml.soap.SOAPFactory. SOAPFactory factory = SOAPFactory.newInstance(); SOAPElement soapElement = factory.createElement(localName, prefix, nsURI); I don't understand why this is done in a non-static method of a class which also extends SOAPFactory. Wouldn't it be better so simply do the following? SOAPElement soapElement = this.createElement(localName, prefix, nsURI); This would return new SOAPElementImpl(localName, prefix, uri) and the cast in SOAPEnvelopeImpl would work. Otherwise SOAPEnvelopeImpl would have to be modified to handle other implemetations of javax.xml.soap.SOAPElement, which might be more complicated. In the specific case where I stumbled over this problem the exception was: java.lang.ClassCastException: org.apache.axis2.saaj.SOAPElementImpl cannot be cast to org.jboss.ws.core.soap.SOAPElementImpl at org.jboss.ws.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:57) The application includes modules which use Axis2 as a SOAP client. JARs includes with the application always appear in the classpath before JBossWS. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBWS-751) Multiple schema imports with the same namespace

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-751?page=com.atlassian.jira.plugi... ] Alessio Soldano updated JBWS-751: --------------------------------- Fix Version/s: jbossws-native-3.2.2 > Multiple schema imports with the same namespace > ----------------------------------------------- > > Key: JBWS-751 > URL: https://jira.jboss.org/jira/browse/JBWS-751 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Reporter: Thomas Diesler > Assignee: Richard Opalka > Fix For: jbossws-native-3.2.2 > > > <types> > <xs:schema> > <xs:import namespace="uri:tranHistory" schemaLocation="TransactionHistoryRq.xsd"/> > <xs:import namespace="uri:tranHistory" schemaLocation="TransactionHistoryRs.xsd"/> > <xs:import namespace="uri:tranHistory" schemaLocation="StatusRs.xsd"/> > </xs:schema> > </types> > Current handling of schema imports is incorrect, since it does not allow for multiple imports with the same namespace. > private void handleSchemaImports(Element schemaEl, URL wsdlLoc) throws MalformedURLException > { > if (wsdlLoc == null) > throw new IllegalArgumentException("Cannot process import, parent location not set"); > > Iterator it = DOMUtils.getChildElements(schemaEl, new QName(Constants.NS_SCHEMA_XSD, "import")); > while (it.hasNext()) > { > Element includeEl = (Element)it.next(); > String schemaLocation = includeEl.getAttribute("schemaLocation"); > String namespace = includeEl.getAttribute("namespace"); > > log.trace("handleSchemaImport: [namespace=" + namespace + ",schemaLocation=" + schemaLocation + "]"); > > // Skip, let the entity resolver resolve these > if (namespace.length() > 0 && schemaLocation.length() > 0) > { > URL currLoc = this.getLocationURL(wsdlLoc, schemaLocation); > schemaLocationsMap.put(namespace, currLoc); > } > else > { > log.warn("Skip invalid schema import: [namespace=" + namespace + ",schemaLocation=" + schemaLocation + "]"); > } > } > } -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2824) test.log file not found exception when run the testsuite and wsprovide command log4j configuration is not initilized error

by Jim Ma (JIRA)

test.log file not found exception when run the testsuite and wsprovide command log4j configuration is not initilized error --------------------------------------------------------------------------------------------------------------------------- Key: JBWS-2824 URL: https://jira.jboss.org/jira/browse/JBWS-2824 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-3.2.2 When running the cxf testsuite and framework test , there is test.log not found exception . Install jbossws-cxf stack and run the wsprovide.sh , it complains log4j configuration not initialized error as CXF's java2ws tool needs log4j configuration. -- 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, 5 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 November 2009