October 2007 - jbossws-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (JBWS-1316) Add support for a configurable time tolerance value that handles clock skew

by Jason T. Greene (JIRA)

Add support for a configurable time tolerance value that handles clock skew --------------------------------------------------------------------------- Key: JBWS-1316 URL: http://jira.jboss.com/jira/browse/JBWS-1316 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Reporter: Jason T. Greene Fix For: jbossws-1.0.5 -- 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, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBWS-1731) Investigate support for jaxws collections

by Thomas Diesler (JIRA)

Investigate support for jaxws collections ----------------------------------------- Key: JBWS-1731 URL: http://jira.jboss.com/jira/browse/JBWS-1731 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Fix For: jbossws-2.1.0 We need a test case that documents the extends of collection 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, 8 months

1
10
0 / 0

[JBoss JIRA] Created: (JBWS-1714) CLONE - Verify correct bahaviour of @WebService.wsdlLocation

by Heiko Braun (JIRA)

CLONE - Verify correct bahaviour of @WebService.wsdlLocation ------------------------------------------------------------ Key: JBWS-1714 URL: http://jira.jboss.com/jira/browse/JBWS-1714 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Heiko Braun Assigned To: Thomas Diesler Fix For: jbossws-2.0.0 I get a wsdl now but it is not the one I defined in my wsdlLocation value in the endpoint interface in the wsdlLocation javax.jws.WebService annotation. I get datetime types set to anySimpleType and all my enumerations have camel case now like this - dropOffType - rather than DropOffType like in the wsdl. I believe a wsdl is being generated still. How do I generate and deploy a web service and have jboss use the wsdl I supply in the war? -- 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, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (JBWS-1702) JAXWS type inheritance

by Thomas Diesler (JIRA)

JAXWS type inheritance ---------------------- Key: JBWS-1702 URL: http://jira.jboss.com/jira/browse/JBWS-1702 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-jbws Reporter: Thomas Diesler Fix For: jbossws-2.1.0 I have a problem with the new JBossWS-1.2.1.GA in JBoss 4.2.0.GA and inheritance. To describe this problem first I have to describe my code structure: For an example I have three classes (ClassA, ClassB and ClassC). ClassC inherits of ClassB and ClassB inherits of ClassA (ClassA --> ClassB --> ClassC). Now I have a webservice method that returns ClassB. In this method an instance of ClassC is being created and returned. This was not a problem in the former JBossWS version (and also in the other J2EE 4 styled webservices) but now in JBossWS 1.2 I only get returned an object of ClassB but I supposed to get an obejct of ClassC. Code: public class ClassA { private String propA; // here setter and getter for propA ...... } public class ClassB extends ClassA { private String propB; // here setter and getter for propB ...... } public class ClassC extends ClassC { private String propC; // here setter and getter for propC ...... } @WebService @SOAPBinding( style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SO APBinding.ParameterStyle.WRAPPED ) public class MyWebService { @WebMethod() public ClassB getClassB() { ClassC classC = new ClassC(); classC.setPropA("propA"); return classC; } /** * --> this method is only used to publish ClassC otherwise it is not known * in this webservice */ @WebMethod() public ClassC getClassC() { ClassC classC = new ClassC(); classC.setPropA("propA"); return classC; } } } Now I call getClassB() and the result that I got is an object of ClassB and not of ClassC. What can I do to get an object of ClassC. I also looked at the returned SOAP message and there you can see that only informations about the ClassB instance are submitted. In JBoss 4.0.5 (JBossWS1.0.3) the SOAP message contains the type of the returned object and all data are being submitted correctly. I also tried the SOAP parameter style BARE but nothing changed. And whenI use RPC/Literal then I get an error in the .NET Client that an instance of ClassB was expected but got an instance of ClassC. I also tried it with a JAVA client but there was the same occurance. -- 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, 8 months

5
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2007