December 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2291) Problem with Deploy and undeploy JBossWS-native-3.0.3.GA

by Kamil Demecki (JIRA)

Problem with Deploy and undeploy JBossWS-native-3.0.3.GA -------------------------------------------------------- Key: JBWS-2291 URL: https://jira.jboss.org/jira/browse/JBWS-2291 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3 Reporter: Kamil Demecki After deploy JBossWS-native-3.0.3.GA on JBossAS 4.2.2.GA and next undeploy, replace with JBossWS-native-2.0.3.GA (which comes with defaults) there is problem when server starts. -- 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, 12 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2439) WS-Eventing and subscription expiration time - restore changes

by Alessio Soldano (JIRA)

WS-Eventing and subscription expiration time - restore changes -------------------------------------------------------------- Key: JBWS-2439 URL: https://jira.jboss.org/jira/browse/JBWS-2439 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Fix For: community contributions -- 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

16 years

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2438) WSDLFilePublisher prematurely stops publishing schema imports

by Ryan Prichard (JIRA)

WSDLFilePublisher prematurely stops publishing schema imports ------------------------------------------------------------- Key: JBWS-2438 URL: https://jira.jboss.org/jira/browse/JBWS-2438 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.5 Reporter: Ryan Prichard In the publishSchemaImports method, the code that prevent infinate loops should continue to the next item in the list instead of returning from the function. The following scenario would prematurely stop Schema2.xsd -- Import Schema3.xsd Schema1.xsd -- import Schema2.xsd -- import Schema3.xsd -- Import Schema4.xsd ..... -- Import SchemaN.xsd In this schenario, Schema4.xsd - SchemaN.xsd wouldn't be published -- 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

16 years

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2331) Exploded deployment: web.xml modified to web.xml.org - Subsequent runs fail

by Ralf Taugerbeck (JIRA)

Exploded deployment: web.xml modified to web.xml.org - Subsequent runs fail --------------------------------------------------------------------------- Key: JBWS-2331 URL: https://jira.jboss.org/jira/browse/JBWS-2331 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.0.3 Environment: win32, jboss AS 4.2.3 GA, jdk 1.5.0_15 Reporter: Ralf Taugerbeck When using exploded EAR/WAR deployment web.xml is modified on each server start. That has two effects: - the original web.xml, which was renamed to web.xml.org after 1st start is lost on 2nd server start - the context parameter jbossws.cxf.beans.url is added to web.xml multiple times My web.xml on second server start: <web-app> ... <context-param> <param-name>jbossws.cxf.beans.url</param-name> <param-value>file:/D:/Tools/jboss-4.2.3.GA/server/default/tmp/jbossws/jbossws-cxf29799.xml</param-value> </context-param> <context-param> <param-name>jbossws.cxf.beans.url</param-name> <param-value>file:/D:/Tools/jboss-4.2.3.GA/server/default/tmp/jbossws/jbossws-cxf58750.xml</param-value> </context-param> </web-app> The exception is: ... Caused by: java.lang.IllegalArgumentException: Duplicate context initialization parameter jbossws.cxf.beans.url at org.apache.catalina.core.StandardContext.addParameter(StandardContext.java:2332) -- 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

16 years

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2119) WebServiceRef injection from DD doesn't work

by Thomas Diesler (JIRA)

WebServiceRef injection from DD doesn't work -------------------------------------------- Key: JBWS-2119 URL: http://jira.jboss.com/jira/browse/JBWS-2119 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.1 Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-native-2.0.3 Specifying a service-ref in ejb-jar.xml like this doesn't work. <?xml version="1.0" encoding="UTF-8"?> <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0"> <description>jBoss test application </description> <display-name>Test</display-name> <enterprise-beans> <session> <ejb-name>StatelessBean</ejb-name> <service-ref> <service-ref-name>service/Endpoint3</service-ref-name> <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface> <mapped-name>jbossws-client/service/TestService</mapped-name> <injection-target> <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class> <injection-target-name>endpoint3</injection-target-name> </injection-target> </service-ref> </session> </enterprise-beans> </ejb-jar> -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2114) Soap attachments are dropped on server response when added in ejb3 jaxws handler

by Thomas Diesler (JIRA)

Soap attachments are dropped on server response when added in ejb3 jaxws handler -------------------------------------------------------------------------------- Key: JBWS-2114 URL: http://jira.jboss.com/jira/browse/JBWS-2114 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Environment: windows, linux, jdk1.5 Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-2.0.0 Soap attachments were dropped on server responses. Attachment can be added on a handler's handleResponse method; however it mysteriously disappeared on the outgoing soap message. The problem was in the ServiceEndpointInvoker. It overwrote the SOAPMessage in the MessageContext. In this class, the method invokeServiceEndpoint was overwritten by ServiceEndpointInvokerEJB21, which invokes the EJB via the ServiceEndpointInterceptor. This ServiceEndpointInterceptor invokes the EJB and also the handlers; it creates the correct SOAPMessage and sets it in the ContextContext. Unfortunately, it was overwritten later by the ServiceEndpointInvoker. Fixes are attached. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2195) MTOM services seem to return two extra bytes at the end

