June 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2226) Investigate why multiple virtual hosts test fails on CXF

by Richard Opalka (JIRA)

Investigate why multiple virtual hosts test fails on CXF -------------------------------------------------------- Key: JBWS-2226 URL: http://jira.jboss.com/jira/browse/JBWS-2226 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-cxf-3.0.3 See jaxws/jbws1178 test case -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2225) wsconsume for cxf maven build

by Richard Opalka (JIRA)

wsconsume for cxf maven build ----------------------------- Key: JBWS-2225 URL: http://jira.jboss.com/jira/browse/JBWS-2225 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Fix For: jbossws-cxf-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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2220) jbossws-native-3.0.2 errata

by Thomas Diesler (JIRA)

jbossws-native-3.0.2 errata --------------------------- Key: JBWS-2220 URL: http://jira.jboss.com/jira/browse/JBWS-2220 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Richard Opalka Assigned To: Thomas Diesler Fix For: jbossws-metro-3.0.2 -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2224) jbossws-metro-3.0.2 errata

by Alessio Soldano (JIRA)

jbossws-metro-3.0.2 errata -------------------------- Key: JBWS-2224 URL: http://jira.jboss.com/jira/browse/JBWS-2224 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Fix For: jbossws-metro-3.0.2 AS 4.2.2 # [JBWS-1673] Fix JAXR samples for Metro # [JBWS-1674] Fix @WebServiceRef with Metro # [JBWS-2127] Cannot generate WSDL for binding "http://www.w3.org/2003/05/soap/bindings/HTTP/" # [JBWS-2128] DefaultHttpContext is not a supported context. # [JBWS-2129] Wrapper class is not found # [JBWS-2130] WebServiceException: null is not a valid service # [JBWS-2131] WebServiceException: Failed to build METRO runtime model # [JBWS-2132] IllegalArgumentException: protocol = http host = null # [JBWS-2133] Failed to access the WSDL # [JBWS-2134] Fault string, and possibly fault code, not set # [JBWS-2135] WebServiceException: Undefined port type # [JBWS-2136] ClassCastException: com.sun.xml.ws.server.EndpointMessageContextImpl # [JBWS-2165] Fix xop tests with maven build FIXME [JBCTS-540] EJB3 proxy does not implement the Home interface FIXME [JBWS-1665] incorrect wsdl generation FIXME: [JBWS-1671] Metro client handler cannot set mime header FIXME: [JBWS-1672] Metro does not respect @HandlerChain on client SEI FIXME [JBWS-1772] WSConsume output is not correctly redirected FIXME [JBWS-1773] Verify isolated classloading with WSConsume FIXME [JBWS-1777] WSProvide output is not correctly redirected FIXME: [JBWS-2204] Implement Metro standard message context properties FIXME [JBWS-981] Virtual host configuration for EJB endpoints -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBWS-1119) Add support for fault signing and encryption

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1119?page=all ] Alessio Soldano updated JBWS-1119: ---------------------------------- Fix Version/s: (was: jbossws-native-3.0.3) > Add support for fault signing and encryption > -------------------------------------------- > > Key: JBWS-1119 > URL: http://jira.jboss.com/jira/browse/JBWS-1119 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-native-3.0.1 > Reporter: Jason T. Greene > Assigned To: Alessio Soldano > > Add the ability to sign faults. WS-Security faults, will of course be unsigned. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2189) Attribute EncodingType is required for Nonce element.

by Sławomir Wojtasiak (JIRA)

Attribute EncodingType is required for Nonce element. ----------------------------------------------------- Key: JBWS-2189 URL: http://jira.jboss.com/jira/browse/JBWS-2189 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-native-3.0.1 Reporter: Sławomir Wojtasiak If element Nonce of UsernameToken have no "EncodingType" attribute set then following exception is thrown: Unsupported nonce encoding type: Problem is localized here: String encodingType = elem.getAttribute("EncodingType"); if (encodingType != null && !Constants.BASE64_ENCODING_TYPE.equalsIgnoreCase(encodingType)) throw new WSSecurityException("Unsupported nonce encoding type: " + encodingType); getAttribute method always returns empty string if attribute doesn't have specified value. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2033) Fix the breadcrumbs tag

by Alessio Soldano (JIRA)

Fix the breadcrumbs tag ----------------------- Key: JBWS-2033 URL: http://jira.jboss.com/jira/browse/JBWS-2033 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano The wiki breadcrumbs tag is not working the right way, i.e. it only shows something like: JBossWS->Page -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2155) Not supporting JMS endpoints for WS-Addressing

by Zach Mabe (JIRA)

