September 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2315) URL.openStream fails in Vista with Connect exception due to IPv6

by Alessio Soldano (JIRA)

URL.openStream fails in Vista with Connect exception due to IPv6 ---------------------------------------------------------------- Key: JBWS-2315 URL: https://jira.jboss.org/jira/browse/JBWS-2315 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-3.0.5 Magesh says: "should we set jvm arg in ant build file by default?" <jvmarg value="-Djava.net.preferIPv4Stack=true"/> -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-2244) EntityResolver is not used when schema imports are handled.

by Franz Willer (JIRA)

EntityResolver is not used when schema imports are handled. ----------------------------------------------------------- Key: JBWS-2244 URL: http://jira.jboss.com/jira/browse/JBWS-2244 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.2 Environment: System (*nix, windows,..) without internet access. Reporter: Franz Willer Priority: Minor Web service deployment fails when a schema file use an import ( e.g. http://www.w3.org/2001/xml.xsd). The reason therefore is that WSDL11Reader.handleSchemaImports does not use EntityResolver. -- 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, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-2207) Allow to fully initialize the WS stack

by Vladimir Ralev (JIRA)

Allow to fully initialize the WS stack -------------------------------------- Key: JBWS-2207 URL: http://jira.jboss.com/jira/browse/JBWS-2207 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Vladimir Ralev The first webmethod call either inbound or outbound is always very slow (for each method). Subsequent calls are fine. My guess is that some lazy initialization occurs at this time. We have an application that requires the first calls to be as fast as the subsequent calls. We need some API or a propery of the stack to allow to fully pre-initialize the stack. -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2011) Signature is invalid error when the message contains \r

by Richard Opalka (JIRA)

Signature is invalid error when the message contains \r ------------------------------------------------------- Key: JBWS-2011 URL: http://jira.jboss.com/jira/browse/JBWS-2011 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Reporter: Richard Opalka Assigned To: Alessio Soldano Fix For: jbossws-native-2.0.4 Description of the problem is on the forum -- 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, 6 months

2
12
0 / 0

[JBoss JIRA] Created: (JBWS-2129) Wrapper class is not found

by Thomas Diesler (JIRA)

Wrapper class is not found -------------------------- Key: JBWS-2129 URL: http://jira.jboss.com/jira/browse/JBWS-2129 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-1.0.1 Reporter: Thomas Diesler [tdiesler@tdvaio trunk]$ ant -Dtest=jaxws/handlerscope test Caused by: com.sun.xml.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class org.jboss.test.ws.jaxws.handlerscope.jaxws.Echo is not found. Have you run APT to generate them? at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:287) at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:596) at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:543) at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:371) at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:258) at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322) at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188) at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467) at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parseAdapters(DeploymentDescriptorParserExt.java:291) -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2287) Run TCK5 and detect issues

by Alessio Soldano (JIRA)

Run TCK5 and detect issues -------------------------- Key: JBWS-2287 URL: https://jira.jboss.org/jira/browse/JBWS-2287 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.4 This task should track the failures on the TCK5 testsuite using Metro. Please add a subtask for each issue specifying the failing test(s). -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2246) NPE deploying web services in service archive in CR1 release

by Andrew Dinn (JIRA)

NPE deploying web services in service archive in CR1 release ------------------------------------------------------------ Key: JBWS-2246 URL: http://jira.jboss.com/jira/browse/JBWS-2246 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.2 Environment: Vanilla JBossAS5.0.0.CR1 release on Fedora 9/Sun JDK 1.5.0_12-b0 Reporter: Andrew Dinn I am trying to deploy a sar in AS5.0.0.CR1 which includes several war files. These wars include JaxWS SEI classes anotated with WebService annotations. The AS is using the bundled version of JBossWS Native. The war file deployment breaks if the sar is deployed before starting JBoss AS. This is because the WS KernelLocator bean has not been intiialized. This is supposed to happen via bean injection according to the bean definition in jbossws-container-beans.xml located in server//deploy. However, the war file is processed (by an instance of JaxWSDeployerHookPreJSE) before the value is injected. The deployer tries to look up the wsf runtime via the kernel and receives a null pointer exception (stack trace as follows): . . . Caused by: java.lang.NullPointerException at org.jboss.wsf.common.KernelAwareSPIFactory.getKernelProvidedSPI(KernelAwareSPIFactory.java:40) at org.jboss.wsf.framework.DefaultWSFRuntimeLocator.locateRuntime(DefaultWSFRuntimeLocator.java:36) at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHook.getWsfRuntime(AbstractDeployerHook.java:59) at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:86) at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174) ... 18 more -- 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, 6 months

