November 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBWS-1194) Release jbossws-1.0.4.GA binary

by Prabhat Jha (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1194?page=comments#action_12346726 ] Prabhat Jha commented on JBWS-1194: ----------------------------------- Against tomcat, I am seeing following errors: TEST-org.jboss.test.ws.jaxrpc.samples.mtom.MTOMTestCase.txt: Caused an ERROR TEST-org.jboss.test.ws.jaxrpc.samples.mtom.MTOMTestCase.txt: Caused an ERROR TEST-org.jboss.test.ws.jaxrpc.samples.mtom.MTOMTestCase.txt: Caused an ERROR TEST-org.jboss.test.ws.jaxrpc.samples.wssecurity.StorePassEncryptTestCase.txt: Caused an ERROR The last failing test could be because tomcat tests were run after sample tests against jbossas were run. I will do a fresh run of tomcat tests and see if the last one disappears. > Release jbossws-1.0.4.GA binary > ------------------------------- > > Key: JBWS-1194 > URL: http://jira.jboss.com/jira/browse/JBWS-1194 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.4 > > > The release criteria for jbossws-1.1.0.GA are: > * pass all internal jbossws tests > * pass all portable j2ee-1.4 tests from the jboss testsuite > * pass all tests in module jaxr,jaxrpc,saaj,webservice from the Sun compatiblity testsuite > * generate all test artifacts with wstools -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1355) CTS: Investigate naming binding failures in java_xml_ws/Service section

by Jason T. Greene (JIRA)

CTS: Investigate naming binding failures in java_xml_ws/Service section ----------------------------------------------------------------------- Key: JBWS-1355 URL: http://jira.jboss.com/jira/browse/JBWS-1355 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Reporter: Jason T. Greene Fix For: jbossws-2.0.0.CR2 This is most likely a problem with our CTS integration layer. -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1354) CTS: Provider implementation gets premature end of file

by Jason T. Greene (JIRA)

CTS: Provider implementation gets premature end of file ------------------------------------------------------- Key: JBWS-1354 URL: http://jira.jboss.com/jira/browse/JBWS-1354 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Environment: com/sun/ts/tests/jaxws/api/javax_xml_ws/Provider/Client.java#invokeTest1_from_wsappclient Reporter: Jason T. Greene Fix For: jbossws-2.0.0.CR2 17:23:12,671 INFO [STDOUT] **** Received in Provider Impl ****** 17:23:12,687 INFO [STDOUT] -> Source=<HelloRequest xmlns="http://helloservice.org/types"><argument>sendSource</argument></HelloRequest> 17:23:12,687 INFO [STDOUT] *** recvBean *** 17:23:12,687 INFO [STDOUT] Received an exception while parsing the source 17:23:12,687 ERROR [STDERR] javax.xml.bind.UnmarshalException - with linked exception: 7:23:12,687 ERROR [STDERR] Caused by: org.xml.sax.SAXParseException: Premature end of file. 17:23:12,687 ERROR [STDERR] at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) 17:23:12,687 ERROR [STDERR] at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) 17:23:12,687 ERROR [STDERR] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) 17:23:12,687 ERROR [STDERR] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) 17:23:12,687 ERROR [STDERR] at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) 17:23:12,687 ERROR [STDERR] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) 17:23:12,687 ERROR [STDERR] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) 17:23:12,687 ERROR [STDERR] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) 17:23:12,687 ERROR [STDERR] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) 17:23:12,687 ERROR [STDERR] at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) 17:23:12,687 ERROR [STDERR] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerI -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1353) CTS: SAXSource not implemented

by Jason T. Greene (JIRA)

CTS: SAXSource not implemented ------------------------------ Key: JBWS-1353 URL: http://jira.jboss.com/jira/browse/JBWS-1353 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Environment: com/sun/ts/tests/jaxws/api/javax_xml_ws/Response/Client.java#getXMLTest_from_wsappclient Reporter: Jason T. Greene Fix For: jbossws-2.0.0.CR2 Dispatch is supposed to support all source types. Looks like we are missing SAX: Caused by: org.jboss.ws.WSException: Source type not implemented: javax.xml.transform.sax.SAXSource at org.jboss.ws.soap.SOAPBodyImpl.getBodyElementFromSource(SOAPBodyImpl.java:365) at org.jboss.ws.soap.SOAPBodyImpl.writeElementContent(SOAPBodyImpl.java:384) at org.jboss.ws.soap.SOAPElementImpl.writeElement(SOAPElementImpl.java:704) at org.jboss.ws.soap.SOAPElementImpl.writeElementContent(SOAPElementImpl.java:719) at org.jboss.ws.soap.SOAPElementImpl.writeElement(SOAPElementImpl.java:704) at org.jboss.ws.soap.SOAPElementWriter.writeElementInternal(SOAPElementWriter.java:147) at org.jboss.ws.soap.SOAPElementWriter.writeElement(SOAPElementWriter.java:128) at org.jboss.ws.soap.SOAPElementWriter.writeElement(SOAPElementWriter.java:107) at org.jboss.ws.binding.soap.SOAPMessageMarshaller.write(SOAPMessageMarshaller.java:77) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.jav -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1194) Release jbossws-1.0.4.GA binary

by Prabhat Jha (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1194?page=comments#action_12346707 ] Prabhat Jha commented on JBWS-1194: ----------------------------------- I did another run of tests today and here is the status: JDK1.4 tests pass with two known errors(JBWS718 and JMS) JDK1.5: Only org.jboss.test.ws.jaxrpc.samples.wssecurity.StorePassEncryptTestCase fail for internal tests and sample tests. When I ran using one-test for ws-internal tests, this test passed but it still failed for sample tests. -Tomcat errors still exist. > Release jbossws-1.0.4.GA binary > ------------------------------- > > Key: JBWS-1194 > URL: http://jira.jboss.com/jira/browse/JBWS-1194 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.4 > > > The release criteria for jbossws-1.1.0.GA are: > * pass all internal jbossws tests > * pass all portable j2ee-1.4 tests from the jboss testsuite > * pass all tests in module jaxr,jaxrpc,saaj,webservice from the Sun compatiblity testsuite > * generate all test artifacts with wstools -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1352) CTS: jaxws/api/javax_xml_ws/Endpoint/Client.java#createTest_from_wsappclient fails

by Jason T. Greene (JIRA)

CTS: jaxws/api/javax_xml_ws/Endpoint/Client.java#createTest_from_wsappclient fails ---------------------------------------------------------------------------------- Key: JBWS-1352 URL: http://jira.jboss.com/jira/browse/JBWS-1352 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Reporter: Jason T. Greene Fix For: jbossws-2.0.0.CR2 11-10-2006 12:12:13: TRACE: resp=false 11-10-2006 12:12:13: ERROR: createTest failed 11-10-2006 12:12:13: ERROR: Exception at: 11-10-2006 12:12:13: ERROR: com.sun.ts.lib.harness.EETest$Fault: createTest failed at com.sun.ts.tests.jaxws.api.javax_xml_ws.Endpoint.Client.createTest(Client.java:239) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.ts.lib.harness.EETest.run(EETest.java:495) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:112) at com.sun.ts.tests.common.vehicle.EmptyVehicleRunner.run(EmptyVehicleRunner.java:30) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:102) at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:392) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:209) at com.sun.ts.lib.harness.EETest.run(EETest.java:204) at com.sun.ts.tests.common.vehicle.wsappclient.WSAppclient.main(WSAppclient.java:39) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ejb3.client.ClientContainer.invokeMain(ClientContainer.java:277) at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:77) at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:174) at org.jboss.client.AppClientMain.main(AppClientMain.java:134) -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1350) CTS: Executor not implemented on Endpoint

by Jason T. Greene (JIRA)

CTS: Executor not implemented on Endpoint ----------------------------------------- Key: JBWS-1350 URL: http://jira.jboss.com/jira/browse/JBWS-1350 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Environment: com/ts/tests/jaxws/api/javax_xml_ws/Endpoint/Client.java#GetSetExecutorTest_from_wsappclient Reporter: Jason T. Greene Fix For: jbossws-2.0.0.CR2 1-10-2006 12:12:52: SVR-ERROR: org.jboss.util.NotImplementedException at org.jboss.ws.jaxws.spi.EndpointImpl.getExecutor(EndpointImpl.java:193) -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1351) CTS: Metadata not implemented on Endpoint

by Jason T. Greene (JIRA)

CTS: Metadata not implemented on Endpoint ----------------------------------------- Key: JBWS-1351 URL: http://jira.jboss.com/jira/browse/JBWS-1351 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Environment: com/sun/ts/tests/jaxws/api/javax_xml_ws/Endpoint/Client.java#GetSetMetaDataTest_from_wsappclient Reporter: Jason T. Greene Fix For: jbossws-2.0.0.CR2 1-10-2006 12:13:02: SVR-ERROR: org.jboss.util.NotImplementedException at org.jboss.ws.jaxws.spi.EndpointImpl.getMetadata(EndpointImpl.java:181) -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1349) CTS: jaxws/api/jaxax_xml_ws/AsyncHandler/Client.java#HandleResponseXMLTest_from_wsappclient hangs

by Jason T. Greene (JIRA)

CTS: jaxws/api/jaxax_xml_ws/AsyncHandler/Client.java#HandleResponseXMLTest_from_wsappclient hangs ------------------------------------------------------------------------------------------------- Key: JBWS-1349 URL: http://jira.jboss.com/jira/browse/JBWS-1349 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jason T. Greene Fix For: jbossws-2.0.0.CR2 -- 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

18 years

1
2
0 / 0

[JBoss JIRA] Updated: (JBWS-652) Add JAAS certificate authentication support to ws-security implementation

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-652?page=all ] Jason T. Greene updated JBWS-652: --------------------------------- Fix Version/s: jbossws-1.0.5 (was: jbossws-1.0.6) A customer has an urgent need for this. There is also high demand. I will find a way to get it done. > Add JAAS certificate authentication support to ws-security implementation > ------------------------------------------------------------------------- > > Key: JBWS-652 > URL: http://jira.jboss.com/jira/browse/JBWS-652 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Fix For: jbossws-1.0.5 > > > Currently X.509 tokens are validated against a truststore that is local to the ws-security deployment. We should offer support for delegating to JAAS/JBossSX so that JEE declarative security can reference known certificates. There is one problem with adding support for this, which is that a WS-Security message may contain many X.509 tokens (perhaps one for signature, and one for encryption), so we would have to somehow decide to pick one. -- 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

18 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2006