August 2007 - jbossws-issues - Jboss List Archives

[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

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, 4 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, 5 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, 5 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, 5 months

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

16 years, 5 months

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

16 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1798) JBossWS cannot find local schema with relative url:s

by Oskar Carlstedt (JIRA)

JBossWS cannot find local schema with relative url:s ---------------------------------------------------- Key: JBWS-1798 URL: http://jira.jboss.com/jira/browse/JBWS-1798 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 5.0 Beta2 and integrated JBossWS (2.0.0.DEV) Reporter: Oskar Carlstedt I deploy an ear file in JBoss5 that contains a war and a jar fil. The jar file contains a SLSB and the war file contains the web service (implemented as a Provider<SOAPMessage>). The war file has the following file structure in the the WEB-INF/wsdl folder: WEB-INF/wsdl my-service.wsdl /imported /my-service /1.0-SNAPSHOT my-service.xsd /common /1.0-SNAPSHOT common.xsd the wsdl file has a schema import like <xsd:import schemaLocation="imported/my-service/1.0-SNAPSHOT/my-service.xsd" .../> the my service.xsd imports the common.xsd file with the following import statement <xsd:import schemaLocation="../../common/1.0-SNAPSHOT/common.xsd" .../> Having this configuration will put JBoss into trouble. The error message sent is telling med that parent paths are not allowed, and pointing out to use getParent() instead. So I setting the schemaLocation attribute to getParent()/getParent()/.... will point out another path, but it is completely wrong. PS... I hope I got all "../":s right. Anyway, I have validated my paths so they are correct. DS. -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1468) Fix @Resource WebServiceContext for jbossas-4.2

by Thomas Diesler (JIRA)

Fix @Resource WebServiceContext for jbossas-4.2 ----------------------------------------------- Key: JBWS-1468 URL: http://jira.jboss.com/jira/browse/JBWS-1468 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Reporter: Thomas Diesler Assigned To: Thomas Diesler Priority: Critical Fix For: jbossws-1.2.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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1761) WSProvide ignore SOAPBinding declaration

by Heiko Braun (JIRA)

WSProvide ignore SOAPBinding declaration ---------------------------------------- Key: JBWS-1761 URL: http://jira.jboss.com/jira/browse/JBWS-1761 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Heiko Braun -- 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, 7 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2007