September 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1654) ServiceDElegate requires non portable method getPortClassMap

by Thomas Diesler (JIRA)

ServiceDElegate requires non portable method getPortClassMap ------------------------------------------------------------ Key: JBWS-1654 URL: http://jira.jboss.com/jira/browse/JBWS-1654 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-xfire Reporter: Thomas Diesler java.lang.IllegalStateException: Could not initialize Service. at org.codehaus.xfire.jaxws.ServiceDelegate.<init>(ServiceDelegate.java:77) at org.codehaus.xfire.jaxws.Provider.createServiceDelegate(Provider.java:32) at javax.xml.ws.Service.<init>(Service.java:57) at org.jboss.test.ws.jaxws.eardeployment.TestEndpointService.<init>(TestEndpointService.java:37) at org.jboss.test.ws.jaxws.eardeployment.EarTestCase.testJSEEndpoint(EarTestCase.java:64) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.lang.NoSuchMethodException: org.jboss.test.ws.jaxws.eardeployment.TestEndpointService.getPortClassMap() at java.lang.Class.getMethod(Class.java:1581) at org.codehaus.xfire.jaxws.ServiceDelegate.<init>(ServiceDelegate.java:60) -- 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

1
7
0 / 0

[JBoss JIRA] Created: (JBWS-1676) Redirect XFire logging to jboss log

by Thomas Diesler (JIRA)

Redirect XFire logging to jboss log ----------------------------------- Key: JBWS-1676 URL: http://jira.jboss.com/jira/browse/JBWS-1676 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Fix For: jbossws-2.1.0 This cuurently uses the jdk logging -- 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

2
5
0 / 0

[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

16 years, 3 months

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

16 years, 3 months

1
3
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

16 years, 3 months

2
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

16 years, 3 months

1
5
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

16 years, 3 months

1
7
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

16 years, 3 months

2
6
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

16 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (JBWS-1797) Setting .NET friendly Endpoint in web.xml

by Heiko Braun (JIRA)

Setting .NET friendly Endpoint in web.xml ----------------------------------------- Key: JBWS-1797 URL: http://jira.jboss.com/jira/browse/JBWS-1797 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.1 Reporter: Heiko Braun Fix For: jbossws-2.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, 3 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues September 2007