Select the right operation metadata when using Dispatch
-------------------------------------------------------
Key: JBWS-2010
URL: http://jira.jboss.com/jira/browse/JBWS-2010
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: jbossws-native-2.0.3
Reporter: Alessio Soldano
Assigned To: Alessio Soldano
Inspite of the Common/ClientImpl …
[View More]deriving the operation metadata from the invoked method, the DispatchImpl doesn't even try to find out the operation metadata corresponding to the message that is going to be sent. For instance this may be a potential issues when using ws-security with custom target configuration.
--
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
[View Less]
Wrong fault handling with logical handlers
------------------------------------------
Key: JBWS-2308
URL: https://jira.jboss.org/jira/browse/JBWS-2308
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-metro
Affects Versions: jbossws-metro-3.0.3
Reporter: Alessio Soldano
We have some issue in fault/exception handling when logical handlers are used. …
[View More]The jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ClientLogicalOutboundHandleFaultFalseTest and jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ClientLogicalInboundHandleFaultFalseTest are failing.
Identify the testcase, reproduce in jbossws-metro testcase and fix.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
Support xml overrides for @PortComponent
----------------------------------------
Key: JBWS-1309
URL: http://jira.jboss.com/jira/browse/JBWS-1309
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jaxws
Reporter: Jason T. Greene
Fix For: jbossws-2.0.0
Similar to EJB3 annotations, we need to support an xml override for the PortComponent annotation. …
[View More]The information will then need to be pulled from the JBoss metadata.
--
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
[View Less]
Username Token JAAS integration
-------------------------------
Key: JBWS-2209
URL: http://jira.jboss.com/jira/browse/JBWS-2209
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: ws-security
Reporter: Alessio Soldano
Assigned To: Alessio Soldano
Ideally we would need the Metro stack to have the same degree of JAAS integration the native …
[View More]stack has (i.e. authentication and authorization delegated to JBoss Security).
--
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
[View Less]
Adding Java 5 Generics for Webservices
--------------------------------------
Key: JBWS-1444
URL: http://jira.jboss.com/jira/browse/JBWS-1444
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.3
Environment: All
Reporter: Olivier PEPIN
It would be really convinient to make jboss WS and jsr-181 support Generics in a Webservice …
[View More]interface.
ie:
@WebMethod
public ContentSet getContent()
{
...
}
with:
public class ContentSet<T>
{
T[] items;
....
....
}
On Jboss 4.0.5 (jboss-ws 1.0.3), the generated wsdl does not generate the correct types and the webservice dos not work.
Comment from Thomas Diesler: his is not yet supported. You could create a feature request 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
[View Less]
Provide client side WS-RM API
-----------------------------
Key: JBWS-2047
URL: http://jira.jboss.com/jira/browse/JBWS-2047
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
The client WS-RM api will enable users to:
* attach to not closed …
[View More]sequences
* to obtain sequence id so it can be used after client restart
* to pick up all not yet delivered response messages but already available in client RMStore
--
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
[View Less]
Which WSA annotations to use?
-----------------------------
Key: JBWS-2149
URL: http://jira.jboss.com/jira/browse/JBWS-2149
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Heiko Braun
There is for instance javax.xml.ws.addressing.Action and javax.xml.ws.Action. WSConsume generates the later, but the MetaData builder looks for the first one.
--
This message is …
[View More]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
[View Less]
Rewrite client side RM implementation to ensure QoS
---------------------------------------------------
Key: JBWS-2045
URL: http://jira.jboss.com/jira/browse/JBWS-2045
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
RM on client side must …
[View More]be recoverable from client restarts and clients must be able to attach to not closed sequences
--
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
[View Less]
Rewrite initial RM implementation to ensure HA and QoS
------------------------------------------------------
Key: JBWS-2048
URL: http://jira.jboss.com/jira/browse/JBWS-2048
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
We have to ensure …
[View More]HA and QoS to make RM production ready.
--
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
[View Less]