by Heiko Braun (JIRA)

MTOM services seem to return two extra bytes at the end ------------------------------------------------------- Key: JBWS-2195 URL: http://jira.jboss.com/jira/browse/JBWS-2195 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.1 Reporter: Heiko Braun Fix For: jbossws-native-3.0.3 -- 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

4
4
0 / 0

[JBoss JIRA] Created: (JBWS-2434) Failure in deployment of EJB3 WS prevents redeployment

by Jose Antonio (JIRA)

Failure in deployment of EJB3 WS prevents redeployment ------------------------------------------------------ Key: JBWS-2434 URL: https://jira.jboss.org/jira/browse/JBWS-2434 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Environment: JDK 1.6_07, Ubuntu 8.04, JBoss 4.2.3 Reporter: Jose Antonio I'm using EJB3 Web services in a project in JBoss 4.2.3. If I try to deploy my EAR and it fails for whatever reason in the web service deployment task, then, I try to redeploy the corrected ear and I get: java.lang.IllegalStateException: Endpoint already registered: jboss.ws:context=services,endpoint=AuthWS at org.jboss.wsf.framework.management.DefaultEndpointRegistry.register(DefaultEndpointRegistry.java:89) at org.jboss.wsf.framework.management.ManagedEndpointRegistry.register(ManagedEndpointRegistry.java:59) at org.jboss.wsf.framework.deployment.EndpointRegistryDeploymentAspect.create(EndpointRegistryDeploymentAspect.java:49) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss42.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 $Proxy34.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.GeneratedMethodAccessor21.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 $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) In the undeployment it should unregister the endpoint, even if it has failed to deploy or only register the endpoint once it has been correctly deployed. Could be related to: https://jira.jboss.org/jira/browse/EJBTHREE-962 -- 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

16 years

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2337) Compatibility issues with using single quoted namespace attributes.

by Jacob Barrett (JIRA)

Compatibility issues with using single quoted namespace attributes. ------------------------------------------------------------------- Key: JBWS-2337 URL: https://jira.jboss.org/jira/browse/JBWS-2337 Project: JBoss Web Services Issue Type: Patch Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3 Environment: OSX 10.5, Java 1.6 Reporter: Jacob Barrett The serializer currently produces the envelope namespace with single quotes around it. While completely valid there are some poorly implemented web service platforms out there that don't parse single quoted attribute values properly. The fix is to double quote the value. -- 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

16 years

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2288) Exception handling issue in org.jboss.ws.core.CommonClient.

by aodhan hoffman (JIRA)

Exception handling issue in org.jboss.ws.core.CommonClient. ----------------------------------------------------------- Key: JBWS-2288 URL: https://jira.jboss.org/jira/browse/JBWS-2288 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3 Environment: Shown running JBossAS 4.2.2 & 4.2.3, JBossWS 3.0.1 & 3.0.3 on windows XP, JVM 1.5.0_15 Reporter: aodhan hoffman In troubleshooting a problem another user, PeterJ, found what looks like a coding error at line 404 in org.jboss.ws.core.CommonClient.invoke(). Exception is caught but details are not logged before another method is called which in turn causes another exception. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141051 I tried using JBossWS 3.x stand alone, stock downloads of JBossAS 4.2.x and JBossAS 4.2.x updated to JBossWS 3.0.1, 3.0.2, & 3.0.3. All versions of JBossWS 3.0.x appear to contain this code segment. // Stacktrace Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.IllegalStateException: Cannot find property: java x.xml.ws.handler.message.outbound 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 $Proxy19.update(Unknown Source) at com.boeing.nmt.nls.mv4client.MV4Client.disableTag(MV4Client.java:308) at com.boeing.nmt.nls.test.AssetTest.main(AssetTest.java:25) Caused by: java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbound at org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.processPivot(MessageContextJAXWS.java:109) at org.jboss.ws.core.jaxws.client.ClientImpl.processPivot(ClientImpl.java:363) at org.jboss.ws.core.CommonClient.processPivotInternal(CommonClient.java:476) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:404) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) // Lines 401-420 of CommonClient.java // http://anonsvn.jboss.org/repos/jbossws/stack/native/trunk/modules/core/sr... catch (Exception ex) { // Reverse the message direction processPivotInternal(msgContext, direction); // <-- line 404, where the later exception gets thrown if (faultType[2] != null) callFaultHandlerChain(portName, faultType[2], ex); if (faultType[1] != null) callFaultHandlerChain(portName, faultType[1], ex); if (faultType[0] != null) callFaultHandlerChain(portName, faultType[0], ex); throw ex; } finally { closeHandlerChain(portName, handlerType[2]); closeHandlerChain(portName, handlerType[1]); closeHandlerChain(portName, handlerType[0]); } -- 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

16 years

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues December 2008