4
11
0 / 0

[JBoss JIRA] Created: (JBWS-2325) Each request results to an open file descriptor

by Richard Opalka (JIRA)

Each request results to an open file descriptor ----------------------------------------------- Key: JBWS-2325 URL: https://jira.jboss.org/jira/browse/JBWS-2325 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3, jbossws-native-3.0.2, jbossws-native-3.0.1 Environment: All platforms Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.4 For this reason application reaches maximum file descriptors allowed and fails every request. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2205) XML Declaration contains endocing in AS 5 but not in AS4

by Heiko Braun (JIRA)

XML Declaration contains endocing in AS 5 but not in AS4 -------------------------------------------------------- Key: JBWS-2205 URL: http://jira.jboss.com/jira/browse/JBWS-2205 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Heiko Braun Assigned To: Heiko Braun 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

15 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2278) JBossWS is picking the wrong binding when both Soap1.1 and Soap1.2 bindings are provided for a port

by Andrew Dinn (JIRA)

JBossWS is picking the wrong binding when both Soap1.1 and Soap1.2 bindings are provided for a port --------------------------------------------------------------------------------------------------- Key: JBWS-2278 URL: https://jira.jboss.org/jira/browse/JBWS-2278 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.2 Environment: AS 5.0.0.CR1 Reporter: Andrew Dinn I am implementing an interop test using WSDL organized as follows: <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions targetNamespace="http://www.wstf.org/docs/scenarios/sc002" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://www.wstf.org/docs/scenarios/sc002"> <wsdl:types> . . . </wsdl:types> <wsdl:message name="Begin"> <wsdl:part name="Begin" element="tns:Begin"/> . . . </wsdl:message> <wsdl:portType name="sc002Port"> <wsdl:operation name="Begin"> . . . </wsdl:portType> <wsdl:binding name="sc002SOAP11Binding" type="tns:sc002Port"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="Begin"> . . . </wsdl:binding> <wsdl:binding name="sc002SOAP12Binding" type="tns:sc002Port"> <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="Begin"> . . . </wsdl:binding> <wsdl:service name="sc002Service"> <wsdl:port name="soap11port" binding="tns:sc002SOAP11Binding"> <soap:address location="http://www.wstf.org/sc002/sc002SOAP11"/> </wsdl:port> <wsdl:port name="soap12port" binding="tns:sc002SOAP12Binding"> <soap12:address location="http://www.wstf.org/sc002/sc002SOAP12"/> </wsdl:port> </wsdl:service> </wsdl:definitions> In other words, there is one port, two bindings and one service exporting the two bindings. I create a client proxy for the port named "soap11port" by invoking new Sc002Service().getPort(new QName("http://www.wstf.org/docs/scenarios/sc002", "soap11port"), Sc002Port.class) The returned port uses a SOAP12 binding even though the WSDL labels it clearly as a 1.1 port. The problem arises because of an error in the construction of the ClientEndPointMetaData used as the endpointMetaData attached to the ClientProxy. This is constructed inside the ServiceDelegateImpl constructor by invoking JAXWSClientMetaDataBuilder.buildMetaData(). The error occurs in inherited method MetaDataBuilder.initEndpointBinding() when it tries to identify the binding associated with QName sc002:soap11port. The following 4 lines are where it goes wrong: WSDLDefinitions wsdlDefinitions = wsdlEndpoint.getWsdlService().getWsdlDefinitions(); WSDLInterface wsdlInterface = wsdlEndpoint.getInterface(); WSDLBinding wsdlBinding = wsdlDefinitions.getBindingByInterfaceName(wsdlInterface.getName()); String bindingType = wsdlBinding.getType(); The first two lines locate the port sc002 associated with the binding identified by sc002:soap11port. The 3rd line then reverse searches from the port to find a binding which binds it. Of course there are two of these and, mirabile dictu, the code even prints a warning about this. It then ignores the correct and returns the soap12 binding. Ironically before reaching this point the JAXWSClientMetaDataBuilder does this search correctly in method buildMetaDataInternal at lines 154/5 it executes this code WSDLBinding wsdlBinding = wsdlEndpoint.getWsdlService().getWsdlDefinitions().getBinding(bindingName); String bindingType = wsdlBinding.getType(); I assume the convoluted code in the inherited method is there for a reason but, then again, that's what overriding was invented for. -- 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, 7 months

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 September 2008