Re: [Exist-development] Renaming the "lib" extension

[Dannes W. <da...@ex...>]

On Thu, Mar 25, 2010 at 11:31 AM, Evgeny Gazdovsky <gaz...@gm...> wrote:
> Simple add path EXIST_HOME/lib/private and put here the your private jars if you have one.

Sure you are right, but that is an implicit result of the changes.
Until now my jars were not exposed.


On Thu, Mar 25, 2010 at 11:39 AM, Evgeny Gazdovsky <gaz...@gm...> wrote:
> Old JNLP stuf have one hardcoded jnlp

sorry I refuse to say OLD jnlp code. IMO is the current and primary
interface, still. :-)


> and can give access to any core exist's jar.

But they do not right now...... hardcoded. If we want to expose
exist-db internal stuff (e.g. jars) it must be discussed, because of
the implicationsm, which are sometimes not directly visible.


> We need only some basic servlets like REST or XQueryServlet.

Maybe you are right. Maybe not. We decided to design it this way some
time ago, probably for good reasons. Any changes must be discussed and
agreed on. Realize that the way some parts are coded (direct in
servlets) is the most efficient way of IO to the outside world.


As I think more of it, probably we should not expose exist-db internal
jars. E.g.
(1) with all kind of signing issues which will appear (just as you saw
yesterday with fluent.jar). Maybe we should store these jars in the
database and have these exposed. With this, it is more easy to install
and upgrade your java based application (with the coming generic
packaging mechanisms)
(2) I fear of the maintenance penalties we'll get. I do not wanna test
all your apps if i decide to upgrade jars files (or add them to the
core)

D.

-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624