Re: [wtp-releng] Orbitizing some WS bundles

[Chris Brealey <cbrealey@xxxxxxxxxx>]

David,
there were a couple reasons why we did
not attempt to jar up the plugins containing third-party jars. I'm fairly
sure the first of these was valid once upon a time (at least pre-OSGi).
Maybe it isn't a concern any more.
1. Resources from a jar (eg. "axis.jar")
within a jarred plugin (eg. "org.apache.axis_1.3.0.v200608161946.jar")
were not loadable by the plugin class loader.
2. Some of the third party jars, in
addition to forming part of the plugin runtime, are also copied as-is into
projects in the workspace (eg. "axis.jar").

If #1 is no longer the case, then jarred
plugins may be OK, though we may need to change the code where we copy
our third party jars.

Cheers - CB.

Chris Brealey
Senior Advisory Technical Manager, Rational Java Web Services, IBM Canada
Ltd.
D3-275, D3/ENX/8200/MKM, 8200 Warden Avenue, Markham, Ontario, Canada,
L6G 1C7
cbrealey@xxxxxxxxxx, 905.413.6038, tieline:969.6038, fax:905.413.4920

David M Williams <david_williams@xxxxxxxxxx>
Sent by: wtp-releng-bounces@xxxxxxxxxxx

03/26/2007 01:41 AM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	" wtp-releng" <wtp-releng@xxxxxxxxxxx>
cc
Subject	[wtp-releng] Orbitizing some WS bundles

One thing I'll be doing this week is putting some of our WS third party
jars in Orbit. 

It appears we have never "jarred" these bundles? Does anyone
know why? 
Is there a known reason we can not? 

Unless I hear otherwise, I do plan to (leave) them jarred up, so let me
know 
if that's not a good idea (and ... test well, once in builds). 

org.apache.commons.logging 
org.apache.axis 
org.apache.jakarta_log4j 
org.apache.wsil4j 
org.uddi4j 
org.wsdl4j 

_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng