November 2006 - jbossws-users - Jboss List Archives

[JBossWS] - Re: Problems returning arrays from Webservice Method

by thomas.diesler＠jboss.com

For this fix not to get lost we'll need a jira issue with the patch + test case (modificatipon) attached. cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986342#3986342 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986342

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Problem with SAAJ Client for Webservice that receives at

by thomas.diesler＠jboss.com

Could you please create a jira issue and attach a patch against the 1.0.4 testsuite that allows us to reproduce this issue. cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986341#3986341 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986341

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: ws-addressing and jsr-109

by thomas.diesler＠jboss.com

there are wsa tests for jaxrpc in the testsuite View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986339#3986339 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986339

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Simple Problem ? - SOAPBody.addDocument()

by thomas.diesler＠jboss.com

You can also create the message directly from the request string View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986337#3986337 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986337

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Ejb3 JMSTransportSupport

by jgilbert

one thing that is not right with this approach is that there is no jms address in the wsdl, because only the SLSB is deployed as a web service. any thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986336#3986336 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986336

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Encryption and Signature from .Net client

by thomas.diesler＠jboss.com

anonymous wrote : | I'm afraid that I don't get this fixed I'm gonna have to transfer our complete system to another application server or throw the complete ws-security stack of jboss overboard and implement the security handler myself from scratch tailored to what the .Net client is sending out. | http://www.jboss.com/services/profsupport Currently the dev team is busy with JAXWS JEE5 certification. This type of interop issue will be addressed as part of the regular MSFT interop workshops. If cost is a concern to your organization, then profsupport might be a valid option. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986335#3986335 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986335

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Ejb3 JMSTransportSupport

by thomas.diesler＠jboss.com

Thanks, this work should be done against jbossws/trunk and should go into jbossws-2.0.0. Maybe you could create a jira issue and attach a patch against jbossws-2.0.0.CR1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986334#3986334 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986334

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Ejb3 JMSTransportSupport

by jgilbert

This could be handle generically without writing code. Just define the mdb in the deployment descriptor with an env-entry for the real service. <enterprise-beans> | <message-driven> | <ejb-name>AuthorizationCallbackMDB</ejb-name> | <ejb-class> | org.jboss.webservice.transport.jms.JMSTransportSupport | </ejb-class> | <messaging-type>javax.jms.MessageListener</messaging-type> | <transaction-type>Container</transaction-type> | <message-destination-type>javax.jms.Queue</message-destination-type> | </message-driven> | <env-entry> | <env-entry-name>serviceName</env-entry-name> | <env-entry-type>String</env-entry-type> | <env-entry-value>AuthorizationCallbackServiceMockBean</env-entry-value> | </env-entry> | </enterprise-beans> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986251#3986251 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986251

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Ejb3 JMSTransportSupport

by jgilbert

I extended JMSTransportSupport and overrode processSOAPMessage() to get something to work with Ejb3 MDBs. For starters the the WebService is implements per usual as a SLSB. I am just using the MDB as an alternate path in the WebService. The MDB just defines the ObjectName for the real web service. | @MessageDriven(activationConfig = {...}) | public class AuthorizationCallbackMDB extends MyJmsTransportSupport implements | MessageListener { | ObjectName getObjectName() { | try { | return new ObjectName( | "jboss.ws:context=payment-authorizer-0,endpoint=AuthorizationCallbackServiceMockBean"); | } catch (Exception e) { | throw new RuntimeException(e); | } | } | } | | public abstract class MyJmsTransportSupport extends JMSTransportSupport { | | private static final long serialVersionUID = 1L; | | abstract ObjectName getObjectName(); | | protected SOAPMessage processSOAPMessage(String fromName, | InputStream reqMessage) throws SOAPException, IOException, | RemoteException { | try { | ServiceEndpointManagerFactory factory = ServiceEndpointManagerFactory | .getInstance(); | ServiceEndpointManager epManager = factory | .getServiceEndpointManager(); | ServiceEndpoint sep = epManager | .getServiceEndpointByID(getObjectName()); | return sep.handleRequest(null, null, reqMessage); | } catch (BindingException ex) { | throw new WSException("Cannot bind incomming soap message", ex); | } | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986246#3986246 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986246

18 years, 2 months

1
0
0 / 0

[JBossWS] - jbossws-1.0.4.GA released

by thomas.diesler＠jboss.com

As of this post I am happy to anounce that jbossws-1.0.4.GA is released. It is a drop in replacement for jbossws-1.0.x.GA in JBossAS-4.0.4.GA and also works in standalone Tomcat. This allows you to develop standard portable J2EE1.4 web service endpoints in Tomcat that can be deployed to JBoss whenever full app server support is required. http://labs.jboss.org/file-access/default/members/jbossws/downloads/Insta... http://labs.jboss.com/portal/jbossws/user-guide/en/html/installation.html What's new ---------- * [JBWS-660] XOP inline base64Binary and sign message * [JBWS-779] Add webservices.xml support to wsdlTojava * [JBWS-868] BPEL in jbossws-samples * [JBWS-1113] Improve performance of Service.getPort() * [JBWS-1178] Multiple virtual host and soap:address problem * [JBWS-1182] Change wsdl-java@file to wsdl-java@location * [JBWS-1200] Provide source download for GA release * [JBWS-1261] Provide support for additional MTOM java types besides byte[] * [JBWS-1299] Add support for wsdl-java@parameter-style * [JBWS-1302] Use EAR name in context root for EJB endpoints * [JBWS-1323] Add JBoss EULA * Bug fixes For details see the change log. http://jira.jboss.com/jira/browse/JBWS?report=com.atlassian.jira.plugin.s... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986216#3986216 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986216

18 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users November 2006