March 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3473) Update jbossws-native-core as part of jbossws-cxf stack installation

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3473: ------------------------------------- Summary: Update jbossws-native-core as part of jbossws-cxf stack installation Key: JBWS-3473 URL: https://issues.jboss.org/browse/JBWS-3473 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.1 Once the clean up of jbws-native (JBWS-3462) is completed, we need to make the jbossws-cxf depend on the native core library artifact (or the whole native prj?) and install it as part of the jbossws-cxf installation process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3462) Remove unsupported features

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3462: ------------------------------------ Summary: Remove unsupported features Key: JBWS-3462 URL: https://issues.jboss.org/browse/JBWS-3462 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1, jbossws-cxf-4.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] (JBWS-3472) Remove ws-addressing support

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3472: ------------------------------------ Summary: Remove ws-addressing support Key: JBWS-3472 URL: https://issues.jboss.org/browse/JBWS-3472 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3471) Remove MTOM & SWAREF support

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3471: ------------------------------------ Summary: Remove MTOM & SWAREF support Key: JBWS-3471 URL: https://issues.jboss.org/browse/JBWS-3471 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3470) Infinite loop in org.jboss.ws.core.soap.NodeImpl

by David Winslow (JIRA)

David Winslow created JBWS-3470: ----------------------------------- Summary: Infinite loop in org.jboss.ws.core.soap.NodeImpl Key: JBWS-3470 URL: https://issues.jboss.org/browse/JBWS-3470 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.0 Environment: JBoss AS 5.1.0GA Reporter: David Winslow When there is an issue with the DOM document uncovered in assertParent(), the construction of the exception calls DOMWriter.printNode(). This method ends up recursively calling back to the NodeImpl.getParent() which calls NodeImpl.assertParent(), which fails and starts the whole cycle over again until the thread blows up with a stack overflow. Sample stack trace of the infinite recursion: at org.jboss.ws.core.soap.NodeImpl.getParentNode(NodeImpl.java:276) at org.jboss.wsf.common.DOMWriter.getNamespaceURI(DOMWriter.java:518) at org.jboss.wsf.common.DOMWriter.printInternal(DOMWriter.java:299) at org.jboss.wsf.common.DOMWriter.print(DOMWriter.java:233) at org.jboss.wsf.common.DOMWriter.printNode(DOMWriter.java:152) at org.jboss.ws.core.soap.NodeImpl.assertSOAPParent(NodeImpl.java:588) at org.jboss.ws.core.soap.NodeImpl.getParentNode(NodeImpl.java:276) at org.jboss.wsf.common.DOMWriter.getNamespaceURI(DOMWriter.java:518) at org.jboss.wsf.common.DOMWriter.printInternal(DOMWriter.java:299) at org.jboss.wsf.common.DOMWriter.print(DOMWriter.java:233) at org.jboss.wsf.common.DOMWriter.printNode(DOMWriter.java:152) at org.jboss.ws.core.soap.NodeImpl.assertSOAPParent(NodeImpl.java:588) at org.jboss.ws.core.soap.NodeImpl.getParentNode(NodeImpl.java:276) at org.jboss.wsf.common.DOMWriter.getNamespaceURI(DOMWriter.java:518) at org.jboss.wsf.common.DOMWriter.printInternal(DOMWriter.java:299) at org.jboss.wsf.common.DOMWriter.print(DOMWriter.java:233) at org.jboss.wsf.common.DOMWriter.printNode(DOMWriter.java:152) at org.jboss.ws.core.soap.NodeImpl.assertSOAPParent(NodeImpl.java:588) at org.jboss.ws.core.soap.NodeImpl.getParentNode(NodeImpl.java:276) at org.jboss.wsf.common.DOMWriter.getNamespaceURI(DOMWriter.java:518) at org.jboss.wsf.common.DOMWriter.printInternal(DOMWriter.java:299) at org.jboss.wsf.common.DOMWriter.print(DOMWriter.java:233) at org.jboss.wsf.common.DOMWriter.printNode(DOMWriter.java:152) at org.jboss.ws.core.soap.NodeImpl.assertSOAPParent(NodeImpl.java:588) This may affect other versions as well but was uncovered using 3.4.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2070) Add attachment interop endpoint for MTOM and SwaRef

by Heiko Braun (JIRA)

Add attachment interop endpoint for MTOM and SwaRef --------------------------------------------------- Key: JBWS-2070 URL: http://jira.jboss.com/jira/browse/JBWS-2070 Project: JBoss Web Services Issue Type: Sub-task 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

12 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-2833) WebServiceContext#getUserPrincipal() returns null when a service is protected by "Standard WSSecurity Endpoint"

by Morten Andersen (JIRA)

