March 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1672) SunRI does not respect @HandlerChain on client SEI

by Thomas Diesler (JIRA)

SunRI does not respect @HandlerChain on client SEI -------------------------------------------------- Key: JBWS-1672 URL: http://jira.jboss.com/jira/browse/JBWS-1672 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Fix For: jbossws-2.1.0 tests-run-internal: [junit] Running org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase [junit] FIXME: [JBWS-1671] SunRI client handler cannot set mime header [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 4.209 sec [junit] Test org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase FAILED @WebService(name="Endpoint") @SOAPBinding(style = SOAPBinding.Style.RPC) @HandlerChain(file = "jaxws-handlers-client.xml") // relative path from the class file public interface EndpointWithHandlerChain { public String echo(String input); } -- 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

14 years, 9 months

4
12
0 / 0

[JBoss JIRA] Created: (JBWS-2021) app-client with client and server not sharing the same filesystem

by Alessio Soldano (JIRA)

app-client with client and server not sharing the same filesystem ----------------------------------------------------------------- Key: JBWS-2021 URL: http://jira.jboss.com/jira/browse/JBWS-2021 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assigned To: Alessio Soldano Fix For: jbossws-native-2.0.5 Some jax-rpc tests using app-client were failing due to JBVFS-17. This however pointed out that our current implementation for app-client is supposed to work only when server and client share the same filesystem (see the referenced forum thread). We should think about something like a buffering virtual file implementation that eagerly reads the referenced resources from the file system before the metadata it is contained in is bound to the JNDI. -- 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

14 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2010) Select the right operation metadata when using Dispatch

by Alessio Soldano (JIRA)

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

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-1309) Support xml overrides for @PortComponent

by Jason T. Greene (JIRA)

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. 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

14 years, 10 months

7
22
0 / 0

[JBoss JIRA] Created: (JBWS-1444) Adding Java 5 Generics for Webservices

by Olivier PEPIN (JIRA)

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

14 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2047) Provide client side WS-RM API

by Richard Opalka (JIRA)

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

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2045) Rewrite client side RM implementation to ensure QoS

by Richard Opalka (JIRA)

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

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2048) Rewrite initial RM implementation to ensure HA and QoS

by Richard Opalka (JIRA)

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

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2041) Rewrite RMDeploymentAspect

by Richard Opalka (JIRA)

Rewrite RMDeploymentAspect -------------------------- Key: JBWS-2041 URL: http://jira.jboss.com/jira/browse/JBWS-2041 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 RMDeploymentAspect: * will de/register endpoint with RMProxy * will provide QoS policy description to be ensured by RMProxy -- 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

14 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-2043) Refactor server side RM handler to be used by RMReceiver

by Richard Opalka (JIRA)

Refactor server side RM handler to be used by RMReceiver -------------------------------------------------------- Key: JBWS-2043 URL: http://jira.jboss.com/jira/browse/JBWS-2043 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 RMServerHandler: * will be refactored to behave like message Filter * will be used by RMReceiver -- 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

14 years, 11 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2008