November 2009 - jbossws-issues - Jboss List Archives

[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

15 years, 1 month

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

15 years, 1 month

3
6
0 / 0

[JBoss JIRA] Updated: (JBWS-2725) wsonsume doesn't like the contract app URLs (http://localhost:8080/contract)

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2725?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2725: ---------------------------------- Fix Version/s: jbossws-native-3.2.2 (was: jbossws-native-3.3) > wsonsume doesn't like the contract app URLs (http://localhost:8080/contract) > ---------------------------------------------------------------------------- > > Key: JBWS-2725 > URL: https://jira.jboss.org/jira/browse/JBWS-2725 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native, tools-jaxws > Affects Versions: jbossws-2.0.2 > Reporter: Tom Fennelly > Assignee: Alessio Soldano > Fix For: jbossws-native-3.2.2 > > > The WSDL URL for ESB based webservices are of the form "http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory&...". The wsconsume tool doesn't like them. See the example below. Might be a JBossWS specific issue at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:190). > wsconsume -v -k -o /Jboss/ESB/trunk/product/samples/quickstarts/webservice_producer/build/wsclient http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory&... > parsing WSDL... > [ERROR] Content is not allowed in prolog. > line 12 of http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory > [ERROR] Failed to read the WSDL document: http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory, because 1) could not find the document; /2) the document could not be read; 3) the root element of the document is not <wsdl:definitions>. > unknown location > Failed to parse the WSDL. > Failed to invoke WsImport > java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information > at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:190) > at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:216) > at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:79) > 'serviceName' is not recognized as an internal or external command, > operable program or batch file. > 'protocol' is not recognized as an internal or external command, > operable program or batch file. -- 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

15 years, 1 month

1
0
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

15 years, 1 month

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

15 years, 1 month

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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2765) Verify loggin redirection

by Alessio Soldano (JIRA)

Verify loggin redirection ------------------------- Key: JBWS-2765 URL: https://jira.jboss.org/jira/browse/JBWS-2765 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano The message here http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161098 correctly points out there's a difference between the doc and what is actually deployed on AS 5. Perhaps the doc was referring to the deployment on AS 4.2 and needs to be updated. Anyway I don't see the cxf-extension-jbossws.xml anywhere... the test covering this has to be revisited. -- 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

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2806) Wrong parameter number exception with explicit soap headers

by Alessio Soldano (JIRA)

Wrong parameter number exception with explicit soap headers ----------------------------------------------------------- Key: JBWS-2806 URL: https://jira.jboss.org/jira/browse/JBWS-2806 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.2.1 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.3 See https://issues.apache.org/jira/browse/CXF-2498 -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2817) org.jboss.test.ws.jaxws.jbws1666.JBWS1666TestCase hangs on Windows

by Jim Ma (JIRA)

org.jboss.test.ws.jaxws.jbws1666.JBWS1666TestCase hangs on Windows ------------------------------------------------------------------ Key: JBWS-2817 URL: https://jira.jboss.org/jira/browse/JBWS-2817 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Fix For: jbossws-cxf-3.3 Running org.jboss.test.ws.jaxws.jbws1666.JBWS1666TestCase Executing command: java -Djava.endorsed.dirs=c:\code\jbossws\lab\jboss-5.1.0.GA\lib\endorsed -cp C:\code\jbossws\stack\cxf\trunk\modules\testsuite\framework-tests\target/test-classes;c:\code\jbossws\lab\jboss-5.1.0.GA\client\jbossws-cxf- client.jar;c:\code\jbossws\lab\jboss-5.1.0.GA\client\jboss-common-core.jar;c:\code\jbossws\lab\jboss-5.1.0.GA\client\jboss-javaee.jar org.jboss.test.ws.jaxws.jbws1666.TestClient localhost -- 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

15 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1800) Trying to monitor the JVM using -Dcom.sun.management.jmxremote prevents the jbossws 2.0.1 from coming up

by Raju Koganty (JIRA)

Trying to monitor the JVM using -Dcom.sun.management.jmxremote prevents the jbossws 2.0.1 from coming up -------------------------------------------------------------------------------------------------------- Key: JBWS-1800 URL: http://jira.jboss.com/jira/browse/JBWS-1800 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.1 Environment: JBossWS 2.0.1 on JBoss 4.0.5 with JDK 1.6 Reporter: Raju Koganty Having -Dcom.sun.management.jmxremote in the startup args to monitor the JVM causes this exception during startup and jbossws 2.0.1 doesn't come up : And here is the exception : java.lang.NullPointerException at org.jboss.wsf.stack.jbws.WSDLFilePublisher.getPublishLocation(WSDLFilePublisher.java:303) at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:103) at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) at org.jboss.wsf.container.jboss40.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss40.DeployerInterceptor.start(DeployerInterceptor.java:90) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy29.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:490) at java.lang.Thread.run(Thread.java:619) -- 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

15 years, 1 month

6
7
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