January 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2468) javax.xml.ws.BindingProvider.getEndpointReference

by Alessio Soldano (JIRA)

javax.xml.ws.BindingProvider.getEndpointReference ------------------------------------------------- Key: JBWS-2468 URL: https://jira.jboss.org/jira/browse/JBWS-2468 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Conformance 4.5 (javax.xml.ws.BindingProvider.getEndpointReference): An implementation MUST be able to return an javax.xml.ws.EndpointReference for the target endpoint if a SOAP binding is being used. If the BindingProvider instance has a binding that is either SOAP 1.1/HTTP or SOAP 1.2/HTTP, then a W3CEndpointReference MUST be returned. If the binding is XML/HTTP an java- .lang.UnsupportedOperationExceptionMUST be thrown. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2480) Soap attachments are dropped on server response

by Richard Opalka (JIRA)

Soap attachments are dropped on server response ----------------------------------------------- Key: JBWS-2480 URL: https://jira.jboss.org/jira/browse/JBWS-2480 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Applies to **/jaxws/jbws1283/*TestCase -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2466) use of JAXB annotations

by Alessio Soldano (JIRA)

use of JAXB annotations ----------------------- Key: JBWS-2466 URL: https://jira.jboss.org/jira/browse/JBWS-2466 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Conformance 3.14 (use of JAXB annotations): An implementation MUST honor any JAXB annotation that exists on an SEI method or parameter to assure that the proper XML infoset is used when marshalling/ unmarshalling the the return value or parameters of the method. The set of JAXB annotations that MUST be supported are: javax.xml.bind.annotation.XmlAttachementRef,javax.xml.bind.annotation- .XmlList, javax.xml.bind.XmlMimeType and javax.xml.bind.annotation.adapters.Xml- JavaTypeAdapter -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2477) Support generics in wrapper classes

by Alessio Soldano (JIRA)

Support generics in wrapper classes ----------------------------------- Key: JBWS-2477 URL: https://jira.jboss.org/jira/browse/JBWS-2477 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native, tools-jaxws Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.6 When running wsprovide with -keep option (ie. generating and keeping the artifacts sources), we currently do not support generics in wrapper classes. So for a SEI like this: @WebService(targetNamespace = "http://foo.bar.com/calculator") public class CalculatorBean { @WebMethod public Set<Integer> getKeys(HashMap<Integer, String> map) { if (map != null) return map.keySet(); else return null; } } we get the following wrapper @XmlRootElement(name = "getKeys", namespace = "http://foo.bar.com/calculator") @XmlType(name = "getKeys", namespace = "http://foo.bar.com/calculator") @XmlAccessorType(XmlAccessType.FIELD) public class GetKeys { @XmlElement(name = "arg0", namespace = "") private HashMap arg0; public HashMap getArg0() { return this.arg0; } public void setArg0(HashMap arg0) { this.arg0 = arg0; } } instead of @XmlRootElement(name = "getKeys", namespace = "http://foo.bar.com/calculator") @XmlType(name = "getKeys", namespace = "http://foo.bar.com/calculator") @XmlAccessorType(XmlAccessType.FIELD) public class GetKeys { @XmlElement(name = "arg0", namespace = "") private HashMap<Integer, String> arg0; public HashMap<Integer, String> getArg0() { return this.arg0; } public void setArg0(HashMap<Integer, String> arg0) { this.arg0 = arg0; } } -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2416) Search is not working on the mediawiki

by Alessio Soldano (JIRA)

Search is not working on the mediawiki -------------------------------------- Key: JBWS-2416 URL: https://jira.jboss.org/jira/browse/JBWS-2416 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: 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

15 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2475) Problem with version mismatches

by Joseph Mango (JIRA)

Problem with version mismatches ------------------------------- Key: JBWS-2475 URL: https://jira.jboss.org/jira/browse/JBWS-2475 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tools-jaxws Environment: Window XP Professional 64Bit Reporter: Joseph Mango Priority: Optional I'm having a problem similar, I happen to be quite new to JAX-WS and am not sure of the correct configs. I created a WSDL and was attempting to create services from that WSDL. JRE 1.5.0_17-b04 JBOSS 4.2.3.GA C:\Documents and Settings\jmango\My Documents\NetBeansProjects\AstCycle\nbproject\jaxws-build.xml:24: You are loading JAX-WS 2.0 API from jar:file:/E:/jboss-4.2.3.GA/client/jboss-jaxws.jar!/javax/xml/ws/Service.class but this tool requires JAX-WS 2.1 API. BUILD FAILED (total time: 0 seconds) Thanks In Advance, Joe [ Show » ] Joseph Mango - 19/Jan/09 12:51 AM I'm having a problem similar, I happen to be quite new to JAX-WS and am not sure of the correct configs. I created a WSDL and was attempting to create services from that WSDL. JRE 1.5.0_17-b04 JBOSS 4.2.3.GA C:\Documents and Settings\jmango\My Documents\NetBeansProjects\AstCycle\nbproject\jaxws-build.xml:24: You are loading JAX-WS 2.0 API from jar:file:/E:/jboss-4.2.3.GA/client/jboss-jaxws.jar!/javax/xml/ws/Service.class but this tool requires JAX-WS 2.1 API. BUILD FAILED (total time: 0 seconds) Thanks In Advance, Joe [Always show]Add Comment Comment: Viewable By: All Users jira-users -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBWS-1931) Update to jaxb-2.1 required for certain endpoints

