November 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1639) Document usage on the wiki

by Thomas Diesler (JIRA)

Document usage on the wiki -------------------------- Key: JBWS-1639 URL: http://jira.jboss.com/jira/browse/JBWS-1639 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-1726) Modularize MetaDataBuilder

by Thomas Diesler (JIRA)

Modularize MetaDataBuilder -------------------------- Key: JBWS-1726 URL: http://jira.jboss.com/jira/browse/JBWS-1726 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws Reporter: Thomas Diesler Fix For: jbossws-2.1.0 Especially, revisit 'toolMode'. Is that really needed? The return below is questionable // The server must always generate WSDL if (generateWsdl || !toolMode) processOrGenerateWSDL(seiClass, serviceMetaData, result.wsdlLocation, sepMetaData); // No need to process endpoint items if we are in tool mode if (toolMode) return sepMetaData; // Sanity check: read the generated WSDL and initialize the schema model // Note, this should no longer be needed, look into removing it WSDLDefinitions wsdlDefinitions = serviceMetaData.getWsdlDefinitions(); JBossXSModel schemaModel = WSDLUtils.getSchemaModel(wsdlDefinitions.getWsdlTypes()); serviceMetaData.getTypesMetaData().setSchemaModel(schemaModel); -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-1637) Provide samples for atomic transaction

by Thomas Diesler (JIRA)

Provide samples for atomic transaction -------------------------------------- Key: JBWS-1637 URL: http://jira.jboss.com/jira/browse/JBWS-1637 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-1634) WS-SecurityPolicy

by Stefano Maestri (JIRA)

WS-SecurityPolicy ----------------- Key: JBWS-1634 URL: http://jira.jboss.com/jira/browse/JBWS-1634 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxws Reporter: Stefano Maestri Assigned To: Stefano Maestri Provide a Policy assertion compatible with ws-SecurityPolicy 1.2 specs. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1638) Provide samples for business activity

by Thomas Diesler (JIRA)

Provide samples for business activity ------------------------------------- Key: JBWS-1638 URL: http://jira.jboss.com/jira/browse/JBWS-1638 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-1395) Add a Standard All Client Configuration to standard-jbossws-client-config.xml

by John Gilbert (JIRA)

Add a Standard All Client Configuration to standard-jbossws-client-config.xml ----------------------------------------------------------------------------- Key: JBWS-1395 URL: http://jira.jboss.com/jira/browse/JBWS-1395 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxws Reporter: John Gilbert Priority: Trivial It would be nice to have this in addition to Standard Client, Standard Secure Client, and Standard Addressing Client, so that all clients don't have to create their config file. <client-config> <config-name>Standard All Client</config-name> <post-handler-chain> <handler-chain-name>PostHandlerChain</handler-chain-name> <handler> <j2ee:handler-name>WSSecurityHandlerOutbound</j2ee:handler-name> <j2ee:handler-class>org.jboss.ws.wsse.WSSecurityHandlerOutbound</j2ee:handler-class> </handler> <handler> <j2ee:handler-name>SOAPClientHandler</j2ee:handler-name> <j2ee:handler-class>org.jboss.ws.addressing.soap.SOAPClientHandler</j2ee:handler-class> </handler> </post-handler-chain> </client-config> -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1865) Unify SOAP message trace

by Heiko Braun (JIRA)

Unify SOAP message trace ------------------------ Key: JBWS-1865 URL: http://jira.jboss.com/jira/browse/JBWS-1865 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productivity Reporter: Heiko Braun Fix For: jbossws-2.1.0 Message trace should work the same way across stacks -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1633) Provide configuration of ws-security ad policy assertion

by Stefano Maestri (JIRA)

Provide configuration of ws-security ad policy assertion -------------------------------------------------------- Key: JBWS-1633 URL: http://jira.jboss.com/jira/browse/JBWS-1633 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxws Reporter: Stefano Maestri Assigned To: Stefano Maestri Fix For: jbossws-2.1.0 The goal is to provide a policy assertion implementation using jboss-ws-security_1_0.xsd schema. The policy will be equivalent to actual external file. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1664) Add support for external policy attachment

by Alessio Soldano (JIRA)

Add support for external policy attachment ------------------------------------------ Key: JBWS-1664 URL: http://jira.jboss.com/jira/browse/JBWS-1664 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-policy Reporter: Alessio Soldano Assigned To: Alessio Soldano Priority: Minor Fix For: jbossws-2.1.0 WS-Policy Attachment specs, chapter 3.4 on external policy attachment: "This mechanism allows Policies to be associated with a Policy Subject independent of that subject's definition and/or representation through the use of a <wsp:PolicyAttachment> element. This element has three components: the Policy Scope of the attachment, the Policy Expressions being bound, and optional security information. The Policy Scope of the attachment is defined using one or more extensible domain expressions that identify Policy Subjects, typically using URIs. [...]" This is supposed to use WS-Addressing to deal with policy scopes. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1471) Remove unwated tomcat excludes

by Thomas Diesler (JIRA)

Remove unwated tomcat excludes ------------------------------ Key: JBWS-1471 URL: http://jira.jboss.com/jira/browse/JBWS-1471 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.0 # TODO: Why are these excluded org/jboss/test/ws/jaxws/samples/wseventing/** org/jboss/test/ws/jaxrpc/samples/wssecurity/StorePassEncryptTestCase.* -- 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, 10 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2007