January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1601) Cannot start service endpoint: org.jboss.ws.WSException: Fault java type is not a java.lang.Exception: java.lang.String

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1601?page=all ] Thomas Diesler updated JBWS-1601: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Cannot start service endpoint: org.jboss.ws.WSException: Fault java type is not a java.lang.Exception: java.lang.String > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBWS-1601 > URL: http://jira.jboss.com/jira/browse/JBWS-1601 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-1.2.0.SP1 > Environment: Windows XP, J2SDK1.5, JAX-WS2.0, JAXB2.0 > Reporter: Geeta Pai > Fix For: jbossws-3.x > > > The webservice deployment fails with following error. > 2007-04-04 10:44:25,143 ERROR [org.jboss.ws.core.server.ServiceEndpointDeployer] Cannot start service endpoint > org.jboss.ws.WSException: Fault java type is not a java.lang.Exception: java.lang.String > at org.jboss.ws.metadata.umdm.FaultMetaData.eagerInitialize(FaultMetaData.java:216) > at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:472) > at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:509) > at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:495) > at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:483) > at org.jboss.ws.metadata.umdm.ServiceMetaData.eagerInitialize(ServiceMetaData.java:421) > at org.jboss.ws.metadata.umdm.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:192) > at org.jboss.ws.core.server.ServiceEndpoint.start(ServiceEndpoint.java:112) > at org.jboss.ws.core.server.ServiceEndpointManager.startServiceEndpoint(ServiceEndpointManager.java:631) > at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:143) > at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndpoint(DeployerInterceptor.java:144) > at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:96) > 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 $Proxy39.start(Unknown Source) > 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 sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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.GeneratedMethodAccessor9.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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:585) > 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:595) > 2007-04-04 10:44:25,143 DEBUG [org.jboss.ws.integration.jboss42.DeployerInterceptorJSE] destroy: -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1568) Provide/Verify WS-Addressing implementation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1568?page=all ] Thomas Diesler updated JBWS-1568: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Provide/Verify WS-Addressing implementation > ------------------------------------------- > > Key: JBWS-1568 > URL: http://jira.jboss.com/jira/browse/JBWS-1568 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1730) Investigate WS-Security with .NET 3.0

by Thomas Diesler (JIRA)

Investigate WS-Security with .NET 3.0 ------------------------------------- Key: JBWS-1730 URL: http://jira.jboss.com/jira/browse/JBWS-1730 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Fix For: jbossws-2.1.1 -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBWS-1570) Provide/Verify WS-Security implementation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1570?page=all ] Thomas Diesler updated JBWS-1570: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Provide/Verify WS-Security implementation > ----------------------------------------- > > Key: JBWS-1570 > URL: http://jira.jboss.com/jira/browse/JBWS-1570 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > > The scope of this is to pass the MSFT interop WS-Security 1.0 testsuite. > Details to follow ... > According to http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossWSSpecStatus we have > 100% WS-Security 1.0 > 90% WS-Security Username Token Profile 1.0 > 90% WS-Security X.509 Profile 1.0 > 0% WS-Security SAML Token Profile 1.0 > 0% WS-Security REL Token Profile 1.0 -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1734) Support for SOAP 1.2 in WSProvideTask and WSProvide

by Juergen Zimmermann (JIRA)

Support for SOAP 1.2 in WSProvideTask and WSProvide --------------------------------------------------- Key: JBWS-1734 URL: http://jira.jboss.com/jira/browse/JBWS-1734 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tools-jaxws Reporter: Juergen Zimmermann Support the generation of a WSDL file using SOAP 1.2 binding. The JAX-WS RI already provides this possibility. See https://jax-ws.dev.java.net/nonav/2.1.2m1/docs/wsgenant.html -- 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

16 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1632) Read / write wsdl extensibility elements on portType/operation/input

by Alessio Soldano (JIRA)

Read / write wsdl extensibility elements on portType/operation/input --------------------------------------------------------------------- Key: JBWS-1632 URL: http://jira.jboss.com/jira/browse/JBWS-1632 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assigned To: Alessio Soldano Priority: Minor Implementation of WS-Policy (issue http://jira.jboss.org/jira/browse/JBWS-856 ) is going to provide marshal and unmarshal mechanism of wsdl extensibility elements (including policies and policy references) to/from the unified wsdl structure. Extensibility elements on definitions/portType/operation/input are going to be ignored for now since processing them required some modifications to the unified wsdl structure; they are not to be ignored any more once this issue is solved. -- 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

16 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1635) Provide/Verify WS-PolicyAttachment implementation for all attachment point defined by specs

by Stefano Maestri (JIRA)

Provide/Verify WS-PolicyAttachment implementation for all attachment point defined by specs ------------------------------------------------------------------------------------------- Key: JBWS-1635 URL: http://jira.jboss.com/jira/browse/JBWS-1635 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stefano Maestri Assigned To: Stefano Maestri The first implementation just consider Port and EndPoint Level. Specs require also webservice, operation, input, message. -- 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

16 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-1636) Provide/Verify WS-PolicyAttachment implementation for UDDI

by Stefano Maestri (JIRA)

Provide/Verify WS-PolicyAttachment implementation for UDDI ---------------------------------------------------------- Key: JBWS-1636 URL: http://jira.jboss.com/jira/browse/JBWS-1636 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stefano Maestri Priority: Minor -- 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

16 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-1728) Investigate embedded JBossWS

by Thomas Diesler (JIRA)

Investigate embedded JBossWS ---------------------------- Key: JBWS-1728 URL: http://jira.jboss.com/jira/browse/JBWS-1728 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Fix For: jbossws-2.1.1 Endpoint.deploy() should work with jdk1.6 and possibly Jetty -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBWS-1547) WS-Policy integration support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1547?page=all ] Thomas Diesler updated JBWS-1547: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > WS-Policy integration support > ----------------------------- > > Key: JBWS-1547 > URL: http://jira.jboss.com/jira/browse/JBWS-1547 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: William DeCoste > Fix For: jbossws-3.x > > > Intuit request. Notes: > If WSS 1.1 is used, use WS-policy and WS-security policy to allow interoperability. > WS-Policy is implemented in JBossWS 1.2; however, there is currently no way of using it. It is expected that WS-Policy support will be available in JBossWS 1.2.1 (See "JBWS-856" in JIRA). -- 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

16 years, 10 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 January 2008