March 2009 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Error while using Wise Soap Client

by ashwindesikan

I asssume you are using eclipse, if so then do the following steps and you should able to add tools.jar to classpath 1. Open Preference dialog 2. choose java --> Installed JREs 3. Choose your preferred JRE and select edit 4. select the option Add External Jars and add to it tools.jar from your JDK's lib folder recycle your sever and you would see in the logs at bootup the classpath contains tools.jar View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220731#4220731 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220731

15 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Error while using Wise Soap Client

by jayadeva

Hi, I am also facing the same classpath problem [ERROR] com.sun.tools.javac.Main is not available in the classpath, requires Suns JDK version 5.0 or latter. Please let me know how did you resolved the same. Jayadeva View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220551#4220551 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220551

15 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Remoting 3 and HTTP client

by david.lloyd＠jboss.com

"richard.opalka(a)jboss.com" wrote : It's not clear to me what's going to happen with remoting? | Is it going to remove client side abstraction or is it going to change binary protocol in incompatible way so using it cross different AS versions is not an option anymore? | Do we need to remove remoting dependency from our client side? This is what's happening. Remoting 3 introduces a new API which is not compatible with Remoting 2. It also is introducing new protocols which are incompatible with the old ones, though a translation layer is possible and is in the works in order to allow some level of interoperability. As of right now, I'm targeting AS 5.1 to have both Remoting 2 and 3 in it, with Remoting 3 existing as a sort of tech preview. At some unspecified point in the future, all services (such as EJB3, invokers, etc) will have been migrated to 3 and Remoting 2 will disappear (API and all). At this stage, all clients should be using R3 (though it will still be possible to support R2 clients without having R2 exist on the server). The HTTP abstractions (client and server) which appeared in Remoting 2 are more of an abstraction leak than an API feature, which came about from the fact that all of Remoting was basically stuck into a single JAR with no distinction between API, SPI, and implementation. A similar abstraction is not going to appear in the Remoting 3 API because the interfaces therein pertain only to remote invocation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219315#4219315 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219315

15 years, 1 month

1
0
0 / 0

jbossws version for implementing username token

by CHALASANI, Aruna

Hello, I am working on jboss-4.0.4GA and jbossws1.0.4 to implement webservice security using username tokens. Is it possible to achieve this with jbossws1.0.4? Thanks. Regards, AC Our Story ... The Bupa Story Visit www.bupastory.com to find out who we are, where we've come from, what we're about and where we're going. Bupa House 15-19 Bloomsbury Way London WC1A 2BA Internet communications are not secure and therefore Bupa does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of Bupa. Bupa Insurance Limited, Bupa Health Assurance Limited, Bupa Insurance Services Limited and Goldsborough Estates Limited are authorised and regulated by the Financial Services Authority. For a list of Bupa's main UK trading companies visit www.bupa.co.uk/html/statements/trading_addresses.html

15 years, 1 month

2
1
0 / 0

[Design of JBoss Web Services] - Re: Remoting 3 and HTTP client

by timfox

JBoss Messaging 2.0 also uses Netty, including the HTTP servlet transport, which allows JMS traffic to be tunnelled over port 80 in any servlet container. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218962#4218962 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218962

15 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Remoting 3 and HTTP client

by alessio.soldano＠jboss.com

"trustin" wrote : Hi Alessio, | | Remoting 3.1 will have HTTP transport, although it's not going to be backward-compatible in wire-level. Release date is not sure yet unfortunately. | | As an alternative, I'd like to suggest you to try Netty HTTP codec - http://www.jboss.org/netty/ | | Check the HTTP client / server example in the documentation section - http://tinyurl.com/5w3fpb (HttpClient, HttpClientPipelineFactory, and HttpResponseHandler are all you need to see.) | | It's supposed to be very efficient in dealing with large number of concurrent HTTP connections thanks to the effectiveness and robustness of its core. Thanks Trustin, this is exactly the kind of suggestion I expected from you guys ;-) I'll try Netty first for sure. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218900#4218900 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218900

15 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Remoting 3 and HTTP client

by richard.opalka＠jboss.com

It's not clear to me what's going to happen with remoting? Is it going to remove client side abstraction or is it going to change binary protocol in incompatible way so using it cross different AS versions is not an option anymore? Do we need to remove remoting dependency from our client side? If we need to remove dependency on remoting and provide pluggible client transport layer then note that we have nontrivial dependencies on JBoss Remoting: * FastInfosetConnectionHTTP * JsonConnectionHTTP * SOAPProtocolConnectionHTTP * SOAPProtocolConnectionJMS i.e. new transport should allow us to do http(s) & jms messages exchange at least. We should also consider socket reuse (this is issue of our current implementation - many customers are complaining about it) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218887#4218887 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218887

15 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Remoting 3 and HTTP client

by trustin

Hi Alessio, Remoting 3.1 will have HTTP transport, although it's not going to be backward-compatible in wire-level. Release date is not sure yet unfortunately. As an alternative, I'd like to suggest you to try Netty HTTP codec - http://www.jboss.org/netty/ Check the HTTP client / server example in the documentation section - http://tinyurl.com/5w3fpb (HttpClient, HttpClientPipelineFactory, and HttpResponseHandler are all you need to see.) It's supposed to be very efficient in dealing with large number of concurrent HTTP connections thanks to the effectiveness and robustness of its core. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218873#4218873 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218873

15 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Remoting 3 and HTTP client

by alessio.soldano＠jboss.com

This is related to https://jira.jboss.org/jira/browse/JBWS-2554 . In few words, JBossWS will soon need to use other means for http client invocations, as Remoting is not going to provide this anymore. Perhaps this might be the chance for making the http client pluggable. Right now I'm thinking about using HTTPClient, any opinion? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218756#4218756 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218756

15 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Error while using Wise Soap Client

by ashwindesikan

Thanks Richard. I got this issue resolved. My classpath was wrong Regards Ashwin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218487#4218487 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218487

15 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev March 2009