January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1548) REST support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1548?page=all ] Thomas Diesler updated JBWS-1548: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > REST support > ------------ > > Key: JBWS-1548 > URL: http://jira.jboss.com/jira/browse/JBWS-1548 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: William DeCoste > Fix For: jbossws-3.x > > > Intuit request. Notes: > Third party presents user credentials via Web service to the server to assure confidentiality. > Third party can be a remote trusted host (e.g. third party application), hosted application (e.g. in remote data center) or a trusted service provider that interact with Intuit Web services. > The Web service can be SOAP or REST Web service. The Server is a business service running Java Web services using a Java EE Web / application server. > The user credentials can be username tokens (e.g. user id and password), digital certificates tokens (e.g. X.509v3 certificates), binary tokens (e.g. biometrics, fingerprint) or a mixture of these tokens (as in multi-factor authentication). > --------------------------------------------------------------------------------------------------------------------------- > System consumes a public REST Web service. > System uses a security token to assure confidentiality when invoking a REST Web service, if sensitive data is carried, or if service provider requires a security token for authentication. > System optionally encrypts or decrypts the sensitive business data when interacting with a REST Web service. > Intuit currently implement REST based Web services through a custom Servlet. Authentication can be achieved by using http based authentication. Support for other security features, would currently need to be implemented by Intuit; maybe using Servlet filters. There are no standards for REST Web services, or for defining value add services such as security. However, according to the Merlin group, Microsoft and IBM have a common way of using REST Web services. Also, Google and Amazon offer REST based Web services too. Therefore, with the absence of any standards, the only real option for JBoss to support REST would be to work with what other vendors are currently doing. However, the REST area is currently in flux, so any implementation would be risky due to the high possibility of change. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1516) Investigate synchronization issue with concurrent requests

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1516?page=all ] Thomas Diesler updated JBWS-1516: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Investigate synchronization issue with concurrent requests > ---------------------------------------------------------- > > Key: JBWS-1516 > URL: http://jira.jboss.com/jira/browse/JBWS-1516 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Heiko Braun > Fix For: jbossws-3.x > > > Performance tests showed that concurrent requests to the same service (shared meta data) suffered from synchronisation issues. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-922) provide integrated browsing of deployed jbossws webservices

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-922?page=all ] Thomas Diesler updated JBWS-922: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > provide integrated browsing of deployed jbossws webservices > ----------------------------------------------------------- > > Key: JBWS-922 > URL: http://jira.jboss.com/jira/browse/JBWS-922 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tools-soapui > Reporter: Ole Matzura > Assigned To: Ole Matzura > Fix For: jbossws-3.x > > > when importing a new wsdl into a soapui project, it should be possible to specify a jbossws installation and show the user a list of deployed services for selection to be imported -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1212) Add support for @SecurityDomain on JSE

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1212?page=all ] Thomas Diesler updated JBWS-1212: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Add support for @SecurityDomain on JSE > -------------------------------------- > > Key: JBWS-1212 > URL: http://jira.jboss.com/jira/browse/JBWS-1212 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-3.x > > > @SecurityDomain is currently only supported for EJB3 endpoints -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-678) OASIS Catalog support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-678?page=all ] Thomas Diesler updated JBWS-678: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > OASIS Catalog support > --------------------- > > Key: JBWS-678 > URL: http://jira.jboss.com/jira/browse/JBWS-678 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-3.x > > Attachments: jboss-entity-resolver.zip > > > From the JAXWS-2.-0 spec > 4.4 Catalog Facility > > JAX-WS mandates support for a standard catalog facility to be used when resolving any Web service docu- 15 > ment that is part of the description of a Web service, specifically WSDL and XML Schema documents. 16 > The facility in question is the OASIS XML Catalogs 1.1 specification [30]. It defines an entity catalog that 17 > handles the following two cases: 18 > ? Mapping an external entity?s public identifier and/or system identifier to a URI reference. 19 > ? Mapping the URI reference of a resource to another URI reference. 20 > Using the entity catalog, an application can package one or more description and/or schema documents in 21 > jar files, avoiding costly remote accesses, or remap remote URIs to other, possibly local ones. Since the 22 > catalog is an XML document, a deployer can easily alter it to suit the local environment, unbeknownst to 23 > the application code. 24 > The catalog is assembled by taking into account all accessible resources whose name is META-INF/jax- 25 > -ws-catalog.xml. Each resource MUST be a valid entity catalog according to the XML Catalogs 1.1 26 > specification. When running on the Java SE platform, the current context class loader MUST be used to 27 > retrieve all the resources with the specified name. Relative URIs inside a catalog file are relative to the 28 > location of the catalog that contains them. 29 > } Conformance (Use of the Catalog): In the process of resolving a URI that points to a WSDL document 30 > or any document reachable from it, a JAX-WS implementation MUST perform a URI resolution for it, as 31 > prescribed by the XML Catalogs 1.1 specification, using the catalog defined above as its entity catalog. 32 > In particular, every JAX-WS API argument or annotation element whose semantics is that of a WSDL 33 > location URI MUST undergo URI resolution using the catalog facility described in this section. 34 > Although defined in the client API chapter for reasons of ease of exposure, use of the catalog is in no way 35 > restricted to client uses of WSDL location URIs. In particular, resolutions of URIs to WSDL and schema 36 > documents that arise during the publishing of endpoint metadata (see 5.2.5) are subject to the requirements 37 > in this section, resulting in catalog-based URI resolutions. > > There is a catalog implementation by Apache > http://xml.apache.org/commons/components/resolver/ > XML Entity and URI Resolvers > http://xml.apache.org/commons/components/resolver/resolver-article.html -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1543) Liberty support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1543?page=all ] Thomas Diesler updated JBWS-1543: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Liberty support > --------------- > > Key: JBWS-1543 > URL: http://jira.jboss.com/jira/browse/JBWS-1543 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: William DeCoste > Fix For: jbossws-3.x > > > Intuit request. Notes: > Support of single sign-on using Liberty, SAML and WS-Federation. > Support of SAML profile. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1461) Migrate our addressing impl to JAXB

by Heiko Braun (JIRA)

Migrate our addressing impl to JAXB ----------------------------------- Key: JBWS-1461 URL: http://jira.jboss.com/jira/browse/JBWS-1461 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Fix For: jbossws-2.0.0 When the addressing custom types (epr, etc) will be marshalled by JAXB, they could be easily be reused to represent addressing elements inside the soap body. -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Updated: (JBWS-1140) Remove Connector xmbean declaration from ejb3 module

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1140?page=all ] Thomas Diesler updated JBWS-1140: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Remove Connector xmbean declaration from ejb3 module > ---------------------------------------------------- > > Key: JBWS-1140 > URL: http://jira.jboss.com/jira/browse/JBWS-1140 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Heiko Braun > Fix For: jbossws-3.x > > -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1546) WS-MEX support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1546?page=all ] Thomas Diesler updated JBWS-1546: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > WS-MEX support > -------------- > > Key: JBWS-1546 > URL: http://jira.jboss.com/jira/browse/JBWS-1546 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: William DeCoste > Fix For: jbossws-3.x > > > Intuit request. Notes: > Support of federated single sign-on using WS-MEX for interoperability -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1412) WS-Eventing clustering capabilities

by Heiko Braun (JIRA)

WS-Eventing clustering capabilities ----------------------------------- Key: JBWS-1412 URL: http://jira.jboss.com/jira/browse/JBWS-1412 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-eventing 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

17 years, 1 month

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2008