| Connecting to web services from a plugin [message #436507] |
Fri, 09 September 2005 21:09  |
Eclipse User |
|
|
|
Originally posted by: bdberry.us.ibm.com
I am trying to connect to web services that I have developed and
deployed in websphere. Any ideas what jar files I am supposed to
include to execute the proxy beans to connect to these services? I have
created the Java proxies using Rational Software Architect. I tried by
including runtime libraries webservices.jar and qname.jar. I keep
getting class not found exceptions and I add jars as appropriate. I end
up with like seven jars and then it starts giving me exceptions about a
class that is in webservices.jar that cannot be found even thought hat
one is included.
|
|
|
|
| Re: Connecting to web services from a plugin [message #436513 is a reply to message #436507] |
Sat, 10 September 2005 16:23  |
| Eclipse User |
|
|
|
Originally posted by: pdavis.airisen.net
Brian Berry wrote:
> I am trying to connect to web services that I have developed and
> deployed in websphere. Any ideas what jar files I am supposed to
> include to execute the proxy beans to connect to these services? I have
> created the Java proxies using Rational Software Architect. I tried by
> including runtime libraries webservices.jar and qname.jar. I keep
> getting class not found exceptions and I add jars as appropriate. I end
> up with like seven jars and then it starts giving me exceptions about a
> class that is in webservices.jar that cannot be found even thought hat
> one is included.
Brian,
I tried this a while ago (albeit from a swing application) and had a
terrible time of it. I did eventually get it to work by packaging most of
the jars in the IBM Web Services Development kit and some of the WebSphere
jars. The size of the resulting application, coupled with the very murky
licensing picture made me abandon this solution. As Chris says "connecting
to WAS is evil", if you're trying to use the IBM client tools.
I've had great success using Axis for a java client (RCP, Swing)instead of
the IBM client tools.
At a hight level, develop your web service within RSA as normal for the
service provider part. Then feed the generated WSDL (assuming you're
creating your service from a model bean) into the Axis
org.apache.axis.wsdl.WSDL2Java generator. The Axis WSDL2Java will generate
fully compatible client proxies, including the service locator and service
proxy, which you can drop into your RCP application.
In the long run, this may turn out to be a better option for an RCP app as
the Eclipse Web Tools project (also providing a Web Service toolkit) uses
Axis.
|
|
|
| Re: Connecting to web services from a plugin [message #436519 is a reply to message #436513] |
Sat, 10 September 2005 21:42 |
| Eclipse User |
|
|
|
Originally posted by: bdberry.us.ibm.com
javasOK wrote:
> Brian Berry wrote:
>
>
>>I am trying to connect to web services that I have developed and
>>deployed in websphere. Any ideas what jar files I am supposed to
>>include to execute the proxy beans to connect to these services? I have
>>created the Java proxies using Rational Software Architect. I tried by
>>including runtime libraries webservices.jar and qname.jar. I keep
>>getting class not found exceptions and I add jars as appropriate. I end
>>up with like seven jars and then it starts giving me exceptions about a
>>class that is in webservices.jar that cannot be found even thought hat
>>one is included.
>
>
> Brian,
>
> I tried this a while ago (albeit from a swing application) and had a
> terrible time of it. I did eventually get it to work by packaging most of
> the jars in the IBM Web Services Development kit and some of the WebSphere
> jars. The size of the resulting application, coupled with the very murky
> licensing picture made me abandon this solution. As Chris says "connecting
> to WAS is evil", if you're trying to use the IBM client tools.
>
> I've had great success using Axis for a java client (RCP, Swing)instead of
> the IBM client tools.
>
> At a hight level, develop your web service within RSA as normal for the
> service provider part. Then feed the generated WSDL (assuming you're
> creating your service from a model bean) into the Axis
> org.apache.axis.wsdl.WSDL2Java generator. The Axis WSDL2Java will generate
> fully compatible client proxies, including the service locator and service
> proxy, which you can drop into your RCP application.
>
> In the long run, this may turn out to be a better option for an RCP app as
> the Eclipse Web Tools project (also providing a Web Service toolkit) uses
> Axis.
>
Thank you so much! Even after trying what Chris had suggested I was
still unable to connect to the web services through my RCP app. after
about 20 minuts of setting up my project to use Apache Axis and
generating the proxy classes it worked like a charm. I wasted so much
time on that websphere stuff - I wish I went with Axis from the start.
This works great now.
|
|
|
Powered by
FUDForum. Page generated in 0.02149 seconds
] 
Search
Help
Register
Login
Home
