January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1752) Investigate CXF samples httpbinding

by Thomas Diesler (JIRA)

Investigate CXF samples httpbinding ----------------------------------- Key: JBWS-1752 URL: http://jira.jboss.com/jira/browse/JBWS-1752 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-cxf Reporter: Thomas Diesler 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

17 years

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-1682) XFire does not generate proper service name

by Thomas Diesler (JIRA)

XFire does not generate proper service name ------------------------------------------- Key: JBWS-1682 URL: http://jira.jboss.com/jira/browse/JBWS-1682 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-xfire Environment: WSDL generation should first respect @WebService.serviceName then fall back to target bean class SimpleName() Note, the wsdl service qname is NOT @WebService.name Testcase: testInvokeAsyncHandler took 0.032 sec Caused an ERROR {http://org.jboss.ws/jaxws/asynchronous}TestEndpointService is not a valid service. Valid services are: {http://org.jboss.ws/jaxws/asynchronous}TestEndpoint javax.xml.ws.WebServiceException: {http://org.jboss.ws/jaxws/asynchronous}TestEndpointService is not a valid service. Valid services are: {http://org.jboss.ws/jaxws/asynchronous}TestEndpoint at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:192) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:159) at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:81) at javax.xml.ws.Service.<init>(Service.java:56) at javax.xml.ws.Service.create(Service.java:680) at org.jboss.test.ws.jaxws.samples.asynchronous.AsynchronousProxyTestCase.createProxy(AsynchronousProxyTestCase.java:108) at org.jboss.test.ws.jaxws.samples.asynchronous.AsynchronousProxyTestCase.testInvokeAsyncHandler(AsynchronousProxyTestCase.java:94) Reporter: Thomas Diesler 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

17 years

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-1746) Add support for configurable invoker in cxf.xml

by Thomas Diesler (JIRA)

Add support for configurable invoker in cxf.xml ----------------------------------------------- Key: JBWS-1746 URL: http://jira.jboss.com/jira/browse/JBWS-1746 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: integration-xfire Reporter: Thomas Diesler Fix For: jbossws-2.1.1 apache-cxf-2.0 ignores writer.write("<jaxws:properties>"); writer.write("<entry key='serviceFactory.invoker' value-ref='" + invoker + "'/>"); writer.write("</jaxws:properties>"); -- 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

17 years

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-1753) Investigate CXF samples logicalhandler

by Thomas Diesler (JIRA)

Investigate CXF samples logicalhandler -------------------------------------- Key: JBWS-1753 URL: http://jira.jboss.com/jira/browse/JBWS-1753 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-cxf Reporter: Thomas Diesler 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

17 years

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-1759) Investigate CXF samples webservice

by Thomas Diesler (JIRA)

Investigate CXF samples webservice ---------------------------------- Key: JBWS-1759 URL: http://jira.jboss.com/jira/browse/JBWS-1759 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-cxf Reporter: Thomas Diesler 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

17 years

1
7
0 / 0

[JBoss JIRA] Created: (JBWS-1686) Add support for @Provider

by Thomas Diesler (JIRA)

Add support for @Provider ------------------------- Key: JBWS-1686 URL: http://jira.jboss.com/jira/browse/JBWS-1686 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-xfire Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.1.0 XFire does not give access to the standard JAXWS WebServiceContext in its Invoker interface import org.codehaus.xfire.MessageContext; import org.codehaus.xfire.fault.XFireFault; /** * The invoker class allows you to control how your service class is invoked. * For instance, you could supply an alternate instance which used a Factory to * create your service instead of XFire instantiating it. * * @author <a href="mailto:dan@envoisolutions.com">Dan Diephouse</a> * @since Nov 16, 2004 */ public interface Invoker { Object invoke( Method m, Object[] params, MessageContext context ) throws XFireFault; } -- 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

17 years

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-1751) Investigate CXF samples handlerchain

by Thomas Diesler (JIRA)

Investigate CXF samples handlerchain ------------------------------------ Key: JBWS-1751 URL: http://jira.jboss.com/jira/browse/JBWS-1751 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-cxf Reporter: Thomas Diesler Fix For: jbossws-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

17 years

2
6
0 / 0

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

