You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by srinivas_svn <sr...@gmail.com> on 2010/04/30 15:54:25 UTC

Using CXF library files

Hi Everyone,

I am to new CXF, In Apache CXF website samples applications, I noticed that
many jar to add to develop 
new webservice. Is there any to avoid using those many jars.


Thanks

-- 
View this message in context: http://old.nabble.com/Using-CXF-library-files-tp28412496p28412496.html
Sent from the cxf-user mailing list archive at Nabble.com.


Re: Using CXF library files

Posted by conficio <Ka...@Conficio.com>.

srinivas_svn wrote:
> 
> Is there any to avoid using those many jars.
> 

Yes, use JRE 1.6 (or newer) and add to the classpath the dir, as dir/* ,
where all those jars are in. Java 6 (1.6) does understand to look for jars
within the directory.



> As a special convenience, a class path element containing a basename of * 
> is considered equivalent to specifying a list of all the files in the
> directory with the extension .jar or .JAR.
> 
> For example, if directory foo contains a.jar and b.JAR, then the class
> path element foo/* is expanded to A.jar;b.JAR, except that the order of
> jar files is unspecified. 
> 
from http://java.sun.com/javase/6/docs/technotes/tools/windows/javac.html

K<o>
-- 
View this message in context: http://old.nabble.com/Using-CXF-library-files-tp28412496p28413599.html
Sent from the cxf-user mailing list archive at Nabble.com.


Re: Using CXF library files

Posted by Daniel Kulp <dk...@apache.org>.
On Friday 30 April 2010 9:54:25 am srinivas_svn wrote:
> Hi Everyone,
> 
> I am to new CXF, In Apache CXF website samples applications, I noticed that
> many jar to add to develop
> new webservice. Is there any to avoid using those many jars.

In the "lib" dir of the CXF distribution, there is a "WHICH_JARS" file that 
describes which jars are required for which features.   Using that info, you 
can pair it down quite a bit.

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog