🚀 go-pugleaf

roymcbrayer <roymcbrayer@austin.rr.com> wrote:

> I guess I am missing the big picture here.  If the archive excludes
> the libraries, then what function do libraries server.  Do I need to
> set up a directory structure on the application machine that includes
> the library files.  This is not just directed to IPWorks.  I have had
> the same problem every time I try to deploy third party class files.
> Source files are no problem but class files are not found.  What do I
> do with the class files included in the library if they are not included
> in the archive builder?

The archive builder excludes required library classes IF that is how
the properties for those libraries are set.  If you changed that 
property, then it should include whatever the property says.

That said, it's still possible the archive builder can miss spotting
dependencies that are computed at runtime.  It recognizes things
like Class.forName("package.class") but it can't handle variable
references.  

If the resulting jar is missing classes you want contained, and the
properties for the library are set properly, then it's probably another
dynamic dependency.  If those items are private and you can't define
fields for them, you need to either bundle that jar with your app
and put it on the app's classpath, or cheat and create a class in
that jar's namespace and create fields that way.

I suspect IP*Works may have done this to make unlicensed bundling
of their commercial product more difficult.


-- 
Joi Ellis (TeamB)               http://www.teamb.com/
No direct email, please.
For best results, post on news server newsgroups.borland.com!
Newsgroup Guidelines: http://www.borland.com/newsgroups/guide.html
Only posts which violate the rules in guide.html are subject to cancelation.