February 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2933) NPE in WebServiceContext unbind code

by Richard Opalka (JIRA)

NPE in WebServiceContext unbind code ------------------------------------ Key: JBWS-2933 URL: https://jira.jboss.org/jira/browse/JBWS-2933 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.3.0 My server code employs an injected WebServiceContext resource. Occasionally, the service call falls over with a null pointer exception when attempting to dereference the injected context. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2308) Wrong fault handling with logical handlers

by Alessio Soldano (JIRA)

Wrong fault handling with logical handlers ------------------------------------------ Key: JBWS-2308 URL: https://jira.jboss.org/jira/browse/JBWS-2308 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-3.0.3 Reporter: Alessio Soldano We have some issue in fault/exception handling when logical handlers are used. The jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ClientLogicalOutboundHandleFaultFalseTest and jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ClientLogicalInboundHandleFaultFalseTest are failing. Identify the testcase, reproduce in jbossws-metro testcase and fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2931) OneWay invocations to a webservice result in ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file.

by Boris Belovic (JIRA)

OneWay invocations to a webservice result in ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file. -------------------------------------------------------------------------------------------------------- Key: JBWS-2931 URL: https://jira.jboss.org/jira/browse/JBWS-2931 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.1 Environment: SOA Platform 5, CR1 Reporter: Boris Belovic When tried to invoke Oneway method on WS endpoint I got this exception. The invocation of Oneway method itself is correct (all statements in Oneway method are executed), but after this invocation there is a Premature end of file error in the client. (See following stacktrace). [java] Exception in thread "main" com.sun.xml.internal.ws.streaming.XMLStreamReaderException: XML reader error: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] [java] Message: Premature end of file. [java] at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:242) [java] at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:70) [java] at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:85) [java] at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:75) [java] at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:167) [java] at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:149) [java] at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:121) [java] at com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280) [java] at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:158) [java] at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74) [java] at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:581) [java] at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:540) [java] at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:525) [java] at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:422) [java] at com.sun.xml.internal.ws.client.Stub.process(Stub.java:235) [java] at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:120) [java] at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230) [java] at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210) [java] at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103) [java] at $Proxy26.oneWayMethod(Unknown Source) [java] at org.jboss.soa.esb.samples.quickstart.ws_i.client.HelloWorldClient.main(Unknown Source) [java] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] [java] Message: Premature end of file. [java] at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:588) [java] at com.sun.xml.internal.ws.util.xml.XMLStreamReaderFilter.next(XMLStreamReaderFilter.java:78) [java] at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:51) [java] ... 19 more This issue came as a part of SOA-1945. There were problems with our WISE SOAPClient, after these were solved Premature end of file appeared in the server console. It was tracked down that this issue originates in JBossWS (see linked issue for details) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2929) Cannot determine variable name for result value

by Marco Zanker (JIRA)

Cannot determine variable name for result value ----------------------------------------------- Key: JBWS-2929 URL: https://jira.jboss.org/jira/browse/JBWS-2929 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-native-3.0.5 Environment: Windows XP Prof; jboss-5.0.0.GA Reporter: Marco Zanker During deployment of this webservice, I receive this error message "Could not determine variable name for element: result". This ws deplyoment works fine under JBoss 4.0.2. I tried to get an answer over the community forum, but there is no response. This problem is similar to the issue JBWS-2035. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2926) WSAddressingClientHandler does not set the action value from soap action

by Jim Ma (JIRA)

WSAddressingClientHandler does not set the action value from soap action ------------------------------------------------------------------------ Key: JBWS-2926 URL: https://jira.jboss.org/jira/browse/JBWS-2926 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2, jbossws-native-3.1.2 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.3.0 When soap action url value is set in requestContext , WSAddressingClientHandler does not put this value in the wsa action . It uses the operation name as its wsa action value instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2925) Investigate jaxws standalone TCK forward test issues

by Jim Ma (JIRA)

Investigate jaxws standalone TCK forward test issues ---------------------------------------------------- Key: JBWS-2925 URL: https://jira.jboss.org/jira/browse/JBWS-2925 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jim Ma Assignee: Jim Ma -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2924) WSAddressingClientHandler does not set the action value from soap action

by Jim Ma (JIRA)

WSAddressingClientHandler does not set the action value from soap action ------------------------------------------------------------------------ Key: JBWS-2924 URL: https://jira.jboss.org/jira/browse/JBWS-2924 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.3.0 When the soap action url value is set in requestContext , WSAddressingClientHandler does not put this value in the wsa action . It uses the operation name as its wsa action value instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1309) Support xml overrides for @PortComponent

by Jason T. Greene (JIRA)

Support xml overrides for @PortComponent ---------------------------------------- Key: JBWS-1309 URL: http://jira.jboss.com/jira/browse/JBWS-1309 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxws Reporter: Jason T. Greene Fix For: jbossws-2.0.0 Similar to EJB3 annotations, we need to support an xml override for the PortComponent annotation. The information will then need to be pulled from the JBoss metadata. -- 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

14 years, 10 months

7
22
0 / 0

[JBoss JIRA] Created: (JBWS-2838) Default value of org.jboss.ws.backward_compatible_context_creator property have to be false when we'll want to be TCK6 compatible

by Richard Opalka (JIRA)

Default value of org.jboss.ws.backward_compatible_context_creator property have to be false when we'll want to be TCK6 compatible --------------------------------------------------------------------------------------------------------------------------------- Key: JBWS-2838 URL: https://jira.jboss.org/jira/browse/JBWS-2838 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.3, jbossws-metro-3.3, jbossws-native-3.3 See jbossws-common/src/main/java/org/jboss/ws/Constants.java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2010