June 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2521) Refactor / rewrite ServiceObjectFactory

by Alessio Soldano (JIRA)

Refactor / rewrite ServiceObjectFactory --------------------------------------- Key: JBWS-2521 URL: https://jira.jboss.org/jira/browse/JBWS-2521 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.1 The jbossws-cxf ServiceObjectFactory needs to be cleaned: - Bus retrieval: this is currently performed through reflection on the Service class and following cast to cxf ServiceImpl; leveraging the BusFactory should be enough to get the default bus that is used by the cxf ProviderImpl for every Service creation - ServiceRef stub properties setup: this is currently performed through reflection on Service class to get the ServiceDelegate and then chaning the ServiceDelegate instance at runtime with a custom onesetting the properties. Instead of doing this hack, we should evaluate leveraging the CXF configuration for runtime constructed objects (http://cwiki.apache.org/CXF20DOC/configuration-of-runtime-constructed-obj...). IOW cxf ServiceImpl looks for a bean named portName.toString() + ".jaxws-client.proxyFactory" to configure the JaxWsProxyFactoryBean used to build the port and that factory bean allows for setting the stub properties. We might be able to generate on the fly and supply a bean configuration to the cxf bus for having our stub properties automatically configured by the already existing cxf configuration system. - perhaps even the handler chain configuration can be achieved in a way similar to the described in the previous point. -- 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

16 years, 5 months

2
9
0 / 0

[JBoss JIRA] Created: (JBWS-2652) jboss-bootstrap upgrade

by Alessio Soldano (JIRA)

jboss-bootstrap upgrade ----------------------- Key: JBWS-2652 URL: https://jira.jboss.org/jira/browse/JBWS-2652 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-integration Affects Versions: jbossws-cxf-3.1.1, jbossws-metro-3.1.1, jbossws-native-3.1.1, jbossws-native-3.1.2 Reporter: Alessio Soldano Assignee: Alessio Soldano -- 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

16 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2346) Issue with SAAJ API: SOAPBody.getElementsByTagNameNS() appears non-recursive

by David Boeren (JIRA)

Issue with SAAJ API: SOAPBody.getElementsByTagNameNS() appears non-recursive ---------------------------------------------------------------------------- Key: JBWS-2346 URL: https://jira.jboss.org/jira/browse/JBWS-2346 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3 Reporter: David Boeren We are trying to migrate our application into JBOSS 4.3EAP, perviously my webservice application was using Sun's saaj api. During the migration, we have been decided to use JBoss SAAJ api and we are seeing some weird problem with an API in SOAPBody class. Here is the sample code: NodeList list = soapMessage.getSOAPBody().getElementsByTagNameNS("urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0", "AdhocQueryResponse"); System.out.println(list.getLength()); list = soapMessage.getSOAPBody().getElementsByTagNameNS("urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0", "ExtrinsicObject"); System.out.println(list.getLength()); The first call to getElementsByTagNameNS() was returning the element list, but the subsequent call was returning an empty nodelist. I am attaching a sample java project created to reproduce the problem. -- 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

16 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2669) jbossws-cxf-3.1.1endpoint management not works

by Alberto Monferrer (JIRA)

jbossws-cxf-3.1.1endpoint management not works ---------------------------------------------- Key: JBWS-2669 URL: https://jira.jboss.org/jira/browse/JBWS-2669 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.1.1 Environment: SLES 10 SP2 with SUN Java SDK 1.5.0_13, JBoss 4.2.3 and JBoss 5.1.0 and jbossws-cxf-3.1.1 Reporter: Alberto Monferrer When we consume an EJB 3 web service deployed at jbossws-cxf-3.1.1, its registered service endpoint metrics counters (RequestCount, ResponseCount... shown at http://127.0.0.1:8080/jbossws/services) not work: never increment values and always show cero. Same happens with a POJO JSR-181 web service endpoint. Its registered service endpoint metrics counters (RequestCount, ResponseCount... shown at http://127.0.0.1:8080/jbossws/services) not work: never increment values and always show cero. But the same web service deployed with jbossws-native, its registered service endpoint metrics counters work fine. -- 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

16 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2686) Parsing errors fail to terminate unmarshalling

by Darran Lofthouse (JIRA)

Parsing errors fail to terminate unmarshalling ---------------------------------------------- Key: JBWS-2686 URL: https://jira.jboss.org/jira/browse/JBWS-2686 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Alessio Soldano Fix For: jbossws-native-3.2.0 If a message received suffers an error converting a value the error is silently dropped and the field is left initialised with the default value. i.e. if an NumberFormatExceptions are thrown converting Strings to longs then the NumberFormatException is dropped and the field left to the default value. The Unmarshaller should by default terminate for the first error or fatal error, currently it only terminates for a fatal error: - http://java.sun.com/javaee/5/docs/api/javax/xml/bind/Unmarshaller.html#se... This is a JAXB issue as raised here: - https://jaxb.dev.java.net/issues/show_bug.cgi?id=655 A workaround could be to add a ValidationEventHandler with this behaviour to our JAXBDeserializer: - Unmarshaller unmarshaller = jaxbContext.createUnmarshaller(); unmarshaller.setAttachmentUnmarshaller( new AttachmentUnmarshallerImpl()); unmarshaller.setEventHandler(new ValidationEventHandler() { public boolean handleEvent(final ValidationEvent event) { int severity = event.getSeverity(); return (severity != ValidationEvent.FATAL_ERROR && severity != ValidationEvent.ERROR); } }); JAXBElement jbe = unmarshaller.unmarshal(xmlFragment, javaType); value = jbe.getValue(); -- 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

