January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1862) RPC DII Calls Assume child element of soap:body is called 'result' in the response message.

by Darran Lofthouse (JIRA)

RPC DII Calls Assume child element of soap:body is called 'result' in the response message. ------------------------------------------------------------------------------------------- Key: JBWS-1862 URL: http://jira.jboss.com/jira/browse/JBWS-1862 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-1.2.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.3 RPC DII Calls Assume child element of soap:body is called 'result' in the response message. For document style endpoints it will fall back to checking the type but for RPC calls if the name does not match the following error will be reported. java.rmi.RemoteException: Call invocation failed; nested exception is: org.jboss.ws.WSException: Cannot find child element: result at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:526) at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:276) ... Caused by: org.jboss.ws.WSException: Cannot find child element: result at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:866) at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:586) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:356) at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:507) ... 2 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

16 years, 1 month

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

16 years, 3 months

3
12
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

16 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1312) Fix JMS transport in trunk

by Jason T. Greene (JIRA)

Fix JMS transport in trunk -------------------------- Key: JBWS-1312 URL: http://jira.jboss.com/jira/browse/JBWS-1312 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason T. Greene Fix For: jbossws-2.0.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, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBWS-1773) Verify isolated classloading with WSConsume

by Heiko Braun (JIRA)

Verify isolated classloading with WSConsume ------------------------------------------- Key: JBWS-1773 URL: http://jira.jboss.com/jira/browse/JBWS-1773 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun -- 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, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-1813) context-root in jboss.xml is ignored

by Thomas Diesler (JIRA)

context-root in jboss.xml is ignored ------------------------------------ Key: JBWS-1813 URL: http://jira.jboss.com/jira/browse/JBWS-1813 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws Affects Versions: jbossws-2.0.1 Reporter: Thomas Diesler Fix For: jbossws-2.0.2 I want to override the default context root for my Web Services. So in my jboss.xml for (myEjb.jar) I have [QUOTE] <context-root>/webservices</context-root> [/QUOTE] inside the jboss->webservices node. But this doesn't seem to be working, the WSDLs are published at http://host/myApp-myEjb/ -- 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 months

6
20
0 / 0

[JBoss JIRA] Created: (JBWS-1673) Fix JAXR samples for SunRI

by Thomas Diesler (JIRA)

Fix JAXR samples for SunRI -------------------------- Key: JBWS-1673 URL: http://jira.jboss.com/jira/browse/JBWS-1673 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Fix For: jbossws-2.1.0 2007-06-01 06:12:43,257 ERROR [org.jboss.jaxr.juddi.transport.SaajTransport:94] Exception:: org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2409) at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName(AttrNSImpl.java:150) at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>(AttrNSImpl.java:111) at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:2012) at com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl.createAttributeNS(SOAPDocumentImpl.java:161) at com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS(ElementImpl.java:684) at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.setAttributeNS(ElementImpl.java:1241) at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttributeBare(ElementImpl.java:499) at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttributeBare(ElementImpl.java:471) at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttribute(ElementImpl.java:454) at org.jboss.jaxr.juddi.transport.SaajTransport.appendAttributes(SaajTransport.java:156) at org.jboss.jaxr.juddi.transport.SaajTransport.appendElements(SaajTransport.java:180) at org.jboss.jaxr.juddi.transport.SaajTransport.appendElements(SaajTransport.java:181) at org.jboss.jaxr.juddi.transport.SaajTransport.createSOAPMessage(SaajTransport.java:136) at org.jboss.jaxr.juddi.transport.SaajTransport.send(SaajTransport.java:77) at org.apache.juddi.proxy.RegistryProxy.execute(RegistryProxy.java:368) at org.apache.juddi.AbstractRegistry.saveBusiness(AbstractRegistry.java:582) at org.apache.ws.scout.registry.BusinessLifeCycleManagerImpl.executeOperation(BusinessLifeCycleManagerImpl.java:532) at org.apache.ws.scout.registry.BusinessLifeCycleManagerImpl.saveOrganizations(BusinessLifeCycleManagerImpl.java:389) at org.jboss.test.ws.jaxws.samples.jaxr.scout.query.JaxrBusinessQueryTestCase.setUp(JaxrBusinessQueryTestCase.java:58) -- 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

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-1684) Fix @WebServiceRef with XFire

by Thomas Diesler (JIRA)

Fix @WebServiceRef with XFire ----------------------------- Key: JBWS-1684 URL: http://jira.jboss.com/jira/browse/JBWS-1684 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.1.0 Caused by: org.jboss.kernel.spi.registry.KernelRegistryEntryNotFoundException: Entry not found with name: ServiceRefHandler at org.jboss.kernel.plugins.registry.AbstractKernelRegistry.getEntry(AbstractKernelRegistry.java:89) at org.jboss.metadata.serviceref.ServiceRefDelegate.<init>(ServiceRefDelegate.java:64) at org.jboss.injection.WebServiceRefHandler.getServiceRef(WebServiceRefHandler.java:146) at org.jboss.injection.WebServiceRefHandler.handleFieldAnnotations(WebServiceRefHandler.java:133) at org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUtil.java:137) at org.jboss.injection.InjectionUtil.processAnnotations(InjectionUtil.java:174) at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:366) at org.jboss.ejb3.SessionContainer.processMetadata(SessionContainer.java:116) -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-1857) Never create the same JAXBContext more than once

by Johann Gyger (JIRA)

Never create the same JAXBContext more than once ------------------------------------------------ Key: JBWS-1857 URL: http://jira.jboss.com/jira/browse/JBWS-1857 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-1.2.1 Reporter: Johann Gyger service.getPort() may become an expensive operation (i.e., several seconds) when using a non-trivial WSDL with complex types. We have been able to track down our performance problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66, creating new instances of JAXBContext is an expensive operation. In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created through the following call hierarchy: JAXBContext.newInstance(Class[], Map<String,?>) line: 570 JAXBContext.newInstance(Class...) line: 522 JAXBAccessor$1.create(Class) line: 67 JAXBAccessor$1.create(ParameterMetaData) line: 54 ParameterMetaData.eagerInitialize() line: 470 OperationMetaData.eagerInitialize(List<Method>) line: 469 ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516 ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502 ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490 JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>) line: 292 ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274 ServiceDelegateImpl.getPort(QName, Class<T>) line: 200 A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe report. Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad. -- 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, 6 months

4
15
0 / 0

[JBoss JIRA] Created: (JBWS-1869) Implement the stream based request handler API

by Heiko Braun (JIRA)

Implement the stream based request handler API ---------------------------------------------- Key: JBWS-1869 URL: http://jira.jboss.com/jira/browse/JBWS-1869 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: integration-metro Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.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, 6 months

3
10
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