by Joseph Mango (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-1931?page=com.atlassian.jira.plug... ] Joseph Mango commented on JBWS-1931: ------------------------------------ I'm having a problem similar, I happen to be quite new to JAX-WS and am not sure of the correct configs. I created a WSDL and was attempting to create services from that WSDL. JRE 1.5.0_17-b04 JBOSS 4.2.3.GA C:\Documents and Settings\jmango\My Documents\NetBeansProjects\AstCycle\nbproject\jaxws-build.xml:24: You are loading JAX-WS 2.0 API from jar:file:/E:/jboss-4.2.3.GA/client/jboss-jaxws.jar!/javax/xml/ws/Service.class but this tool requires JAX-WS 2.1 API. BUILD FAILED (total time: 0 seconds) Thanks In Advance, Joe > Update to jaxb-2.1 required for certain endpoints > ------------------------------------------------- > > Key: JBWS-1931 > URL: https://jira.jboss.org/jira/browse/JBWS-1931 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Environment: JBOSS 4.2.2 GA, JDK1.6 > Reporter: cai jc > Assignee: Richard Opalka > > I created a web service endpoint using JWS: > /* > * BookWS.java > * > * > * To change this template, choose Tools | Template Manager > * and open the template in the editor. > */ > package net.cjc.ws; > import java.util.List; > import javax.ejb.*; > import javax.jws.*; > import javax.jws.soap.SOAPBinding; > import net.cjc.beans.AuthorManager; > import net.cjc.entity.Book; > @WebService(name="BookWS",targetNamespace="http://net.cjc.ws",serviceName="BookWSService") > @SOAPBinding(style= SOAPBinding.Style.RPC) > @Stateless > public class BookWS { > /* @EJB > private AuthorManager am; > @WebMethod > public List<Book> getMyBook(String me) > { > return am.queryBooks(me); > }*/ > @WebMethod > public String getMyBook(String me) > { > return "you have nothing!"; > } > } > And modified web.xml to configure this endpoint as a servlet. > At deploy time,the app server throws an exception: > 06:13:45,593 ERROR [MainDeployer] Could not start deployment: file:/D:/jboss-4.2.2.GA/server/default/tmp/deploy/tmp7551cjc.ear-contents/cjc-war.war > java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder > at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422) > at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286) > at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139) > at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105) > at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:116) > ... > But I still can see this web service from http://localhost:8080/jbossws/services.While I click it to retrieve WSDL,another exception is thrown: > 06:25:15,796 ERROR [RequestHandlerImpl] Error processing web service request > java.lang.IllegalStateException: Cannot obtain endpoint meta data > at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:520) > at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.java:144) > at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:126) > at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) > .... > Is this a bug? or my fault? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2455) Conformance Requirements JAX-WS 2.1

by Alessio Soldano (JIRA)

Conformance Requirements JAX-WS 2.1 ----------------------------------- Key: JBWS-2455 URL: https://jira.jboss.org/jira/browse/JBWS-2455 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano We should track here the conformance requirements added in JAX-WS 2.1, then provide a test for each of them. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2474) SOAP Addressing Support

by Alessio Soldano (JIRA)

SOAP Addressing Support ----------------------- Key: JBWS-2474 URL: https://jira.jboss.org/jira/browse/JBWS-2474 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Conformance 10.23 (SOAP Addressing Support): An implementation MUST supportWS-Addressing 1.0 SOAP Binding -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2473) Unsupported WebServiceFeatureAnnotation

by Alessio Soldano (JIRA)

Unsupported WebServiceFeatureAnnotation --------------------------------------- Key: JBWS-2473 URL: https://jira.jboss.org/jira/browse/JBWS-2473 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Conformance 7.3 (Unsupported WebServiceFeatureAnnotation): If an unrecongnized or unsupported annotation annotated with the WebServiceFeatureAnnotation meta-annotation: • In a client setting, an implementation MUST NOT invoke the remote operation being invoked, if any. Instead, it MUST throw a WebServiceException, setting its cause to an exception approximating the cause of the error (e.g. an IllegalArgumentException or a ClassNotFoundException). • In a server setting, annotation, an implementation MUST NOT dispatch to an endpoint implementation object. Rather, it MUST generate a fault appropriate to the binding in use. -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2009