WebServiceContext#getUserPrincipal() returns null when a service is protected by "Standard WSSecurity Endpoint" --------------------------------------------------------------------------------------------------------------- Key: JBWS-2833 URL: https://jira.jboss.org/jira/browse/JBWS-2833 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-native-3.1.2 Environment: jboss-5.1.0.GA (i.e. JBoss Web Services version 3.1.2.GA) java 1.6 Reporter: Morten Andersen When exposing a webservice using the "@WebServiceProvider" annotation, and protecting it with WSSE username token the WebServiceContext#userPrincipal is not set. The WEB-INF/jboss-wsse-server.xml is configured as described here: http://www.jboss.org/community/wiki/JBossWS-WS-Securityoptions#POJO_Endpo... Although this does not really seem to be enough, as it is also required to have META-INF/standard-jaxws-endpoint-config.xml file with only the "Standard WSSecurity Endpoint" on the server to actually enforce the authentication of the username token. Attached: * wstest.war: example war - exposing one webservice (compiled from the content of server.zip) * server.zip: source for the wstest.war * client.zip: simple client for the server, sending a username token. Reproducing the problem: 1) deploy wstest.war to a jboss 5.1.0 2) open the run.sh in the client.zip, and set the JBOSS_5 to fit your installation. It the server is not listening on 8080, modify the url in the client source (WsExampleClient.java). 3) compile and run the client, by running ./run.sh 4) inspect the server log. If this says: "[INFO] Principal = null" we have the problem (expected principal = admin) Server code: * service: server.zip:src/main/java/org/example/WsExample.java * wsdl: server.zip:src/main/webapp/WEB-INF/wsdl * wsse-config: server.zip:src/main/webapp/WEB-INF/jboss-wsse-server.xml * wsse-config2: server.zip:src/main/webapp/META-INF/standard-jaxws-endpoint-config.xml It seems that "wsse-config2" is required. If this is not present, it is possible for the client to send any client credentials it want (or leave them out) and it will still get admission to the service. Other areas where this has been discussed: * http://www.jboss.org/index.html?module=bb&op=viewtopic&t=127582&postdays=... * http://www.jboss.org/community/wiki/jbosssecuritytokenservice#comment-2075 (in relation to the same problem in the JBoss STS) -- 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

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] (JBWS-2575) Client received com.sun.xml.ws.streaming.XMLStreamReaderException when invoking WebService annotated with OneWay

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-2575?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-2575: ---------------------------------- Assignee: (was: Alessio Soldano) > Client received com.sun.xml.ws.streaming.XMLStreamReaderException when invoking WebService annotated with OneWay > ---------------------------------------------------------------------------------------------------------------- > > Key: JBWS-2575 > URL: https://issues.jboss.org/browse/JBWS-2575 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Environment: JBoss 5.0.0 under Windows XP > wsdl and stub generated using jax-ws tools > Reporter: Mosse Franck > > A standalone client receives an exception when it tries to invoke a web service annotated with @OneWay. > The exception received on the client side is : > com.sun.xml.ws.streaming.XMLStreamReaderException: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog > at [row,col {unknown-source}]: [1,0] > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:242) > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:70) > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:85) > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:75) > at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:167) > at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:149) > at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:121) > at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280) > at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:158) > at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74) > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559) > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518) > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503) > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400) > at com.sun.xml.ws.client.Stub.process(Stub.java:235) > at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:120) > at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230) > at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210) > at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103) > at $Proxy30.createPerson(Unknown Source) > at test.example1.TestPeopleManager.testCreatePerson(TestPeopleManager.java:41) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) > at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) > at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) > at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) > at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) > at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66) > at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) > at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) > at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) > at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog > at [row,col {unknown-source}]: [1,0] > at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:686) > at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134) > at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040) > at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069) > at com.sun.xml.ws.util.xml.XMLStreamReaderFilter.next(XMLStreamReaderFilter.java:56) > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:51) > ... 39 more > The code of the web service is : > package test.example1; > import javax.ejb.Stateless; > import javax.jws.Oneway; > import javax.jws.WebMethod; > import javax.jws.WebParam; > import javax.jws.WebService; > @WebService( name="PeopleManager", serviceName="PeopleManager", targetNamespace="http://techtip.com/samples/example1") > @Stateless > public class PeopleManager { > @WebMethod( operationName="createPerson") > @Oneway > public void createPerson ( @WebParam(name="firstName") String firstName, @WebParam(name="lastName")String lastName, @WebParam(name="age") int age) > { > System.out.println ("Creating person [firstName=" + firstName + "; lastName=" + lastName + ";age=" + age + "]"); > } > } > Remark : If the @OneWay annotation is removed, the invocation from the client is successful. > The code of the client is : > package test.example1; > import java.net.MalformedURLException; > import java.net.URL; > import javax.xml.namespace.QName; > import org.junit.BeforeClass; > import org.junit.Test; > import test.example1.generated.*; > public class TestPeopleManager { > > private static PeopleManager peopleManager; > private static final String HOST_NAME = "localhost"; > private static final String PORT_NUMBER = "8080"; > private static final String TARGET_NAMESPACE = "http://techtip.com/samples/example1"; > > @BeforeClass > public static void beforeClass () throws MalformedURLException > { > String wsdlUrl = "http://" + HOST_NAME + ":" + PORT_NUMBER + "/TestWebService/PeopleManager?wsdl"; > URL wsdlLocation = new URL( wsdlUrl); > QName serviceName = new QName( > TARGET_NAMESPACE, > "PeopleManager" > ); > > PeopleManager_Service service = new PeopleManager_Service( > wsdlLocation, serviceName > ); > > peopleManager = service.getPeopleManagerPort (); > > } > @Test > public void testCreatePerson() throws Exception { > peopleManager.createPerson ( "Franck", "Mosse", 40); > } > > } > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3468) Remove ws-security support

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3468: ------------------------------------ Summary: Remove ws-security support Key: JBWS-3468 URL: https://issues.jboss.org/browse/JBWS-3468 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3072) The wsdl part generated for fault message is not valid

by Jim Ma (JIRA)

The wsdl part generated for fault message is not valid ------------------------------------------------------ Key: JBWS-3072 URL: https://jira.jboss.org/browse/JBWS-3072 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2012