16 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2682) Incorrect Parsing of Badly Formed int

by Darran Lofthouse (JIRA)

Incorrect Parsing of Badly Formed int ------------------------------------- Key: JBWS-2682 URL: https://jira.jboss.org/jira/browse/JBWS-2682 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.0 If the int being parsed is 1-1 it is incorrectly parsed as -11. This is an underlying JAXB issue also raised here: - https://jaxb.dev.java.net/issues/show_bug.cgi?id=644 -- 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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2554) Remove dependency on Remoting 2

by David Lloyd (JIRA)

Remove dependency on Remoting 2 ------------------------------- Key: JBWS-2554 URL: https://jira.jboss.org/jira/browse/JBWS-2554 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Remoting 2.x is going away, possibly for the forthcoming JBossAS 5.1 release; Remoting 3 will not have an equivalent generic HTTP abstraction. Anything depending on Remoting 2 will break if it is not ported to some other situation. -- 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

16 years, 6 months

5
12
0 / 0

[JBoss JIRA] Created: (JBWS-2527) BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext

by Alessio Soldano (JIRA)

BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext ---------------------------------------------------------------------------------------------------------------- Key: JBWS-2527 URL: https://jira.jboss.org/jira/browse/JBWS-2527 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.0 02-11-2009 11:10:32: SVR-ERROR: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:121) at org.springframework.context.support.AbstractApplicationContext.containsBean(AbstractApplicationContext.java:765) at org.apache.cxf.configuration.spring.ConfigurerImpl.configureBean(ConfigurerImpl.java:118) at org.apache.cxf.jaxws.ServiceImpl.configureObject(ServiceImpl.java:513) at org.apache.cxf.jaxws.ServiceImpl.createPort(ServiceImpl.java:429) at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:292) at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:287) at org.jboss.wsf.stack.cxf.client.ServiceRefStubPropertyServiceDelegate.getPort(ServiceRefStubPropertyServiceDelegate.java:172) at javax.xml.ws.Service.getPort(Service.java:44) at com.sun.ts.tests.jaxws.api.javax_xml_ws.Endpoint.Client.getPortJavaEE(Client.java:111) at com.sun.ts.tests.jaxws.api.javax_xml_ws.Endpoint.Client.setup(Client.java:189) -- 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

16 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-2681) Concurrency issues where multiple threads create Port using Service Simultaneously

by Darran Lofthouse (JIRA)

Concurrency issues where multiple threads create Port using Service Simultaneously ---------------------------------------------------------------------------------- Key: JBWS-2681 URL: https://jira.jboss.org/jira/browse/JBWS-2681 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.0 Where multiple threads attempt to create a port or call an endpoint from a newly created Service one of a number of errors is reported. java.lang.NullPointerException at org.jboss.ws.extensions.xop.jaxws.ReflectiveAttachmentRefScanner.isJDKType(ReflectiveAttachmentRefScanner.java:262) at org.jboss.ws.extensions.xop.jaxws.ReflectiveAttachmentRefScanner.scanBean(ReflectiveAttachmentRefScanner.java:78) at org.jboss.ws.metadata.umdm.ParameterMetaData.initializeAttachmentParameter(ParameterMetaData.java:500) at org.jboss.ws.metadata.umdm.ParameterMetaData.eagerInitialize(ParameterMetaData.java:485) at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:465) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:526) at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:510) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:500) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193) at javax.xml.ws.Service.getPort(Service.java:116) java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) at java.util.AbstractList$Itr.next(AbstractList.java:420) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:524) at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:510) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:500) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193) at javax.xml.ws.Service.getPort(Service.java:116) java.lang.IllegalStateException: Cannot synchronize to any of these methods: at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:492) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:526) at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:510) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:500) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193) at javax.xml.ws.Service.getPort(Service.java:116) java.lang.IllegalStateException: Cannot synchronize to any of these methods: public abstract org.jboss.support.ws.phonebook.TelephoneNumber org.jboss.support.ws.phonebook.PhoneBook.lookup(org.jboss.support.ws.phonebook.Person) OperationMetaData: qname={http://www.jboss.org/support/phonebook}lookup javaName=lookup style=document/literal/WRAPPED oneWay=false soapAction= at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:492) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:526) at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:510) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:500) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193) at javax.xml.ws.Service.getPort(Service.java:116) javax.xml.ws.WebServiceException: java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbound at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:307) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:245) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) at $Proxy15.lookup(Unknown Source) at org.jboss.support.ws.phonebook.ThreadedCallingClient$Caller.run(ThreadedCallingClient.java:51) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbound at org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.processPivot(MessageContextJAXWS.java:110) at org.jboss.ws.core.jaxws.client.ClientImpl.processPivot(ClientImpl.java:266) at org.jboss.ws.core.CommonClient.processPivotInternal(CommonClient.java:467) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:395) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:233) javax.xml.ws.soap.SOAPFaultException: Request struct cannot be null at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:75) at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109) at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:233) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) at $Proxy15.lookup(Unknown Source) javax.xml.ws.soap.SOAPFaultException: java.lang.NullPointerException at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:75) at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109) at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:233) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) at $Proxy15.lookup(Unknown Source) -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2685) Remove dependency on Sun's proprietary APIs

by Alessio Soldano (JIRA)

Remove dependency on Sun's proprietary APIs ------------------------------------------- Key: JBWS-2685 URL: https://jira.jboss.org/jira/browse/JBWS-2685 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-3.2.1 We currently leverages Sun's proprietary api, for instance com.sun.image.codec.jpeg.* That should be avoided to allow run on different JVMs. -- 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

16 years, 6 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2009