November 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1858) Generate WSDL after all relevant metadata is available

by Thomas Diesler (JIRA)

Generate WSDL after all relevant metadata is available ------------------------------------------------------ Key: JBWS-1858 URL: http://jira.jboss.com/jira/browse/JBWS-1858 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.3 This is related to [JBWS-1797] -- 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, 11 months

2
2
0 / 0

[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, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (JBWS-1904) There should be a way to explicitly set the namespace of a WebFault in the generated WSDL schema

by Vesselin Kirov (JIRA)

There should be a way to explicitly set the namespace of a WebFault in the generated WSDL schema ------------------------------------------------------------------------------------------------ Key: JBWS-1904 URL: http://jira.jboss.com/jira/browse/JBWS-1904 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.1.SP2 Reporter: Vesselin Kirov At the moment the code in org.jboss.metadata.builder.jaxws.JAXWSMetaDataBuilder.addFault does not use the namespace information from @WebFault (if present) for the xml type in the WSDL schema that is generated. It is easy to change the code to do this, however I'm not sure if this would break some other use cases. The other approach would be to use the XmlType annotation (not used at all at the moment). -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-1739) Provide API complete implementation forn jboss-5.0.0.Beta3

by Thomas Diesler (JIRA)

Provide API complete implementation forn jboss-5.0.0.Beta3 ---------------------------------------------------------- Key: JBWS-1739 URL: http://jira.jboss.com/jira/browse/JBWS-1739 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-2.1.0 The SPI needs to be stabilized and freed from implementation detail. The container integration should live with the container. -- 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, 11 months

2
4
0 / 0

[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, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (JBWS-1845) Use of @ResponceWrapper annotation cause generation of incorrect wsdl upon deployment

by Gary Greenberg (JIRA)

Use of @ResponceWrapper annotation cause generation of incorrect wsdl upon deployment ------------------------------------------------------------------------------------- Key: JBWS-1845 URL: http://jira.jboss.com/jira/browse/JBWS-1845 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.1 Environment: Win XP Pro SP2, JBoss 4.2.1, JBossWS 2.0.1 Reporter: Gary Greenberg I used @ResponseWrapper annotation for my web method and generated on deploymeny wsdl did not correspond to the specified class. That caused SOAPFaultException on the return from the call. Details of the the issue explained on the forum. -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-1824) Content-type header is not set in SOAP response

by Lukas Jungmann (JIRA)

Content-type header is not set in SOAP response ----------------------------------------------- Key: JBWS-1824 URL: http://jira.jboss.com/jira/browse/JBWS-1824 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-1.2.1 Reporter: Lukas Jungmann -have a JAX-WS web service in a web module deployed on JBoss 4.2.1 (use JBossWS for this service) -create a JAX-WS client for this service in java application (and use JAX-WS RI 2.1.2 from jax-ws.dev.java.net/or tools from JDK6update3) -run the client expected: the JBossWS web service is successfully called from JAX-WS RI client actual: the call of the operation fails because of missing Content-Type header in the SOAP response TCP dump from Wireshark tool: GET /JBossWS-test/JBossWS?wsdl HTTP/1.1 User-Agent: Java/1.6.0_03-ea Host: 127.0.0.1:8080 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive HTTP/1.1 200 OK Server: Apache-Coyote/1.1 X-Powered-By: Servlet 2.4; JBoss-4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)/Tomcat-5.5 Content-Type: text/xml Transfer-Encoding: chunked Date: Wed, 12 Sep 2007 13:39:11 GMT f7 <definitions name='JBossWSService' targetNamespace='http://ws.test.jboss/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://ws.test.jboss/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> ... </definitions> 0 POST /JBossWS-test/JBossWS HTTP/1.1 SOAPAction: "" Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Content-Type: text/xml; charset=utf-8 User-Agent: Java/1.6.0_03-ea Host: 127.0.0.1:8080 Connection: keep-alive Content-Length: 189 HTTP/1.1 200 OK Server: Apache-Coyote/1.1 X-Powered-By: Servlet 2.4; JBoss-4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)/Tomcat-5.5 Transfer-Encoding: chunked Date: Wed, 12 Sep 2007 13:39:11 GMT 0 <?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:sayHi xmlns:ns2="http://ws.test.jboss/"><name>tom</name></ns2:sayHi></S:Body></S:Envelope -- 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, 12 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-1913) WS-Security doesn't work any more

by Juergen Zimmermann (JIRA)

WS-Security doesn't work any more --------------------------------- Key: JBWS-1913 URL: http://jira.jboss.com/jira/browse/JBWS-1913 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-2.0.2 Environment: JBossAS 4.2.2, JBossWS 2.0.2; JDK 1.6.0_03 Reporter: Juergen Zimmermann My application works fine with JBossAS 4.2.2 and the included JBossWS 2.0.1. However, after upgrading to JBossWS 2.0.2 I get this stacktrace: 2007-11-27 15:43:10,209 ERROR org.jboss.ws.extensions.security.WSSecurityDispatcher - Internal error occured handling outbound message: org.jboss.ws.extensions.security.WSSecurityException: Problems loading Keystore: Keystore was tampered with, or password was incorrect at org.jboss.ws.extensions.security.SecurityStore.loadStore(SecurityStore.java:167) at org.jboss.ws.extensions.security.SecurityStore.loadKeyStore(SecurityStore.java:100) at org.jboss.ws.extensions.security.SecurityStore.<init>(SecurityStore.java:90) at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleOutbound(WSSecurityDispatcher.java:303) at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleOutboundSecurity(WSSecurityHandler.java:95) at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient.handleOutbound(WSSecurityHandlerClient.java:45) at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140) at org.jboss.ws.core.jaxws.client.ClientImpl.callRequestHandlerChain(ClientImpl.java:160) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:297) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) at $Proxy25.getVersion(Unknown Source) at de.hska.test.JBossWSTest.getVersion(JBossWSTest.java:130) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.experimental.theories.runner.Function.invoke(Function.java:25) at org.junit.experimental.theories.runner.TheoryContainerReference.invoke(TheoryContainerReference.java:26) at org.junit.experimental.theories.runner.TheoryContainerReference.runWithParameters(TheoryContainerReference.java:107) at org.junit.experimental.theories.runner.TheoryMethod.invoke(TheoryMethod.java:37) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:26) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:36) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:36) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:766) Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect at com.sun.crypto.provider.JceKeyStore.engineLoad(DashoA13*..) at java.security.KeyStore.load(KeyStore.java:1185) at org.jboss.ws.extensions.security.SecurityStore.loadStore(SecurityStore.java:155) ... 38 more -- 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, 12 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1903) DOMUtils doesn clear thread locals

by Heiko Braun (JIRA)

DOMUtils doesn clear thread locals ---------------------------------- Key: JBWS-1903 URL: http://jira.jboss.com/jira/browse/JBWS-1903 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: 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

17 years

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1882) Reorganize wiki documentation

by Alessio Soldano (JIRA)

Reorganize wiki documentation ----------------------------- Key: JBWS-1882 URL: http://jira.jboss.com/jira/browse/JBWS-1882 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano Wiki pages need to be reorganized according to the productivity strategy introduced here: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121127 This implies better leveraging wiki categories, providing new pages, enhancing the current ones, providing the different user "red paths", etc. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2007