October 2007 - jbossws-issues - Jboss List Archives

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

3
4
0 / 0

[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, 12 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

17 years

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

17 years

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

17 years

3
23
0 / 0

[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

17 years

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

17 years

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

17 years

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

17 years

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

17 years

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2007