April 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1119) Add support for fault signing and encryption

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1119?page=all ] Thomas Diesler updated JBWS-1119: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-native-2.0.5) > Add support for fault signing and encryption > -------------------------------------------- > > Key: JBWS-1119 > URL: http://jira.jboss.com/jira/browse/JBWS-1119 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Assigned To: Alessio Soldano > Fix For: jbossws-3.x, jbossws-1.0.3 > > > Add the ability to sign faults. WS-Security faults, will of course be unsigned. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1188) Relax requirement for wsu:id for UsernameToken

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1188?page=all ] Thomas Diesler updated JBWS-1188: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-native-2.0.5) > Relax requirement for wsu:id for UsernameToken > ---------------------------------------------- > > Key: JBWS-1188 > URL: http://jira.jboss.com/jira/browse/JBWS-1188 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.3 > Reporter: Darran Lofthouse > Fix For: jbossws-3.x > > > The JBossWS UsernameToken implementation is mandating that the wsu:id attribute is present on incomming requests. > Some thirdparty web services stacks being used as clients to JBossWS do not send the ID so we are rejecting the request. Additionally we do not actually use the id anywhere anyway. > The requirement for the id should be relaxed. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1498) Hudson build fails under Windows

by Alejandro Guizar (JIRA)

Hudson build fails under Windows -------------------------------- Key: JBWS-1498 URL: http://jira.jboss.com/jira/browse/JBWS-1498 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Affects Versions: jbossws-1.2.0, jbossws-2.0.0 Environment: Windows XP Pro Reporter: Alejandro Guizar In target hudson-setup: <exec executable="basename" outputproperty="svn.basename"> <arg value="${svn.url}"/> </exec> <exec executable="dirname" outputproperty="svn.basedir.local"> <arg value="${basedir}"/> </exec> Neither basename nor dirname are standard Windows commands. Targets hudson-start and hudson-stop invoke script catalina.sh to start/stop the web server. This is non portable as well. -- 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

4
10
0 / 0

[JBoss JIRA] Created: (JBWS-1933) RPC/Encoded

by Darran Lofthouse (JIRA)

RPC/Encoded ----------- Key: JBWS-1933 URL: http://jira.jboss.com/jira/browse/JBWS-1933 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-2.0.2 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.3 The following describes how RPC/Encoded types should be identified: - For each element containing a value, the type of the value MUST be represented by at least one of the following conditions: (a) the containing element instance contains an xsi:type attribute, (b) the containing element instance is itself contained within an element containing a (possibly defaulted) SOAP-ENC:arrayType attribute or (c) or the name of the element bears a definite relation to the type, that type then determinable from a schema. JBossWS does not currently use the xsi:type on the types so stacks such as Axis are unable to identify the type inside the element which represents the operation name. -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-1839) Leverage WSI tools

by Heiko Braun (JIRA)

Leverage WSI tools ------------------ Key: JBWS-1839 URL: http://jira.jboss.com/jira/browse/JBWS-1839 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productivity Reporter: Heiko Braun These might be useful additions to the management console (Monitor) or the standalone tools (Analyzer) http://www.ws-i.org/deliverables/workinggroup.aspx?wg=testingtools http://www.ws-i.org/Testing/Tools/2005/06/WSI_Test_Java_Final_1.1.zip -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-1325) Add support for virtual-hosts for EJB2.1 endpoints

by Darran Lofthouse (JIRA)

Add support for virtual-hosts for EJB2.1 endpoints -------------------------------------------------- Key: JBWS-1325 URL: http://jira.jboss.com/jira/browse/JBWS-1325 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 Assigned To: Darran Lofthouse Fix For: jbossws-1.0.5 This will require a change to the jboss.xml deployment descriptor to allow this to be specified. -- 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

5
8
0 / 0

[JBoss JIRA] Updated: (JBWS-1161) Interop endpoints for MTOM

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1161?page=all ] Thomas Diesler updated JBWS-1161: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-native-2.0.5) > Interop endpoints for MTOM > -------------------------- > > Key: JBWS-1161 > URL: http://jira.jboss.com/jira/browse/JBWS-1161 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-3.x > > > http://131.107.72.15/ilab/Messaging/WCFInteropPlugFest_Messaging.doc -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-981) Virtual host configuration for EJB endpoints

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-981?page=all ] Thomas Diesler updated JBWS-981: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-native-2.0.5) > Virtual host configuration for EJB endpoints > -------------------------------------------- > > Key: JBWS-981 > URL: http://jira.jboss.com/jira/browse/JBWS-981 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > > I use JBoss 4.0.4 GA and want to deploy a EJB3 (JSR-181) webserivce. Nearly everything is fine. The problem is that the generated servlet of the webservice is deployed on the default virtual host, but I want to change this to another. How is this possible? I tried to add an jboss-web.xml in META-INF directory of the jar-file containing the webservice bean and interface, but with no success. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-939) Allow setting of SSL and authentication properties for retrieving remote WSDL files

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-939?page=all ] Thomas Diesler updated JBWS-939: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-native-2.0.5) > Allow setting of SSL and authentication properties for retrieving remote WSDL files > ----------------------------------------------------------------------------------- > > Key: JBWS-939 > URL: http://jira.jboss.com/jira/browse/JBWS-939 > 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 > > > Currently only system properties can be used. A possible solution is to enhance our proprietary service factory API. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1849) Provide API to clean up MTOM attachments

by Magesh Kumar B (JIRA)

Provide API to clean up MTOM attachments ---------------------------------------- Key: JBWS-1849 URL: http://jira.jboss.com/jira/browse/JBWS-1849 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws Affects Versions: jbossws-1.2.0.SP1 Environment: Windows Reporter: Magesh Kumar B Priority: Optional When using MTOM with attachments, the temp files created using SwapableMemoryDataSource are not deleted in Windows environment. This is due to a problem in Windows and an outstanding bug in Java too contributes to it. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4171239 It would be nice to have an API that can be explicity called to delete these temp files created as part of MTOM requests. -- 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

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2008