Allow configuration of secret key wrap algorithm
------------------------------------------------
Key: JBWS-1874
URL: http://jira.jboss.com/jira/browse/JBWS-1874
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: ws-security
Affects Versions: jbossws-2.0.1
Reporter: Alessio Soldano
Assigned To: Alessio Soldano
WCF wsse interoperability test 3.3 (November 2007) requires the mutual secret key to be wrapped with the RSA-OAEP algorithm. The current implementation always wraps the key with the RSA v1.5 algorithm (despite being able to unwrap using any algorithm). It should be possible to specify the key wrap algorithm in the wsse configuration files.
--
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
Disable HTTP chunking for J2ME client s
---------------------------------------
Key: JBWS-1381
URL: http://jira.jboss.com/jira/browse/JBWS-1381
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jaxrpc
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-1.0.5
How do I disable HTTP chunking for my EJB3 webservices?
I am using @WebMethod etc.
I need to disable HTTP chunking because my J2ME client (the wireless toolkit) can't handle chunking yet.
--
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
Investigate WS-Security with .NET 3.0
-------------------------------------
Key: JBWS-1730
URL: http://jira.jboss.com/jira/browse/JBWS-1730
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-jaxws
Reporter: Thomas Diesler
Fix For: jbossws-2.1.1
--
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
Read / write wsdl extensibility elements on portType/operation/input
---------------------------------------------------------------------
Key: JBWS-1632
URL: http://jira.jboss.com/jira/browse/JBWS-1632
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Alessio Soldano
Assigned To: Alessio Soldano
Priority: Minor
Implementation of WS-Policy (issue http://jira.jboss.org/jira/browse/JBWS-856 ) is going to provide marshal and unmarshal mechanism of wsdl extensibility elements (including policies and policy references) to/from the unified wsdl structure.
Extensibility elements on definitions/portType/operation/input are going to be ignored for now since processing them required some modifications to the unified wsdl structure; they are not to be ignored any more once this issue is solved.
--
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
Provide/Verify WS-PolicyAttachment implementation for UDDI
----------------------------------------------------------
Key: JBWS-1636
URL: http://jira.jboss.com/jira/browse/JBWS-1636
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Stefano Maestri
Priority: Minor
--
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
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
Use the ClientLauncher from the wsrunclient scripts in order to make @WebServiceRef work from standalone clients
-----------------------------------------------------------------------------------------------------------------
Key: JBWS-1695
URL: http://jira.jboss.com/jira/browse/JBWS-1695
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Heiko Braun
Fix For: jbossws-2.1.0
--
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
Investigate embedded JBossWS
----------------------------
Key: JBWS-1728
URL: http://jira.jboss.com/jira/browse/JBWS-1728
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-jaxws
Reporter: Thomas Diesler
Fix For: jbossws-2.1.1
Endpoint.deploy() should work with jdk1.6 and possibly Jetty
--
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