June 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-447) Vote for WS-BPEL

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-447?page=all ] Thomas Diesler updated JBWS-447: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-BPEL > ---------------- > > Key: JBWS-447 > URL: http://jira.jboss.com/jira/browse/JBWS-447 > 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 WS-BPEL if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-bpel/ > Business Process Execution Language for Web Services provides a means to formally specify business processes and interaction protocols. > BPEL4WS provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web Services interaction model and enables it to support business transactions. BPEL4WS defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intra-corporate and the business-to-business spaces. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-504) Vote for WS-Managment

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-504?page=all ] Thomas Diesler updated JBWS-504: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-Managment > --------------------- > > Key: JBWS-504 > URL: http://jira.jboss.com/jira/browse/JBWS-504 > 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 WS-Managment if this is relevant to your enterprise web services > http://msdn.microsoft.com/ws/2004/10/ws-management/ > This specification describes a general SOAP-based protocol for managing systems such as PCs, servers, devices, Web services and other applications, and other manageable entities. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-330) Vote for WS-Distributed Managment

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-330?page=all ] Thomas Diesler updated JBWS-330: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-Distributed Managment > --------------------------------- > > Key: JBWS-330 > URL: http://jira.jboss.com/jira/browse/JBWS-330 > Project: JBoss Web Services > Issue Type: Feature Request > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-Distributed Managment if this is relevant to your enterprise web services > http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsdm > WSDM Overview: > The OASIS Web Services Distributed Management TC is defining two sets of specifications: Web Services Distributed Management: Management Using Web Services(MUWS) and Web Services Distributed Management: Management Of Web Services (MOWS) specifications. > Management Using Web Services > WSDM MUWS 1.0 defines how to represent and access the manageability interfaces of resources as Web services. It is the foundation of enabling management applications to be built using Web services and allows resources to be managed by many managers with one set of instrumentation. This specification provides interoperable, base manageability for monitoring and control managers using Web services. WSDM MUWS 1.0 has been defined in two specifications, MUWS Part 1, which defines the base architectural concepts and required components, and MUWS Part 2 which defines standard composeable support for manageability capabilities. > Management Of Web Services > WSDM MOWS defines the manageability model for managing Web services as a resource and how to describe and access that manageability using MUWS. > The OASIS Web Services Distributed Management TC has approved the Web Services Distributed Management: Management Using Web Services (MUWS) 1.0 and Web Services Distributed Management: Management Of Web Services (MOWS) 1.0 specifications for public review. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-497) Vote for WS-Trust

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-497?page=all ] Thomas Diesler updated JBWS-497: -------------------------------- Component/s: productization (was: jbossws-jaxws) (was: ws-security) > Vote for WS-Trust > ----------------- > > Key: JBWS-497 > URL: http://jira.jboss.com/jira/browse/JBWS-497 > 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 WS-Trust if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-trust/ > The recently updated Web Services Trust Language (WS-Trust) uses the secure messaging mechanisms of WS-Security to define additional primitives and extensions for security token exchange to enable the issuance and dissemination of credentials within different trust domains. > The Web Services Trust Language (WS-Trust) uses the secure messaging mechanisms of WS-Security to define additional primitives and extensions for the issuance, exchange and validation of security tokens. WS-Trust also enables the issuance and dissemination of credentials within different trust domains. > 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-336) Vote for JBossIDE integration

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-336?page=all ] Thomas Diesler updated JBWS-336: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for JBossIDE integration > ----------------------------- > > Key: JBWS-336 > URL: http://jira.jboss.com/jira/browse/JBWS-336 > Project: JBoss Web Services > Issue Type: Feature Request > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > The JBossWS tools project should be well integrated with JBossIDE -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-36) Vote for WS-AtomicTransaction

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-36?page=all ] Thomas Diesler updated JBWS-36: ------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-AtomicTransaction > ----------------------------- > > Key: JBWS-36 > URL: http://jira.jboss.com/jira/browse/JBWS-36 > Project: JBoss Web Services > Issue Type: Feature Request > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-AtomicTransaction if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-tx/ > This specification provides the definition of the atomic transaction coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification. The specification defines three specific agreement coordination protocols for the atomic transaction coordination type: completion, volatile two-phase commit, and durable two-phase commit. Developers can use any or all of these protocols when building applications that require consistent agreement on the outcome of short-lived distributed activities that have the all-or-nothing property. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-501) Vote for WS-MetaDataExchage

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-501?page=all ] Thomas Diesler updated JBWS-501: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-MetaDataExchage > --------------------------- > > Key: JBWS-501 > URL: http://jira.jboss.com/jira/browse/JBWS-501 > 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 WS-MetaDataExchange if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-mex/ > Web services use metadata to describe what other endpoints need to know to interact with them. Specifically, WS-Policy describes the capabilities, requirements, and general characteristics of Web services; WSDL describes abstract message operations, concrete network protocols, and endpoint addresses used by Web services; XML Schema describes the structure and contents of XML-based messages received and sent by Web services. > To bootstrap communication with a Web service, this specification defines three request-response message pairs to retrieve these three types of metadata: one retrieves the WS-Policy associated with the receiving endpoint or with a given target namespace, another retrieves either the WSDL associated with the receiving endpoint or with a given target namespace, and a third retrieves the XML Schema with a given target namespace. Together these messages allow efficient, incremental retrieval of a Web service?s metadata. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-496) Vote for WS-SecureConversation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-496?page=all ] Thomas Diesler updated JBWS-496: -------------------------------- Component/s: productization (was: jbossws-jaxws) (was: ws-security) > Vote for WS-SecureConversation > ------------------------------ > > Key: JBWS-496 > URL: http://jira.jboss.com/jira/browse/JBWS-496 > 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 WS-SecureConversation if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-secon/ > The Web Services Secure Conversation Language (WS-SecureConversation) is built on top of the WS-Security and WS-Policy models to provide secure communication between services. WS-Security focuses on the message authentication model but not a security context, and thus is subject several forms of security attacks. This specification defines mechanisms for establishing and sharing security contexts, and deriving keys from security contexts, to enable a secure conversation. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-500) Vote for WS-BusinessActivity

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-500?page=all ] Thomas Diesler updated JBWS-500: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-BusinessActivity > ---------------------------- > > Key: JBWS-500 > URL: http://jira.jboss.com/jira/browse/JBWS-500 > 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 WS-BusinessActivity if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-tx/ > This specification provides the definition of the business activity coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification. The specification defines two specific agreement coordination protocols for the business activity coordination type: BusinessAgreementWithParticipantCompletion and BusinessAgreementWithCoordinatorCompletion. Developers can use any or all of these protocols when building applications that require consistent agreement on the outcome of long-running distributed activities. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-329) Vote for WS-Resource

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-329?page=all ] Thomas Diesler updated JBWS-329: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-Resource > -------------------- > > Key: JBWS-329 > URL: http://jira.jboss.com/jira/browse/JBWS-329 > Project: JBoss Web Services > Issue Type: Feature Request > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-Resource if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/ws-resource/ > The Web Services Resource Framework defines a family of specifications for accessing stateful resources using Web services. It includes the WS-ResourceProperties, WS-ResourceLifetime, WS-BaseFaults, and WS-ServiceGroup specifications. The motivation for these new specifications is that while Web service implementations typically do not maintain state information during their interactions, their interfaces must frequently allow for the manipulation of state, that is, data values that persist across and evolve as a result of Web service interactions. For example, an online airline reservation system must maintain state concerning flight status, reservations made by specific customers, and the system itself: its current location, load, and performance. Web service interfaces that allow requestors to query flight status, make reservations, change reservation status, and manage the reservation system must necessarily provide access to this state. In the Web Services Resource Framework we model state as stateful resources and codify the relationship between Web services in terms of an implied resource pattern. -- 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, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2007