April 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2160) Upgrade CXF to 2.1

by Richard Opalka (JIRA)

Upgrade CXF to 2.1 ------------------ Key: JBWS-2160 URL: http://jira.jboss.com/jira/browse/JBWS-2160 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.0.1 Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-3.0.2 CXF 2.1 is already available and supports JAX-WS 2.1-1 -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2094) Upgrade to Apache CXF 2.0.5-incubator

by Richard Opalka (JIRA)

Upgrade to Apache CXF 2.0.5-incubator ------------------------------------- Key: JBWS-2094 URL: http://jira.jboss.com/jira/browse/JBWS-2094 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-1.0.1 Reporter: Richard Opalka Fix For: jbossws-cxf-1.0.2 The Apache Incubator CXF team is proud to announce the availability of the 2.0.5 release! http://incubator.apache.org/cxf/download.html -- 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
4
0 / 0

[JBoss JIRA] Created: (JBWS-2100) Unlock WS-Addressing in all stacks

by Thomas Diesler (JIRA)

Unlock WS-Addressing in all stacks ---------------------------------- Key: JBWS-2100 URL: http://jira.jboss.com/jira/browse/JBWS-2100 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-3.0.2 Please provide samples and documentation on WS-Policy for all stacks. Link this issue to stack specific issues. -- 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
11
0 / 0

[JBoss JIRA] Created: (JBWS-2156) Allow JBossWS users to prefix SOAP messages with processing instruction

by Richard Opalka (JIRA)

Allow JBossWS users to prefix SOAP messages with processing instruction ----------------------------------------------------------------------- Key: JBWS-2156 URL: http://jira.jboss.com/jira/browse/JBWS-2156 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-cxf-3.0.2 I know there was a JIRA freeze last Friday but this is really simple to implement and incorporate to next release ;) -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2154) org.jboss.ws.WSException: arg0 is not a valid property on class ...

by Silvano Maffeis (JIRA)

org.jboss.ws.WSException: arg0 is not a valid property on class ... -------------------------------------------------------------------- Key: JBWS-2154 URL: http://jira.jboss.com/jira/browse/JBWS-2154 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.1 Environment: JDK 1.6_05, Windows XP Reporter: Silvano Maffeis Priority: Minor I'm getting the following error in deploying a simple document/literal web service with jbossws-3.0.1-native-2.0.4.GA on jboss 4.2.2.GA. org.jboss.ws.WSException: arg0 is not a valid property on class ... Full stack trace: 09:22:41,781 ERROR [MainDeployer] Could not start deployment: file:/C:/dev/tools/j2ee/jboss-4.2.2.GA /server/viperats/deploy/mobank-server-core.war org.jboss.ws.WSException: arg0 is not a valid property on class com.vipera.ts.server.ws.jaxws.NewOpe ration at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccessor(JAXBContextImpl.java:926) at org.jboss.ws.metadata.accessor.JAXBAccessorFactory.create(JAXBAccessorFactory.java:51) at org.jboss.ws.metadata.umdm.EndpointMetaData.createAccessor(EndpointMetaData.java:713) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeAccessors(EndpointMetaData.java:694) at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:567) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:553) at org.jboss.ws.metadata.umdm.ServiceMetaData.eagerInitialize(ServiceMetaData.java:435) at org.jboss.ws.metadata.umdm.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:196) at org.jboss.wsf.stack.jbws.EagerInitializeDeploymentAspect.create(EagerInitializeDeploymentAspect. java:50) This happens when the WAR holding the web service is deployed. The WSDL (that's what you get when you create a document/literal WSDL using the Eclipse wizard): <?xml version="1.0" encoding="UTF-8" standalone="no"?> <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.example.org/MyTest/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="MyTest" targetNamespace="http://www.example.org/MyTest/"> <wsdl:types> <xsd:schema targetNamespace="http://www.example.org/MyTest/"> <xsd:element name="NewOperation"> <xsd:complexType> <xsd:sequence> <xsd:element name="in" type="xsd:string"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="NewOperationResponse"> <xsd:complexType> <xsd:sequence> <xsd:element name="out" type="xsd:string"/> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> </wsdl:types> <wsdl:message name="NewOperationRequest"> <wsdl:part element="tns:NewOperation" name="parameters"/> </wsdl:message> <wsdl:message name="NewOperationResponse"> <wsdl:part element="tns:NewOperationResponse" name="parameters"/> </wsdl:message> <wsdl:portType name="MyTest"> <wsdl:operation name="NewOperation"> <wsdl:input message="tns:NewOperationRequest"/> <wsdl:output message="tns:NewOperationResponse"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="MyTestSOAP" type="tns:MyTest"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="NewOperation"> <soap:operation soapAction="http://www.example.org/MyTest/NewOperation"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="MyTest"> <wsdl:port binding="tns:MyTestSOAP" name="MyTestSOAP"> <soap:address location="http://www.example.org/"/> </wsdl:port> </wsdl:service> </wsdl:definitions> The WebService implementation: @WebService(name = "MyTest", targetNamespace = "http://www.example.org/MyTest/") public class MyTestWebService implements MyTest { public String newOperation(String in) { return null; } } -- 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
2
0 / 0

[JBoss JIRA] Created: (JBWS-2108) Release artifacts to the maven repository

by Thomas Diesler (JIRA)

Release artifacts to the maven repository ----------------------------------------- Key: JBWS-2108 URL: http://jira.jboss.com/jira/browse/JBWS-2108 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-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

16 years, 6 months

2
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-2075) Make sure that every FIXME in the testsuite is still valid

by Richard Opalka (JIRA)

Make sure that every FIXME in the testsuite is still valid ---------------------------------------------------------- Key: JBWS-2075 URL: http://jira.jboss.com/jira/browse/JBWS-2075 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.4, jbossws-metro-1.0.1, jbossws-cxf-1.0.1 -- 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
13
0 / 0

[JBoss JIRA] Created: (JBWS-2033) Fix the breadcrumbs tag

by Alessio Soldano (JIRA)

Fix the breadcrumbs tag ----------------------- Key: JBWS-2033 URL: http://jira.jboss.com/jira/browse/JBWS-2033 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano The wiki breadcrumbs tag is not working the right way, i.e. it only shows something like: JBossWS->Page -- 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
7
0 / 0

[JBoss JIRA] Created: (JBWS-2155) Not supporting JMS endpoints for WS-Addressing

by Zach Mabe (JIRA)

Not supporting JMS endpoints for WS-Addressing ---------------------------------------------- Key: JBWS-2155 URL: http://jira.jboss.com/jira/browse/JBWS-2155 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native, ws-addressing Affects Versions: jbossws-native-3.0.1 Environment: JBoss 4.2.2.GA, Windows XP, Sun JVM 1.5.0_08 Reporter: Zach Mabe when using a JMS endpoint at the EPR for either the faultTo or ReplyTo address within the WS-Addressing headers, the server always fails with the message ClassNotFound org.jboss.remoting.transport.jms.TransportClientFactory. How the faultTo is set on the client side AddressingProperties props = (AddressingProperties) reqContext.get(JAXWSAConstants.CLIENT_ADDRESSING_PROPERTIES); EndpointReference ep =ADDRESS_BUILDER.newEndpointReference(new URI("jms://queue/WSDropQueue")); props.setFaultTo(ep); This issue seems to be rooted in the fact that, on the server side, when the org.jboss.ws.core.soap.SOAPConnectionImpl is called to send the response/fault, it uses a org.jboss.ws.core.client.SOAPProtocolConnectionHTTP which in turns uses the JBoss-Remoting client which doesn't provide JMS 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, 6 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2008