November 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1100) Move WS-Eventing to updated wsa schema

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1100?page=all ] Thomas Diesler updated JBWS-1100: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Move WS-Eventing to updated wsa schema > -------------------------------------- > > Key: JBWS-1100 > URL: http://jira.jboss.com/jira/browse/JBWS-1100 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-eventing > Affects Versions: jbossws-1.0.1 > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-1.0.6 > > > Currently eventing uses a customized wsa schema. It should use the public, updated addressing schema instead. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-869) JAXR in jbossws-samples

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-869?page=all ] Thomas Diesler updated JBWS-869: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > JAXR in jbossws-samples > ----------------------- > > Key: JBWS-869 > URL: http://jira.jboss.com/jira/browse/JBWS-869 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: documentation > Reporter: Thomas Diesler > Assigned To: Anil Saldhana > Fix For: jbossws-1.0.6 > > > The parent issue description: > The sample code in that chapter should be backed up by the standalone sample download. > ------------ > Every chapter in the userguide is backed up with one/more testcase in the jbossws testsuite. The tests are then compiled together in a standlaone sample zip. > Please show us how to use JAXR with some samples. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-429) Create Custom Holders for Custom types that define INOUT parameters and OUT parameters [WSDLToJava Subsystem]

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-429?page=all ] Thomas Diesler updated JBWS-429: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Create Custom Holders for Custom types that define INOUT parameters and OUT parameters [WSDLToJava Subsystem] > ------------------------------------------------------------------------------------------------------------- > > Key: JBWS-429 > URL: http://jira.jboss.com/jira/browse/JBWS-429 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: wstools > Reporter: Anil Saldhana > Fix For: jbossws-1.0.6 > > > WSDL 1.1 can define IN-OUT parameters and OUT. Then there is a need to generate Holders by the WSDLToJava component of JBossWS Tools. > Now if the type that defines an INOUT parameter, is a type that is NOT supported by standard Jax-RPC types, then custom holder classes need to be generated. > If the type is supported by Jax-RPC, then standard holders defined in the javax.xml.rpc.holders package can be used. Examples are ShortWrapperHolder, IntegerWrapperHolder, FloatWrapperHolder etc. > Custom Holders will be handled after the first release of wstools. If there is demand, I can raise the priority. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1116) Use HTTP port from HttpServletRequest for port rewriting

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1116?page=all ] Thomas Diesler updated JBWS-1116: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Use HTTP port from HttpServletRequest for port rewriting > -------------------------------------------------------- > > Key: JBWS-1116 > URL: http://jira.jboss.com/jira/browse/JBWS-1116 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.2 > Reporter: Jay Key > Fix For: jbossws-1.0.6 > > > Please consider using the IP address and port from the HttpServletRequest when rewriting the URL in published wsdl. This would work out-of-the box for 99.999% of all users without the need for configuration changes, and supports cases where JBoss is running behind a NAPT firewall or other proxy-tunnel. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-895) Provide support for policy attachments

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-895?page=all ] Thomas Diesler updated JBWS-895: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Provide support for policy attachments > -------------------------------------- > > Key: JBWS-895 > URL: http://jira.jboss.com/jira/browse/JBWS-895 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-1.0.6 > > > Web Services Policy Attachment (WS-PolicyAttachment), > defines two general-purpose mechanisms for associating policies with the subjects to > which they apply; the policies may be defined as part of existing metadata about the > subject or the policies may be defined independently and associated through an external > binding to the subject. > Relevant to JBossWS are the following questions: > - How to reference policies from WSDL definitions. > - How to associate policies with deployed Web service 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

18 years, 2 months

1
0
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-1.0.6 (was: jbossws-1.0.5) > 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-1.0.6 > > > 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1264) Update products page

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1264?page=all ] Thomas Diesler updated JBWS-1264: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Update products page > -------------------- > > Key: JBWS-1264 > URL: http://jira.jboss.com/jira/browse/JBWS-1264 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Heiko Braun > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.6 > > > http://www.jboss.org/products/jbossws -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-916) Implement javax.xml.rpc.session.maintain

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-916?page=all ] Thomas Diesler updated JBWS-916: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Implement javax.xml.rpc.session.maintain > ---------------------------------------- > > Key: JBWS-916 > URL: http://jira.jboss.com/jira/browse/JBWS-916 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Jason T. Greene > Fix For: jbossws-1.0.6 > > > JAX-RPC specifies a non-interoperable cookie based session mechanism that is controlled via the session.maintain property. > We should implement this since customers are using similar mechanisms in Axis. > We should also clearly document the interoperability problems with this approach. > -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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1202) Allow HttpSession timeout to be set of EJB endpoints.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1202?page=all ] Thomas Diesler updated JBWS-1202: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > Allow HttpSession timeout to be set of EJB endpoints. > ----------------------------------------------------- > > Key: JBWS-1202 > URL: http://jira.jboss.com/jira/browse/JBWS-1202 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.3 > Reporter: Darran Lofthouse > Fix For: jbossws-1.0.6 > > > Allow HttpSession timeout to be set of EJB endpoints, currently this can only be set for POJO endpoints as they already have a war. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-461) WS-Transaction section in user guide backed up by sample code

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-461?page=all ] Thomas Diesler updated JBWS-461: -------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) > WS-Transaction section in user guide backed up by sample code > ------------------------------------------------------------- > > Key: JBWS-461 > URL: http://jira.jboss.com/jira/browse/JBWS-461 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-transaction > Reporter: Thomas Diesler > Fix For: jbossws-1.0.6 > > > Integrate the Arjuna WS-Tx with JBossWS. > There should be a tests-transaction target in the jbossws testsuite. -- 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

18 years, 2 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 November 2006