[SOLVED] RTC webservice plugin consumer

I had to package the web service runtime jar files in the lib folder of the plugin so that they would be deployed into the plugin classpath.

 Hi All, 

 Thank you so much Sam. But I cannot understand the approach that you said, is manual or exist a file (plugin.xml or MANIFEST.MF), if this configuration is in some file where is the tab? I had tried many things but nothing works for me. So, let me explain better the scenarios:

 

a)      I have another plugin that package the webservice client (generated by eclipse). This second one has a dependency by the first one. Where this dependency was configured in dependencies tab of MANIFEST.MF file.

 

b)      I have a plugin that was created by existing jars, where this jars is necessaries to jax-rpc execution (axis.jar, commons-discovery-0.2.jar, javax.wsdl_1.6.2.v201012040545.jar, jaxrpc.jar, org.apache.commons.logging_1.0.4.v201101211617.jar, saaj.jar);

 

 

c)       The third one plugin is the main, who has the advisor class that extends AbstractService and implements IOperationAdvisor. So, just this one has a site project, the others just plugin and feature. Beyond, this project plugin has dependency for the others, and I configured the site project to expose feature and plugins for the all.

 

 

I am posting the files for help in this link: https://www.assembla.com/spaces/usdplugin/documents/cNdvok5yar4R7dacwqEsg8/download/cNdvok5yar4R7dacwqEsg8

 

Provision Status Log: http://www.heypasteit.com/clip/0VI5

 

Thanks a lot.

 Thanks a lot, one more time, for your help, sam. So I discovered another way to do it, where the approach is much easier and more helpful in our context. The approach is similar a shared labraries was concept and can be reused by others plugins that has this dependency as a requirement. Well, after read a lot of articles that gave me better understanding about plugins dependency I discovered three ways to do the same thing, where the first one is where I was doing without successful. The second one is the manner that Sam said. And the third one is the manner that is more convenient  in our case. This approach is so much simpler then others in my opinion because all do you want to do is edit just one file, turning the administration simple than other manners that you must edit many files, or many different parts always when some modification is necessary. And better, you can share the libs with other applications (plugins, advisors..) as necessary, where this libs will always stay in the same place, and not replicated for each one. By the way the solution dont care if you dependency is  another plugin or where it is placed, you just whant to write a line one MANIFEST.MF as below:

Bundle-ClassPath: .,

 external:C:/Users/Delljoaobosco/Desktop/lib.jar,

 external:C:/Users/Delljoaobosco/Desktop/usdclient.jar,

 external:C:/Users/Delljoaobosco/Desktop/com.ibm.ws.webservices.thinclient_7.0.0.jar