by Richard Opalka (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1931?page=comments#action_12395208 ] Richard Opalka commented on JBWS-1931: -------------------------------------- Can't reproduce the problem on JDK1.6.x on AS 4.2.2 GA. My webservice code: package org.jboss.test.ws.jaxws.jbws1931; import java.util.List; import javax.ejb.Stateless; import javax.jws.WebService; import javax.jws.WebMethod; import javax.jws.soap.SOAPBinding; @WebService(name="BookWS",targetNamespace="http://net.cjc.ws",serviceName="BookWSService") @SOAPBinding(style= SOAPBinding.Style.RPC) @Stateless public class BookWS { @WebMethod public String getMyBook(String me) { return "you have nothing!"; } } My web.xml file: <?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4"> <servlet> <servlet-name>JBWS1931Service</servlet-name> <servlet-class>org.jboss.test.ws.jaxws.jbws1931.BookWS</servlet-class> </servlet> <servlet-mapping> <servlet-name>JBWS1931Service</servlet-name> <url-pattern>/JBWS1931</url-pattern> </servlet-mapping> </web-app> My application.xml file: <?xml version="1.0" encoding="UTF-8"?> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4"> <module> <web> <web-uri>jaxws-jbws1931.war</web-uri> <context-root>jaxws-jbws1931</context-root> </web> </module> </application> My ear structure: jaxws-jbws1931.ear + META-INF/application.xml + jaxws-jbws1931.war + WEB-INF/classes/org/jboss/test/ws/jaxws/jbws1931/BookWS + WEB-INF/web.xml I followed the instructions for running on JDK 1.6 from here: http://jbws.dyndns.org/mediawiki/index.php?title=Installation > Update to jaxb-2.1 required for certain endpoints > ------------------------------------------------- > > Key: JBWS-1931 > URL: http://jira.jboss.com/jira/browse/JBWS-1931 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Environment: JBOSS 4.2.2 GA, JDK1.6 > Reporter: cai jc > Assigned To: Richard Opalka > Fix For: jbossws-2.0.3 > > > 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

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

by Richard Opalka (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1931?page=comments#action_12395123 ] Richard Opalka commented on JBWS-1931: -------------------------------------- I'll do this investigation ;-) > Update to jaxb-2.1 required for certain endpoints > ------------------------------------------------- > > Key: JBWS-1931 > URL: http://jira.jboss.com/jira/browse/JBWS-1931 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Environment: JBOSS 4.2.2 GA, JDK1.6 > Reporter: cai jc > Assigned To: Richard Opalka > Fix For: jbossws-2.0.3 > > > 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1819) wsrunclient script(s) differ and do not always function.

by Tom Uijldert (JIRA)

wsrunclient script(s) differ and do not always function. -------------------------------------------------------- Key: JBWS-1819 URL: http://jira.jboss.com/jira/browse/JBWS-1819 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Affects Versions: jbossws-2.0.1 Environment: Windows-XP including Cygwin. Reporter: Tom Uijldert Priority: Minor Scripts wsrunclient.sh and wsrunclient.bat contain some questionable code: 1. They both define a "-Djava.endorsed.dirs" that is only used by javac. The compiler is not called here, only the JVM. The JVM doesn't seem to use it... 2. The included classpaths in the batch- and shell-file differ wildly. This cannot be attributed to OS-differences. I keep wondering what jars are actually needed... 3. The 'eval ...' command in wsrunclient.sh mis-quotes the actual command and at least 1 jar is missing. Below a "diff -u" on the shell-script. Changes that were needed to get it running in my environment. Hope this helps, Tom. the diff: ---------- --- ../../jbossws-native-2.0.1.GA/bin/wsrunclient.sh 2007-08-17 18:58:06.000000000 +0200 +++ ../../jboss-4.2.1.GA/bin/wsrunclient.sh.new 2007-09-21 13:53:59.638125000 +0200 @@ -52,9 +52,6 @@ # Setup JBoss sepecific properties JAVA_OPTS="$JAVA_OPTS" -# Setup the java endorsed dirs -JBOSS_ENDORSED_DIRS="$JBOSS_HOME/lib/endorsed" - # Setup the client classpath WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/log4j.jar" WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jbossws-client.jar" @@ -66,6 +63,8 @@ # JBossAS-4.2 subset of jbossall-client.jar WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jboss-common-client.jar" +WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/lib/endorsed/xercesImpl.jar" + while [ $# -ge 1 ]; do case $1 in "-classpath") WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$2"; shift;; @@ -82,9 +81,7 @@ JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"` fi -# Execute the JVM eval "$JAVA" $JAVA_OPTS \ - -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \ -Dlog4j.configuration=wstools-log4j.xml \ - -classpath "$WSRUNCLIENT_CLASSPATH" \ + -classpath '$WSRUNCLIENT_CLASSPATH' \ "$args" -- 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

17 years

4
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2008