Not supporting JMS endpoints for WS-Addressing ---------------------------------------------- Key: JBWS-2155 URL: http://jira.jboss.com/jira/browse/JBWS-2155 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native, ws-addressing Affects Versions: jbossws-native-3.0.1 Environment: JBoss 4.2.2.GA, Windows XP, Sun JVM 1.5.0_08 Reporter: Zach Mabe when using a JMS endpoint at the EPR for either the faultTo or ReplyTo address within the WS-Addressing headers, the server always fails with the message ClassNotFound org.jboss.remoting.transport.jms.TransportClientFactory. How the faultTo is set on the client side AddressingProperties props = (AddressingProperties) reqContext.get(JAXWSAConstants.CLIENT_ADDRESSING_PROPERTIES); EndpointReference ep =ADDRESS_BUILDER.newEndpointReference(new URI("jms://queue/WSDropQueue")); props.setFaultTo(ep); This issue seems to be rooted in the fact that, on the server side, when the org.jboss.ws.core.soap.SOAPConnectionImpl is called to send the response/fault, it uses a org.jboss.ws.core.client.SOAPProtocolConnectionHTTP which in turns uses the JBoss-Remoting client which doesn't provide JMS support. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2190) Default encoding is used to decode responses.

by Sławomir Wojtasiak (JIRA)

Default encoding is used to decode responses. --------------------------------------------- Key: JBWS-2190 URL: http://jira.jboss.com/jira/browse/JBWS-2190 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.1 Environment: JBoss AS 4.2, JAXWS 3.0.1 Native. Reporter: Sławomir Wojtasiak During response processing (on client side) JaxWS Native uses default JVM character encoding to read data from inputStream but there is always UTF-8 used as a default encoding when response is sent to the client. Following code sets encoding while response is prepared and sent on the server side: boolean writeXML = isWriteXMLDeclaration(); String charsetEncoding = getCharSetEncoding(); SOAPElementWriter writer = new SOAPElementWriter(outs, charsetEncoding); // Implementation of getCharSetEncoding(). private String getCharSetEncoding() throws SOAPException { String charsetName = (String)getProperty(CHARACTER_SET_ENCODING); if (charsetName == null) charsetName = "UTF-8"; return charsetName; } On the client side there is no character encoding set when input stream is passed to the xml parser, so default encoding is used to decode it (which is ISO-8859-1 in my case and I can't change it only because JaxWS needs it). I'm sure that DEFAULT encoding should be the same during processing requests and responses. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBWS-2185) NPE in JBossXSEntityResolver while deploying wsconsume generated WS

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-2185?page=all ] Alessio Soldano updated JBWS-2185: ---------------------------------- Fix Version/s: jbossws-native-3.0.3 > NPE in JBossXSEntityResolver while deploying wsconsume generated WS > ------------------------------------------------------------------- > > Key: JBWS-2185 > URL: http://jira.jboss.com/jira/browse/JBWS-2185 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Environment: Recognized on Linux 2.6.24-16/x86 using Sun's JDK 1.5.0_07-b03 > Reproduced on Windows Vista/x86 using Sun's JDK 1.5.0_14-b03 > Reporter: Maximilian Schmidt > Fix For: jbossws-native-3.0.3 > > > Deploying a bottom-up webservice, which uses complex messages (compiled from eGIF/UBL2 schemas), results in a NPE as shown below: > java.lang.NullPointerException > at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSEntityResolver.getXMLInputSource(JBossXSEntityResolver.java:167) > at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSEntityResolver.resolveEntity(JBossXSEntityResolver.java:135) > at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) > at org.apache.xerces.impl.xs.XMLSchemaLoader.resolveDocument(Unknown Source) > at org.apache.xerces.impl.xs.traversers.XSDHandler.resolveSchema(Unknown Source) > at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown Source) > at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) > at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) > at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source) > at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:182) > at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:391) > at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:406) > at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:172) > at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128) > at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.processOrGenerateWSDL(JAXWSWebServiceMetaDataBuilder.java:373) > at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:158) > at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50) > at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63) > at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:66) > at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) > 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 $Proxy45.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.GeneratedMethodAccessor20.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 $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) > Generating a WSDL from classes using wsprovide and afterwards way back to code using wsconsume results in a web service that on deployment produces the very same error, although wsprovide/wsconsume work flawlessly. See the mentioned forum thread for more information or take a look at > http://page.mi.fu-berlin.de/schmidtm/jbossws-jaxb/ > where the mentioned WSDL along with an eclipse/ant project that generates a deployable WAR can be found and used to reproduce the problem. -- 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, 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 June 2008