September 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1816) JAXWS SOAPFault inheritance

by Thomas Diesler (JIRA)

JAXWS SOAPFault inheritance --------------------------- Key: JBWS-1816 URL: http://jira.jboss.com/jira/browse/JBWS-1816 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.2 I'm using wsprovide (an ant task in maven on windows) to generate my wsdl and then wsconsume to generate my client classes. My web service method throws multiple exceptions, some of which extend from each other. Unfortunately that inheritance relationship is lost in the generated wsdl (no < extension base...) and of course in the client classes. Is there some way to get the wsprovide task to do what I'm asking for? Maybe with an annotation or something specific passed in when I call the task? Thanks in advance. BTW - there are multiple JIRA items (like: http://jira.jboss.com/jira/browse/JBWS-251) that refer to this issue issue. However it doesn't appear that it ever valid or addressed. So I'm wondering if there's something basic that I should be doing? Like digging into the documentation on javaToWSDL which I believe is being used by wsprovide. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBWS-1832) Investigate, design and implement WS-RM global configuration

by Richard Opalka (JIRA)

Investigate, design and implement WS-RM global configuration ------------------------------------------------------------ Key: JBWS-1832 URL: http://jira.jboss.com/jira/browse/JBWS-1832 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assigned To: Richard Opalka -- 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

1
1
0 / 0

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

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-1762) web.xml modified to web.xml.org - Subsequent runs fail

by Heiko Braun (JIRA)

web.xml modified to web.xml.org - Subsequent runs fail ------------------------------------------------------ Key: JBWS-1762 URL: http://jira.jboss.com/jira/browse/JBWS-1762 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: 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, 11 months

3
23
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-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-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-1799) Two ejb3s exposed as 2 different web services in the same ear file. Can't have same methods with different parameters..

by Sureshbabu Thyvalappil (JIRA)

Two ejb3s exposed as 2 different web services in the same ear file. Can't have same methods with different parameters.. ----------------------------------------------------------------------------------------------------------------------- Key: JBWS-1799 URL: http://jira.jboss.com/jira/browse/JBWS-1799 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Environment: Debian etch. Reporter: Sureshbabu Thyvalappil Please look at the url for description. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116665 First ejb: @WebService(name="UserAccountServiceEndPoint", targetNamespace="namespace1", serviceName="UserAccountService1.0") @SOAPBinding(style=SOAPBinding.Style.DOCUMENT,use=SOAPBinding.Use.LITERAL) @Stateless @WebContext(transportGuarantee="NONE",contextRoot="/svc-useracctv1.0",urlPattern="/UserAccountService1.0") public class UserAccountService implements IUserAccountService { @WebMethod @TransactionAttribute(javax.ejb.TransactionAttributeType.SUPPORTS) public boolean authenticate(@WebParam(name="username") String aUsername) { boolean ret; ......... return ret; } } interface for 1st ejb: @Remote public interface IUserAccountService { public boolean authenticate(String aUsername); } second ejb: @WebService(name="UserAccountServiceExtEndPoint", targetNamespace="namespaceExt", serviceName="UserAccountServiceExt1.0") @SOAPBinding(style=SOAPBinding.Style.DOCUMENT,use=SOAPBinding.Use.LITERAL) @Stateless @WebContext(transportGuarantee="NONE",contextRoot="/svc-useracctv1.0",urlPattern="/UserAccountServiceExt1.0") public class UserAccountServiceExt implements IUserAccountServiceExt { @WebMethod @TransactionAttribute(javax.ejb.TransactionAttributeType.SUPPORTS) public boolean authenticate(@WebParam(name="username") String aUsername, @WebParam(name="password") String password) { boolean ret; ......... return ret; } } interface for 2nd ejb: @Remote public interface IUserAccountServiceExt { public boolean authenticate(String aUsername, String aPassword); } -- 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
10
0 / 0

[JBoss JIRA] Created: (JBWS-1793) Verify that all scripts are working properly

by Thomas Diesler (JIRA)

Verify that all scripts are working properly -------------------------------------------- Key: JBWS-1793 URL: http://jira.jboss.com/jira/browse/JBWS-1793 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: tools-jaxrpc, tools-jaxws Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-2.0.2 There are reports of incorrect classpaths in scripts that we distribute. Please setup test cases that verify that all scripts are working properly. This includes windows scripts. Talk to QA about automatically testing on MSFT. This issue should record script test coverage -- 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

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