jbossws-issues September 2007

jbossws-issues@lists.jboss.org

1 participants
154 discussions

[JBoss JIRA] Created: (JBWS-1805) web.xml not restored when server failure

by Brian Blasko (JIRA)

web.xml not restored when server failure ---------------------------------------- Key: JBWS-1805 URL: http://jira.jboss.com/jira/browse/JBWS-1805 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.1 Environment: RH Linux Reporter: Brian Blasko Priority: Minor The fix for issue JBWS-1762 was to restore the web.xml from the web.xml.org if it was found when shutdown of the web app that the service was deployed in. This fails if there is a crash of the server where the web app is not cleanly shutdown. Subsequent startup will not deploy the web services. -- 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

3
5
0 / 0

[JBoss JIRA] Updated: (JBWS-1138) DOMEnvelopeBuilder misses global namespace declaration

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1138?page=all ] Darran Lofthouse updated JBWS-1138: ----------------------------------- Description: I have just been testing a deployment using the latest version of the JBossWS code and the default request message generated by SoapUI is being rejected. If I send the following message: - (typ is defined on soapenv:Envelope) <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://www.jboss.org/support/phonebook/types"> <soapenv:Body> <typ:lookup> <firstName>Darran</firstName> <surname>Lofthouse</surname> </typ:lookup> </soapenv:Body> </soapenv:Envelope> It is rejected with the following error: - <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header/> <env:Body> <env:Fault> <faultcode>env:Client</faultcode> <faultstring>org.jboss.ws.binding.BindingException: org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: The prefix "typ" for element "typ:lookup" is not bound. @ *unknown*[1,13]</faultstring> </env:Fault> </env:Body> </env:Envelope> However if I modify the request message to : - (Moving the namespace from the Envelope element to the lookup element) <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <typ:lookup xmlns:typ="http://www.jboss.org/support/phonebook/types"> <firstName>Darran</firstName> <surname>Lofthouse</surname> </typ:lookup> </soapenv:Body> </soapenv:Envelope> The web service works as expected: - <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header/> <env:Body> <ns1:lookupResponse xmlns:ns1="http://www.jboss.org/support/phonebook/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <areaCode>01234</areaCode> <number>123456</number> </ns1:lookupResponse> </env:Body> </env:Envelope> Regards, Darran Lofthouse. was: I have just been testing a deployment using the latest version of the JBossWS code and the default request message generated by SoapUI is being rejected. If I send the following message: - (typ is defined on soapenv:Envelope) <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://www.jboss.org/support/phonebook/types"> <soapenv:Body> <typ:lookup> <firstName>Darran</firstName> <surname>Lofthouse</surname> </typ:lookup> </soapenv:Body> </soapenv:Envelope> It is rejected with the following error: - <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header/> <env:Body> <env:Fault> <faultcode>env:Client</faultcode> <faultstring>org.jboss.ws.binding.BindingException: org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: The prefix "typ" for element "typ:lookup" is not bound. @ *unknown*[1,13]</faultstring> </env:Fault> </env:Body> </env:Envelope> However if I modify the request message to : - (Moving the namespace from the Envelope element to the lookup element) <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <typ:lookup xmlns:typ="http://www.jboss.org/support/phonebook/types"> <firstName>Darran</firstName> <surname>Lofthouse</surname> </typ:lookup> </soapenv:Body> </soapenv:Envelope> The web service works as expected: - <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header/> <env:Body> <ns1:lookupResponse xmlns:ns1="http://www.jboss.org/support/phonebook/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <areaCode>01342</areaCode> <number>892702</number> </ns1:lookupResponse> </env:Body> </env:Envelope> Regards, Darran Lofthouse. > DOMEnvelopeBuilder misses global namespace declaration > ------------------------------------------------------ > > Key: JBWS-1138 > URL: http://jira.jboss.com/jira/browse/JBWS-1138 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: jbossws-1.0.2 > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-1.0.3 > > Attachments: PhoneBook.war > > > I have just been testing a deployment using the latest version of the JBossWS code and the default request message generated by SoapUI is being rejected. > If I send the following message: - > (typ is defined on soapenv:Envelope) > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://www.jboss.org/support/phonebook/types"> > <soapenv:Body> > <typ:lookup> > <firstName>Darran</firstName> > <surname>Lofthouse</surname> > </typ:lookup> > </soapenv:Body> > </soapenv:Envelope> > It is rejected with the following error: - > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> > <env:Header/> > <env:Body> > <env:Fault> > <faultcode>env:Client</faultcode> > <faultstring>org.jboss.ws.binding.BindingException: org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: The prefix "typ" for element "typ:lookup" is not bound. @ *unknown*[1,13]</faultstring> > </env:Fault> > </env:Body> > </env:Envelope> > However if I modify the request message to : - (Moving the namespace from the Envelope element to the lookup element) > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> > <soapenv:Body> > <typ:lookup xmlns:typ="http://www.jboss.org/support/phonebook/types"> > <firstName>Darran</firstName> > <surname>Lofthouse</surname> > </typ:lookup> > </soapenv:Body> > </soapenv:Envelope> > The web service works as expected: - > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> > <env:Header/> > <env:Body> > <ns1:lookupResponse xmlns:ns1="http://www.jboss.org/support/phonebook/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <areaCode>01234</areaCode> > <number>123456</number> > </ns1:lookupResponse> > </env:Body> > </env:Envelope> > Regards, > Darran Lofthouse. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1801) WSDL To Java - When an array if returned from a method on the SEI it is incorrectly ommitted from the generated JAX-RPC mapping.

by Darran Lofthouse (JIRA)

WSDL To Java - When an array if returned from a method on the SEI it is incorrectly ommitted from the generated JAX-RPC mapping. --------------------------------------------------------------------------------------------------------------------------------- Key: JBWS-1801 URL: http://jira.jboss.com/jira/browse/JBWS-1801 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxrpc Affects Versions: jbossws-2.0.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.2 When an array if returned from a method on the SEI it is incorrectly ommitted from the generated JAX-RPC mapping. For a background on the reasons why array wrapping is required please see the following issue: - http://jira.jboss.com/jira/browse/JBWS-732 When a wrapped array is used it is possible for us to skip generating the Java class representing the wrapper and to also skip this mapping in the generated JAX-RPC mapping file. Currently the tools are incorrectly identifying a return type from a method on the SEI which is an array as a wrapped type so although the Java class is generated it is ommitted from the generated JAX-RPC mapping. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1794) init-param for handler defined in jaxrpc-config not processed

by Darran Lofthouse (JIRA)

init-param for handler defined in jaxrpc-config not processed ------------------------------------------------------------- Key: JBWS-1794 URL: http://jira.jboss.com/jira/browse/JBWS-1794 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-2.0.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.2 When handlers are defined in the JBossWS specific jaxrpc-config descriptor the init-param values specified are not processed so are not made available to the init method of the handler. -- 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

1
2
0 / 0

← Newer
1
...
13
14
15
16
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues September 2007