March 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2078) Vote for BasicSecurityProfile-1.1

by Thomas Diesler (JIRA)

Vote for BasicSecurityProfile-1.1 --------------------------------- Key: JBWS-2078 URL: http://jira.jboss.com/jira/browse/JBWS-2078 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productization Reporter: Thomas Diesler Fix For: jbossws-voting Please vote for BasicSecurityProfile-1.0 if this is relevant to your enterprise web services http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html Defines the WS-I Basic Security Profile 1.0 (hereafter, "Profile"), consisting of a set of non-proprietary Web services specifications, along with clarifications to and amplifications of those specifications which promote interoperability. Section 1 introduces the Profile, and relates the philosophy that it takes with regard to interoperability. Section 2, "Scope of the Profile," delimits the areas where the Profile improves interoperability. Section 3, "Profile Conformance," explains what it means to be conformant to the Profile. Each subsequent section addresses a component of the Profile, and consists of two parts; an overview detailing the component specifications and their extensibility points, followed by subsections that address individual parts of the component specifications. Note that there is no relationship between the section numbers in this document and those in the referenced specifications. In order to secure a communication between two parties, the two parties must exchange security credentials (either directly or indirectly). However, each party needs to determine if they can "trust" the asserted credentials of the other party. This specification defines extensions to WS-Security for issuing and exchanging security tokens and ways to establish and access the presence of trust relationships. Using these extensions, applications can engage in secure communication designed to work with the general Web Services framework, including WSDL service descriptions, UDDI businessServices and bindingTemplates, and SOAP messages. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Commented: (JBWS-670) Provide JMS transport for JAX-WS client

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-670?page=comments#action_12404396 ] Thomas Diesler commented on JBWS-670: ------------------------------------- AFAICS there are a number of proposals, but no standard http://ws.apache.org/wsif/providers/wsdl_extensions/jms_extension.html http://cwiki.apache.org/CXF20DOC/jms-transport.html http://weblogs.java.net/blog/vivekp/archive/2007/01/jms_soapwsdl_bi.html > Provide JMS transport for JAX-WS client > --------------------------------------- > > Key: JBWS-670 > URL: http://jira.jboss.com/jira/browse/JBWS-670 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > > Currently, the client will have to use the JMS API directly > InitialContext context = new InitialContext(); > QueueConnectionFactory connectionFactory = (QueueConnectionFactory)context.lookup("ConnectionFactory"); > Queue reqQueue = (Queue)context.lookup("queue/RequestQueue"); > Queue resQueue = (Queue)context.lookup("queue/ResponseQueue"); > QueueConnection con = connectionFactory.createQueueConnection(); > QueueSession session = con.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); > QueueReceiver receiver = session.createReceiver(resQueue); > ResponseListener responseListener = new ResponseListener(); > receiver.setMessageListener(responseListener); > con.start(); > TextMessage message = session.createTextMessage(reqMessage); > message.setJMSReplyTo(resQueue); > waitForResponse = true; > > QueueSender sender = session.createSender(reqQueue); > sender.send(message); > sender.close(); > int timeout = 5000; > while (waitForResponse && timeout > 0) > { > Thread.sleep(100); > timeout -= 100; > } > assertNotNull("Expected response message", responseListener.resMessage); > assertEquals(DOMUtils.parse(resMessage), DOMUtils.parse(responseListener.resMessage)); > con.stop(); > session.close(); > con.close(); > Instead, the client should use the standard JAX-WS API to consume a wsdl that defines the jms binding -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-670) Provide JMS transport for JAX-WS client

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-670?page=all ] Thomas Diesler updated JBWS-670: -------------------------------- Summary: Provide JMS transport for JAX-WS client (was: JMS transport via JBoss Remoting) Description: Currently, the client will have to use the JMS API directly InitialContext context = new InitialContext(); QueueConnectionFactory connectionFactory = (QueueConnectionFactory)context.lookup("ConnectionFactory"); Queue reqQueue = (Queue)context.lookup("queue/RequestQueue"); Queue resQueue = (Queue)context.lookup("queue/ResponseQueue"); QueueConnection con = connectionFactory.createQueueConnection(); QueueSession session = con.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); QueueReceiver receiver = session.createReceiver(resQueue); ResponseListener responseListener = new ResponseListener(); receiver.setMessageListener(responseListener); con.start(); TextMessage message = session.createTextMessage(reqMessage); message.setJMSReplyTo(resQueue); waitForResponse = true; QueueSender sender = session.createSender(reqQueue); sender.send(message); sender.close(); int timeout = 5000; while (waitForResponse && timeout > 0) { Thread.sleep(100); timeout -= 100; } assertNotNull("Expected response message", responseListener.resMessage); assertEquals(DOMUtils.parse(resMessage), DOMUtils.parse(responseListener.resMessage)); con.stop(); session.close(); con.close(); Instead, the client should use the standard JAX-WS API to consume a wsdl that defines the jms binding > Provide JMS transport for JAX-WS client > --------------------------------------- > > Key: JBWS-670 > URL: http://jira.jboss.com/jira/browse/JBWS-670 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > > Currently, the client will have to use the JMS API directly > InitialContext context = new InitialContext(); > QueueConnectionFactory connectionFactory = (QueueConnectionFactory)context.lookup("ConnectionFactory"); > Queue reqQueue = (Queue)context.lookup("queue/RequestQueue"); > Queue resQueue = (Queue)context.lookup("queue/ResponseQueue"); > QueueConnection con = connectionFactory.createQueueConnection(); > QueueSession session = con.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); > QueueReceiver receiver = session.createReceiver(resQueue); > ResponseListener responseListener = new ResponseListener(); > receiver.setMessageListener(responseListener); > con.start(); > TextMessage message = session.createTextMessage(reqMessage); > message.setJMSReplyTo(resQueue); > waitForResponse = true; > > QueueSender sender = session.createSender(reqQueue); > sender.send(message); > sender.close(); > int timeout = 5000; > while (waitForResponse && timeout > 0) > { > Thread.sleep(100); > timeout -= 100; > } > assertNotNull("Expected response message", responseListener.resMessage); > assertEquals(DOMUtils.parse(resMessage), DOMUtils.parse(responseListener.resMessage)); > con.stop(); > session.close(); > con.close(); > Instead, the client should use the standard JAX-WS API to consume a wsdl that defines the jms binding -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2076) Make sure external link to framework is tagged.

