October 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2809) Investigate why MemoryBufferRecorderTestCase is failing

by Richard Opalka (JIRA)

Investigate why MemoryBufferRecorderTestCase is failing ------------------------------------------------------- Key: JBWS-2809 URL: https://jira.jboss.org/jira/browse/JBWS-2809 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Fix For: jbossws-cxf-3.3 -- 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
4
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-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] Created: (JBWS-2771) Importes XSD´s schemaLocation URL Port not changed when "webServicePort" property set in stack-agnostic-jboss-beans.xml

by David Calvente (JIRA)

Importes XSD´s schemaLocation URL Port not changed when "webServicePort" property set in stack-agnostic-jboss-beans.xml ----------------------------------------------------------------------------------------------------------------------- Key: JBWS-2771 URL: https://jira.jboss.org/jira/browse/JBWS-2771 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.0 Environment: Debian, JDK 1.6.0-13, JBoss 5.1 with Patched JBossWS 3.2.0 Native (Patched means https://jira.jboss.org/jira/browse/JBWS-2759). Also in WinXP Reporter: David Calvente Priority: Critical In an environtment where JBoss 5.1 is behind an Apache ReverseProxy, JBoss running on port 8080, but accessed via reverse proxy via port 80, you can use stack-agnostic-jboss-beans.xml to modify: host name: <property name="webServiceHost">jbossws.undefined.host</property> <property name="modifySOAPAddress">true</property> and Port: <property name="webServicePort">80</property> This works OK for endPoint: <soap:address location="http://server.domain.com:80/typex/ws"/> Uses Port 80 as specified!! BUT leaves unmodified Port for schemaLocation: "http://server.domain.com:8080/typex/ws?wsdl&resource=TXM_Fault.xsd"/> Uses JBoss port and NOT 80 !!! So, when a client tries to use the WSDL it can't find the referenced XSD's failing!! -- 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-2651) ClassCast Exception in case of malformed webservice response

by Gandulf Kohlweiss (JIRA)

ClassCast Exception in case of malformed webservice response ------------------------------------------------------------ Key: JBWS-2651 URL: https://jira.jboss.org/jira/browse/JBWS-2651 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.1 Environment: Windows XP JDK 1.6 JBoss 4.2.3 GA JBossWs 3.1.1 Reporter: Gandulf Kohlweiss At the moment jbossws throws a ClassCast Exception in case of an illegal webservice response (missing closing tag, etc...) : [code] Caused by: javax.xml.ws.WebServiceException: java.lang.ClassCastException: org.jboss.ws.core.soap.Te xtImpl cannot be cast to org.jboss.ws.core.soap.SOAPElementI mpl at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) at $Proxy311.bookOrders(Unknown Source) at com.skidata.dta.server.co.v3_0.classic.impl.BookOrdersHelper.invoke(BookOrdersHelper.java :46) ... 12 more Caused by: java.lang.ClassCastException: org.jboss.ws.core.soap.TextImpl cannot be cast to org.jboss .ws.core.soap.SOAPElementImpl at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:894) at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:634) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) ... 16 more [/code] It would be helpful to get the actual Parse Excpetion from the xml parser instead of this classcastexcpetion. Digging through the code i found out that this might occur because the MessageFectory to parse the response is initialized with ignoreParseErrors = true. e.g in the SOAPMessageUnMarshallerHTTP at line 82 (source .3.1.1.GA) [code] MimeHeaders mimeHeaders = getMimeHeaders(metadata); soapMsg = getMessageFactory().createMessage(mimeHeaders, inputStream, true); [/code] -- 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

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2769) Make sure our test suites for all stacks pass on Windows XP

by Richard Opalka (JIRA)

Make sure our test suites for all stacks pass on Windows XP ----------------------------------------------------------- Key: JBWS-2769 URL: https://jira.jboss.org/jira/browse/JBWS-2769 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-metro-3.2.0, jbossws-cxf-3.2.0, jbossws-native-3.2.0 Environment: Windows XP, Java 5 Reporter: Richard Opalka Assignee: Jim Ma Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 Make sure our test suites pass on Windows XP (for all three stacks). I noticed there are some failures on Windows XP related to attachments when running the tests (maybe others) in Native stack. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBWS-2692) Define client/server security policy for JBWS testsuite and run it under a security manager

by Alessio Soldano (JIRA)

Define client/server security policy for JBWS testsuite and run it under a security manager ------------------------------------------------------------------------------------------- Key: JBWS-2692 URL: https://jira.jboss.org/jira/browse/JBWS-2692 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 We should start from the server.policy and client.policy that comes in the AS testsuite (see testsuite/src/resources/securitymgr). Those policies most probably require additions for some trusted libraries used by jbossws-native and apache cxf. The goal is being able to run the whole testsuite under a security manager. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBWS-2770) Rewrite org.jboss.test.ws.jaxws.binding testcase to get SOAPMessageContext from handlers

by Alessio Soldano (JIRA)

Rewrite org.jboss.test.ws.jaxws.binding testcase to get SOAPMessageContext from handlers ---------------------------------------------------------------------------------------- Key: JBWS-2770 URL: https://jira.jboss.org/jira/browse/JBWS-2770 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-cxf-3.3, jbossws-metro-3.3, jbossws-native-3.3 We have @Resource public WebServiceContext context; public String namespace() { try { SOAPMessageContext msgContext = (SOAPMessageContext)context.getMessageContext(); SOAPMessage soapMessage = msgContext.getMessage(); SOAPEnvelope soapEnvelope = (SOAPEnvelope)soapMessage.getSOAPPart().getEnvelope(); String nsURI = soapEnvelope.getNamespaceURI(); log.info(nsURI); return nsURI; } catch (SOAPException ex) { throw new WebServiceException(ex); } } in an endpoint. The SOAPMessageContext can be obtained from handlers only, so the SOAPMessageContext retrieval should be done in a server side handler. This is related to CXF-1511 -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2009