March 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2067) Breakup tools script for each stack

by Heiko Braun (JIRA)

Breakup tools script for each stack ----------------------------------- Key: JBWS-2067 URL: http://jira.jboss.com/jira/browse/JBWS-2067 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-3.0.2 We should have one script per stack and remove it from the framework codebase -- 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

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2086) Update AS5 container integration to work on EJB3 integration API only

by Heiko Braun (JIRA)

Update AS5 container integration to work on EJB3 integration API only --------------------------------------------------------------------- Key: JBWS-2086 URL: http://jira.jboss.com/jira/browse/JBWS-2086 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun -- 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

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2089) isXOPPackage() is returning an incorrect value

by David Boeren (JIRA)

isXOPPackage() is returning an incorrect value ---------------------------------------------- Key: JBWS-2089 URL: http://jira.jboss.com/jira/browse/JBWS-2089 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Reporter: David Boeren I am trying to pass an mtom/xop attachment on a webservice call, but the attachment is not being correctly received. When I step through the JbossWS code, it gets to the org.jboss.ws.extensions.xop.jaxws.AttachmentUnmarshallerImpl class. When the isXOPPackage() method is called, the return value is false, so the getAttachmentAsDataHandler() method never gets called. If I force the isXOPPackage() to return true, then getAttachmentAsDataHandler() is called, and I can see the attachment data in the web method. So, it looks as if there is a bug in isXOPPackage() which is preventing it from recognizing the attachment. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBWS-1714) CLONE - Verify correct bahaviour of @WebService.wsdlLocation

by Heiko Braun (JIRA)

CLONE - Verify correct bahaviour of @WebService.wsdlLocation ------------------------------------------------------------ Key: JBWS-1714 URL: http://jira.jboss.com/jira/browse/JBWS-1714 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Heiko Braun Assigned To: Thomas Diesler Fix For: jbossws-2.0.0 I get a wsdl now but it is not the one I defined in my wsdlLocation value in the endpoint interface in the wsdlLocation javax.jws.WebService annotation. I get datetime types set to anySimpleType and all my enumerations have camel case now like this - dropOffType - rather than DropOffType like in the wsdl. I believe a wsdl is being generated still. How do I generate and deploy a web service and have jboss use the wsdl I supply in the 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

16 years

4
11
0 / 0

[JBoss JIRA] Created: (JBWS-2083) EJB3 integration API for deployment and invocation handling

by Heiko Braun (JIRA)

EJB3 integration API for deployment and invocation handling ----------------------------------------------------------- Key: JBWS-2083 URL: http://jira.jboss.com/jira/browse/JBWS-2083 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-3.0.1 Further decouple WS from EJB3 implementation details. The associated forum thread covers the details. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBWS-2054) Unify access to client/server side features

by Thomas Diesler (JIRA)

Unify access to client/server side features ------------------------------------------- Key: JBWS-2054 URL: http://jira.jboss.com/jira/browse/JBWS-2054 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Fix For: jbossws-native-2.0.5 org.jboss.ws.metadata.config.EndpointFeature should go All feature/property functionality that can be set in the config should be made available via WebServiceFeature. The native code base should not have to query the config and the endpoint meta data seperately for a given feature. The standard MTOM WebServiceFeature should be supported. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBWS-2063) Complete FastInfoset data binding

by Thomas Diesler (JIRA)

Complete FastInfoset data binding ---------------------------------- Key: JBWS-2063 URL: http://jira.jboss.com/jira/browse/JBWS-2063 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Fix For: jbossws-native-2.0.5 -- 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
3
0 / 0

[JBoss JIRA] Created: (JBWS-2062) JSON message type

by Thomas Diesler (JIRA)

JSON message type ----------------- Key: JBWS-2062 URL: http://jira.jboss.com/jira/browse/JBWS-2062 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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
6
0 / 0

[JBoss JIRA] Created: (JBWS-2077) Provide JMS Binding in generated WSDL

by Thomas Diesler (JIRA)

Provide JMS Binding in generated WSDL -------------------------------------- Key: JBWS-2077 URL: http://jira.jboss.com/jira/browse/JBWS-2077 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Fix For: jbossws-3.x Currently, the client will have to use the JMS API directly InitialContext context = new InitialContext(); QueueConnectionFactory connectionFactory = (QueueConnectionFactory)context.lookup("ConnectionFactory"); Queue reqQueue = (Queue)context.lookup("queue/RequestQueue"); Queue resQueue = (Queue)context.lookup("queue/ResponseQueue"); QueueConnection con = connectionFactory.createQueueConnection(); QueueSession session = con.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); QueueReceiver receiver = session.createReceiver(resQueue); ResponseListener responseListener = new ResponseListener(); receiver.setMessageListener(responseListener); con.start(); TextMessage message = session.createTextMessage(reqMessage); message.setJMSReplyTo(resQueue); waitForResponse = true; QueueSender sender = session.createSender(reqQueue); sender.send(message); sender.close(); int timeout = 5000; while (waitForResponse && timeout > 0) { Thread.sleep(100); timeout -= 100; } assertNotNull("Expected response message", responseListener.resMessage); assertEquals(DOMUtils.parse(resMessage), DOMUtils.parse(responseListener.resMessage)); con.stop(); session.close(); con.close(); Instead, the client should use the standard JAX-WS API to consume a wsdl that defines the jms binding -- 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
4
0 / 0

[JBoss JIRA] Created: (JBWS-2059) Complete JSON data binding

by Thomas Diesler (JIRA)

Complete JSON data binding --------------------------- Key: JBWS-2059 URL: http://jira.jboss.com/jira/browse/JBWS-2059 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Fix For: jbossws-native-2.0.5 -- 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
3
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