August 2008 - jbossws-issues - Jboss List Archives

[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, 7 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, 7 months

4
11
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

[JBoss JIRA] Created: (JBWS-2240) PortComponent from jboss.xml descriptor is not parsed

by Alessio Soldano (JIRA)

PortComponent from jboss.xml descriptor is not parsed ----------------------------------------------------- Key: JBWS-2240 URL: http://jira.jboss.com/jira/browse/JBWS-2240 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Alessio Soldano Assigned To: Heiko Braun Priority: Blocker I see this in EJBArchiveMetaDataAdapterEJB3.buildEnterpriseBeansMetaData(...) : ... while (it.hasNext()) { WebServiceDeclaration container = it.next(); // TODO: Add PortComponent parsing to EJBDescriptorHandler PortComponentSpec pcMetaData = container.getAnnotation(PortComponentSpec.class); MessageDriven mdbMetaData = container.getAnnotation(MessageDriven.class); EJBMetaData ejbMetaData = null; ... It seems to me the portComponent specified in jboss.xml (and available in the JBossEnterpriseBeanMetaData instance) is not read; this may result in the wrong endpoint address being set, which is the cause of this tck5 failure: http://hudson.qa.jboss.com/hudson/view/TCK5/job/tck5-webservices12/204/te... -- 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
7
0 / 0

[JBoss JIRA] Created: (JBWS-2241) POrtComponentSpec is missing the UrlPattern property

by Heiko Braun (JIRA)

POrtComponentSpec is missing the UrlPattern property ---------------------------------------------------- Key: JBWS-2241 URL: http://jira.jboss.com/jira/browse/JBWS-2241 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.2 Reporter: Heiko Braun Fix For: jbossws-native-3.0.3 This needs to be parsed in org.jboss.ejb3.Ejb3DescriptorHandler -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1772) WSConsume output is not correctly redirected

by Heiko Braun (JIRA)

WSConsume output is not correctly redirected -------------------------------------------- Key: JBWS-1772 URL: http://jira.jboss.com/jira/browse/JBWS-1772 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxws Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun Currently the CodeWriter redirects output to System.out It's hardcoded in the SunRi tools codebase. I've created an issue for this: https://jax-ws.dev.java.net/issues/show_bug.cgi?id=387 It's no big deal, but should be fixed to simplify tools intergation with other products, IDE's, etc -- 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
12
0 / 0

[JBoss JIRA] Created: (JBWS-2282) Release spi, common and framework

by Alessio Soldano (JIRA)

Release spi, common and framework --------------------------------- Key: JBWS-2282 URL: https://jira.jboss.org/jira/browse/JBWS-2282 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4 -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2264) NPE when web services are shut down

by Andrew Dinn (JIRA)

NPE when web services are shut down ----------------------------------- Key: JBWS-2264 URL: https://jira.jboss.org/jira/browse/JBWS-2264 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.2 Reporter: Andrew Dinn See WS Native forum posting: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=139609 -- 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

[JBoss JIRA] Created: (JBWS-1397) Fix <wsdl-publish-location> for jboss-5.0.x

by Thomas Diesler (JIRA)

Fix <wsdl-publish-location> for jboss-5.0.x ------------------------------------------- Key: JBWS-1397 URL: http://jira.jboss.com/jira/browse/JBWS-1397 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.0 [tdiesler@localhost test]$ ant -Dtest=org.jboss.test.ws.jaxrpc.samples.jsr109pojo.RpcJSETestCase one-test one-test: [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109pojo.RpcJSETestCase [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 0.971 sec [junit] Test org.jboss.test.ws.jaxrpc.samples.jsr109pojo.RpcJSETestCase FAILED -- 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
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2008