by Richard Opalka (JIRA)

Make sure external link to framework is tagged. ----------------------------------------------- Key: JBWS-2076 URL: http://jira.jboss.com/jira/browse/JBWS-2076 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.4, jbossws-metro-1.0.1, jbossws-cxf-1.0.1 It needs to point to the framework tag for a release. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1994) Improve the metro build

by Thomas Diesler (JIRA)

Improve the metro build ----------------------- Key: JBWS-1994 URL: http://jira.jboss.com/jira/browse/JBWS-1994 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-metro-1.0.1 The build fails when invoked with Ant. If this is intensional, we should have proper error messages [tdiesler@tddell trunk]$ ant main build.metro: [exec] Buildfile: metro-build-adapter.xml [exec] BUILD FAILED [exec] Target `WSIT.main' does not exist in this project. It is used from target `-metro.runtime.jar'. [exec] Total time: 1 second BUILD FAILED /home/tdiesler/svn/jbossws/stack/metro/trunk/ant-import/build-metro.xml:78: The following error occurred while executing this line: /home/tdiesler/svn/jbossws/stack/metro/trunk/ant-import/build-metro.xml:23: exec returned: 1 -- 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, 1 month

2
25
0 / 0

[JBoss JIRA] Created: (JBWS-1864) Extend MTOM test coverage to verify different data types

by Heiko Braun (JIRA)

Extend MTOM test coverage to verify different data types --------------------------------------------------------- Key: JBWS-1864 URL: http://jira.jboss.com/jira/browse/JBWS-1864 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: integration-metro, jbossws-jaxws Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.1.0 Currently the test coverage only uses simple types like Strings for instance. The MTOM test cases shoule be extended to verify that other possible attachment data types do work on both optimized and regular messages. -- 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2007) Release jbossws-3.0.1 binaries and sources

by Richard Opalka (JIRA)

Release jbossws-3.0.1 binaries and sources ------------------------------------------ Key: JBWS-2007 URL: http://jira.jboss.com/jira/browse/JBWS-2007 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-3.0.1 The release criteria for jbossws are: * release jbossws-native * release jbossws-metro * release jbossws-cxf -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Updated: (JBWS-1119) Add support for fault signing and encryption

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1119?page=all ] Alessio Soldano updated JBWS-1119: ---------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138308#4138308 > Add support for fault signing and encryption > -------------------------------------------- > > Key: JBWS-1119 > URL: http://jira.jboss.com/jira/browse/JBWS-1119 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Assigned To: Alessio Soldano > Fix For: jbossws-1.0.3, jbossws-native-2.0.5 > > > Add the ability to sign faults. WS-Security faults, will of course be unsigned. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1119) Add support for fault signing and encryption

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1119?page=all ] Alessio Soldano updated JBWS-1119: ---------------------------------- Fix Version/s: jbossws-native-2.0.5 > Add support for fault signing and encryption > -------------------------------------------- > > Key: JBWS-1119 > URL: http://jira.jboss.com/jira/browse/JBWS-1119 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Assigned To: Alessio Soldano > Fix For: jbossws-1.0.3, jbossws-native-2.0.5 > > > Add the ability to sign faults. WS-Security faults, will of course be unsigned. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-1119) Add support for fault signing and encryption

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1119?page=all ] Alessio Soldano reopened JBWS-1119: ----------------------------------- > Add support for fault signing and encryption > -------------------------------------------- > > Key: JBWS-1119 > URL: http://jira.jboss.com/jira/browse/JBWS-1119 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Assigned To: Jason T. Greene > Fix For: jbossws-1.0.3, jbossws-native-2.0.5 > > > Add the ability to sign faults. WS-Security faults, will of course be unsigned. -- 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, 1 month

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 March 2008