[JBoss JIRA] Created: (JBWS-1685) Add support for WebServiceContext propagation
by Thomas Diesler (JIRA)
Add support for WebServiceContext propagation
---------------------------------------------
Key: JBWS-1685
URL: http://jira.jboss.com/jira/browse/JBWS-1685
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
tests-run-internal:
[junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
[junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 7.163 sec
[junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
[junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.312 sec
BUILD SUCCESSFUL
Total time: 15 seconds
[tdiesler@tddell sunri]$ cat output-tests/reports/TEST-org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase.txt
Testsuite: org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 7.163 sec
Testcase: testGetWebContext took 1.919 sec
FAILED
expected:<pass> but was:<fail>
junit.framework.ComparisonFailure: expected:<pass> but was:<fail>
at org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase.testGetWebContext(WebServiceContextEJBTestCase.java:71)
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)
--
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
[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
[JBoss JIRA] Created: (JBWS-1689) Add support for SwaRef
by Thomas Diesler (JIRA)
Add support for SwaRef
----------------------
Key: JBWS-1689
URL: http://jira.jboss.com/jira/browse/JBWS-1689
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
Fix various issues with @WebParam. For example the default xmlName when @WebParam is not specified
There also seems to be some JAXB context issues.
[tdiesler@tdvaio xfire]$ cat output-tests/reports/TEST-org.jboss.test.ws.jaxws.samples.webparam.WebParamTestCase.txt
Testsuite: org.jboss.test.ws.jaxws.samples.webparam.WebParamTestCase
Tests run: 4, Failures: 0, Errors: 4, Time elapsed: 2.995 sec
Testcase: testEcho took 1.993 sec
Caused an ERROR
Parameter arg0 does not exist!
javax.xml.ws.soap.SOAPFaultException: Parameter arg0 does not exist!
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:171)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:240)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
at $Proxy25.echo(Unknown Source)
at org.jboss.test.ws.jaxws.samples.webparam.WebParamTestCase.testEcho(WebParamTestCase.java:69)
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)
Testcase: testPingOneWay took 0.049 sec
Caused an ERROR
Could not unmarshall type : "org.jboss.test.ws.jaxws.samples.webparam" doesnt contain ObjectFactory.class or jaxb.index
javax.xml.ws.soap.SOAPFaultException: Could not unmarshall type : "org.jboss.test.ws.jaxws.samples.webparam" doesnt contain ObjectFactory.class or jaxb.index
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:171)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:240)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
at $Proxy25.pingOneWay(Unknown Source)
at org.jboss.test.ws.jaxws.samples.webparam.WebParamTestCase.testPingOneWay(WebParamTestCase.java:77)
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)
Testcase: testPingTwoWay took 0.049 sec
Caused an ERROR
Could not unmarshall type : "org.jboss.test.ws.jaxws.samples.webparam" doesnt contain ObjectFactory.class or jaxb.index
javax.xml.ws.soap.SOAPFaultException: Could not unmarshall type : "org.jboss.test.ws.jaxws.samples.webparam" doesnt contain ObjectFactory.class or jaxb.index
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:171)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:240)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
at $Proxy25.pingTwoWay(Unknown Source)
at org.jboss.test.ws.jaxws.samples.webparam.WebParamTestCase.testPingTwoWay(WebParamTestCase.java:86)
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)
Testcase: testSecurePing took 0.065 sec
Caused an ERROR
Could not unmarshall type : "org.jboss.test.ws.jaxws.samples.webparam" doesnt contain ObjectFactory.class or jaxb.index
javax.xml.ws.soap.SOAPFaultException: Could not unmarshall type : "org.jboss.test.ws.jaxws.samples.webparam" doesnt contain ObjectFactory.class or jaxb.index
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:171)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:240)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
at $Proxy25.securePing(Unknown Source)
at org.jboss.test.ws.jaxws.samples.webparam.WebParamTestCase.testSecurePing(WebParamTestCase.java:97)
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)
--
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
[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
[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
[JBoss JIRA] Created: (JBWS-1505) Methods defined in an interface superclass don't appear in WSDL.
by Iaacov Rosenberg (JIRA)
Methods defined in an interface superclass don't appear in WSDL.
----------------------------------------------------------------
Key: JBWS-1505
URL: http://jira.jboss.com/jira/browse/JBWS-1505
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4
Environment: JBoss 4.0.5 GA, JRE 1.5.0_10, WinXP
Reporter: Iaacov Rosenberg
Given the following scenario:
public interface Intf1 {
public int getMember1();
public void setMember1(int member1);
}
public interface Intf2 extends Intf1 {
public int getMember2();
public void setMember2(int member2);
}
Whenever JBossWS uses reflection, either when generating the WSDL file or when returning values that implement Intf2, only members defined in Intf2 (i.e. Member2) are processed, while ignoring inherited members.
This only happens with interfaces. Inherited classes are processed correctly.
--
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, 4 months
[JBoss JIRA] Created: (JBWS-1324) JMS Endpoint - Message delivery starts before endpoint is ready.
by Darran Lofthouse (JIRA)
JMS Endpoint - Message delivery starts before endpoint is ready.
----------------------------------------------------------------
Key: JBWS-1324
URL: http://jira.jboss.com/jira/browse/JBWS-1324
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxrpc
Affects Versions: jbossws-1.0.3
Reporter: Darran Lofthouse
Fix For: jbossws-1.0.6
For most endpoints we need the EJB to be initialised before we initialise the web service, this way we know the session bean will be ready to process requests before the first request from a client is received.
For message driven beans we need the web service to be initialised before the first message is processed by the MDB, however the same logic is used as is used for session beans so it is possible that the first message will be received while the web service is still being initialised.
--
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, 4 months
[JBoss JIRA] Created: (JBWS-1630) wstools error when using xsd:extension in schema
by Balaji Hari (JIRA)
wstools error when using xsd:extension in schema
------------------------------------------------
Key: JBWS-1630
URL: http://jira.jboss.com/jira/browse/JBWS-1630
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: wstools
Affects Versions: jbossws-1.2.1
Reporter: Balaji Hari
We have the following type extension defined in schema. When runnning wstools against WSDL its looking for wrong QName and throws NullpointerException.
<xsd:simpleType name="NetExplosiveWeightType">
<xsd:restriction base="xsd:decimal">
<xsd:whiteSpace value="collapse" />
<xsd:totalDigits value="9" />
<xsd:fractionDigits value="2" />
</xsd:restriction>
</xsd:simpleType>
<xsd:element name="NetExplosiveWeight">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="tns:NetExplosiveWeightType">
<xsd:attribute name="uom" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="collapse" />
<xsd:minLength value="1" />
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
Exception in thread "main" java.lang.NullPointerException
at org.jboss.ws.tools.XSDTypeToJava.getVARList(XSDTypeToJava.java:204)
at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:149)
at org.jboss.ws.tools.XSDTypeToJava.createVARforXSElementDeclaration(XSDTypeToJava.java:599)
at org.jboss.ws.tools.XSDTypeToJava.createVARsForElements(XSDTypeToJava.java:522)
at org.jboss.ws.tools.XSDTypeToJava.createVARsforXSParticle(XSDTypeToJava.java:449)
at org.jboss.ws.tools.XSDTypeToJava.getVARList(XSDTypeToJava.java:248)
at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:149)
at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:113)
at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:759)
at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:752)
at org.jboss.ws.tools.WSDLToJava.generateParameter(WSDLToJava.java:577)
at org.jboss.ws.tools.WSDLToJava.appendParameters(WSDLToJava.java:431)
at org.jboss.ws.tools.WSDLToJava.appendDocParameters(WSDLToJava.java:387)
at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:291)
at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:589)
at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:619)
at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:187)
at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:304)
at org.jboss.ws.tools.WSTools.process(WSTools.java:137)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:69)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
at org.jboss.ws.tools.WSTools.main(WSTools.java:58)
--
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, 4 months