August 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2727) Fix AS-Tests-AS-6.0.0 hudson job

by Alessio Soldano (JIRA)

Fix AS-Tests-AS-6.0.0 hudson job -------------------------------- Key: JBWS-2727 URL: https://jira.jboss.org/jira/browse/JBWS-2727 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 The AS-Tests-AS-6.0.0 job on hudson is failing since the latest changes in AS trunk build. That needs to be fixed (and it might require running it with jdk 1.6). -- 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

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2726) Rewrite dar/JMSClientTestCase

by Richard Opalka (JIRA)

Rewrite dar/JMSClientTestCase ----------------------------- Key: JBWS-2726 URL: https://jira.jboss.org/jira/browse/JBWS-2726 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Alessio Soldano Fix For: jbossws-native-3.2.1 I'm assigning this issue to you Alessio because you're the test author. dar/JMSClientTestCase test uses MBean server and checks MessageCount attribute for detecting whether message have been delivered to MDB, or not. However this approach causes transient failures against different AS versions. For example when I run that test standalone against AS 5.1.0, I'm getting failure for the first time. Other test executions pass without problems (i.e. 2-nd and other tries). Please consider using file approach instead of checking MBean server attributes. This will be more reliable approach IMHO. -- 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

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2320) Check JBossWS Maven Support on Windows OS

by Richard Opalka (JIRA)

Check JBossWS Maven Support on Windows OS ----------------------------------------- Key: JBWS-2320 URL: https://jira.jboss.org/jira/browse/JBWS-2320 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4 It will make our community happy -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2672) Make the JBoss Remoting property 'socketFactoryClassName' available to allow clients to specify the SocketFactory

by Darran Lofthouse (JIRA)

Make the JBoss Remoting property 'socketFactoryClassName' available to allow clients to specify the SocketFactory ----------------------------------------------------------------------------------------------------------------- Key: JBWS-2672 URL: https://jira.jboss.org/jira/browse/JBWS-2672 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.0 -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2587) Investigate why jaxws.samples.wssecurity.* tests are failing when running whole test suite

by Richard Opalka (JIRA)

Investigate why jaxws.samples.wssecurity.* tests are failing when running whole test suite ------------------------------------------------------------------------------------------ Key: JBWS-2587 URL: https://jira.jboss.org/jira/browse/JBWS-2587 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.0 Reporter: Richard Opalka Assignee: Alessio Soldano Priority: Optional Fix For: jbossws-native-3.1.1 Results : Failed tests: testUsernameTokenNegative(org.jboss.test.ws.jaxws.samples.wssecurity.SimpleUsernameTestCase) testUsernameTokenNegative(org.jboss.test.ws.jaxws.samples.wssecurity.SimpleDispatchTestCase) Tests run: 1438, Failures: 2, Errors: 0, Skipped: 0 I'd like to see that fixed. Feel free to reschedule to next release Alessio (since code freeze is away already) but if you have some time could you have a look now? The strange thing for me is we can't reproduce it on hudson. -- 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

15 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2630) Invalid "Endpoint Address" in http://localhost:8080/jbossws/services, when a .war is embedded in a jar.

by Daniel Bevenius (JIRA)

Invalid "Endpoint Address" in http://localhost:8080/jbossws/services, when a .war is embedded in a jar. --------------------------------------------------------------------------------------------------------- Key: JBWS-2630 URL: https://jira.jboss.org/jira/browse/JBWS-2630 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Priority: Minor I noticed this when working on getting examples for JBossESB running on JBoss AS 5. We have .esb archives (jar archives) that can contain a .war inside of them. For example, we have a quickstart that is named Quickstart_webservice_consumer1.esb which contains a Quickstart_webservice_consumer1.war. Deploying this on AS 5 will produce the following "Endpoint Address" in http://localhost:8080/jbossws/services: http://127.0.0.1:8080/Quickstart_webservice_consumer1-Quickstart_webservi... But if I try to access that the resource is not found. I was not sure about the component for this. The ContextServlet exists in the jbossws-framework project but I don't know if that maps to one of the components in the dropdown. -- 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

15 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2724) JBossWS-Native WSRM Server does not set Accept.AckstTo.Address on CreateSequenceResponse

by Hans Guldager Knudsen (JIRA)

JBossWS-Native WSRM Server does not set Accept.AckstTo.Address on CreateSequenceResponse ---------------------------------------------------------------------------------------- Key: JBWS-2724 URL: https://jira.jboss.org/jira/browse/JBWS-2724 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native, ws-reliable Reporter: Hans Guldager Knudsen Trying to interact with at JBossWS-Native WS-RM enabled endpoint using - MS WCF and Sun Metro 1.4/1.5 clients I noticed that 'native' wsrm server does/can not set the Accept.AckstTo.Address on CreateSequenceResponse. -- 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

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2723) JBossWS-Native WSRM Server does not use Offer Identifier

by Hans Guldager Knudsen (JIRA)

JBossWS-Native WSRM Server does not use Offer Identifier -------------------------------------------------------- Key: JBWS-2723 URL: https://jira.jboss.org/jira/browse/JBWS-2723 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native, ws-reliable Reporter: Hans Guldager Knudsen Trying to interact with at JBossWS-Native WS-RM enabled endpoint using - MS WCF and Sun Metro 1.4/1.5 clients I noticed that 'native' wsrm server does/can not use the Offer Identifier from the incoming CreateSequence, but always generates a new/random. -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2712) Allign JBossWS Scout version with Scout version in AS

by Richard Opalka (JIRA)

Allign JBossWS Scout version with Scout version in AS ----------------------------------------------------- Key: JBWS-2712 URL: https://jira.jboss.org/jira/browse/JBWS-2712 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0 -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2402) Upgrade jUDDI to 2.0rc5

by Alessio Soldano (JIRA)

Upgrade jUDDI to 2.0rc5 ----------------------- Key: JBWS-2402 URL: https://jira.jboss.org/jira/browse/JBWS-2402 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.5 We should upgrade jUDDI dependency to 2.0rc5 to satisfy the SOA-P requirements. See the forum thread for more 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

15 years, 3 months

2
17
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2009