January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1547) WS-Policy integration support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1547?page=all ] Thomas Diesler updated JBWS-1547: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > WS-Policy integration support > ----------------------------- > > Key: JBWS-1547 > URL: http://jira.jboss.com/jira/browse/JBWS-1547 > 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: > If WSS 1.1 is used, use WS-policy and WS-security policy to allow interoperability. > WS-Policy is implemented in JBossWS 1.2; however, there is currently no way of using it. It is expected that WS-Policy support will be available in JBossWS 1.2.1 (See "JBWS-856" in JIRA). -- 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
0
0 / 0

[JBoss JIRA] Created: (JBWS-1635) Provide/Verify WS-PolicyAttachment implementation for all attachment point defined by specs

by Stefano Maestri (JIRA)

Provide/Verify WS-PolicyAttachment implementation for all attachment point defined by specs ------------------------------------------------------------------------------------------- Key: JBWS-1635 URL: http://jira.jboss.com/jira/browse/JBWS-1635 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stefano Maestri Assigned To: Stefano Maestri The first implementation just consider Port and EndPoint Level. Specs require also webservice, operation, input, message. -- 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

3
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] Updated: (JBWS-1128) Add provison to specify a JassSecurityDomain in WS-SECURITY config

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1128?page=all ] Thomas Diesler updated JBWS-1128: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Add provison to specify a JassSecurityDomain in WS-SECURITY config > ------------------------------------------------------------------ > > Key: JBWS-1128 > URL: http://jira.jboss.com/jira/browse/JBWS-1128 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.2 > Reporter: Magesh Kumar B > Priority: Optional > Fix For: jbossws-3.x > > > Ideally the existing SecurityStore and configuration will remain for doing per-deployment keystore configuration. > Optionally they should be able to refer to a JaasSecurityDomain, which would be globaly configured. This needs to be optional because we deploy against the mc, which is not necessarily jboss (could be tomcat). > -Jason -- 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
0
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] Updated: (JBWS-1551) NetBeans support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1551?page=all ] Thomas Diesler updated JBWS-1551: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > NetBeans support > ---------------- > > Key: JBWS-1551 > URL: http://jira.jboss.com/jira/browse/JBWS-1551 > 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 > > > Formally support NetBeans IDE for Java to WSDL and WSDL to Java. -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1596) Add support for ROOT contexts on EJB endpoints with JBoss/Tomcat

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1596?page=all ] Thomas Diesler updated JBWS-1596: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Add support for ROOT contexts on EJB endpoints with JBoss/Tomcat > ---------------------------------------------------------------- > > Key: JBWS-1596 > URL: http://jira.jboss.com/jira/browse/JBWS-1596 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Jason T. Greene > 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

16 years, 10 months

1
0
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-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] Updated: (JBWS-1567) Release jbossws for SOA platform

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1567?page=all ] Thomas Diesler updated JBWS-1567: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Release jbossws for SOA platform > -------------------------------- > > Key: JBWS-1567 > URL: http://jira.jboss.com/jira/browse/JBWS-1567 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > 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

16 years, 10 months

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