I am developing applications that use an native, shared library; I am using
NetBeans as the IDE tool, and deploy my apps to Glassfish. In Netbeans I have
to include the .jar file that encapsualtes the API for the shared library in
the project; unfortunately this means that every time I re-deploy, Glassfish
tries to load another instance of the native, shared library, and fails, so
in effect I have to restart Glassfish every time I make even the smallest
change. This is clearly not sustainable, and I don't believe that people who
develop J2EE apps haven't found a way around this issue.
To me it seems that one ought to be able to do the same as for JDBC drivers -
you load it as part of the Glassfish configuration, independently of any
application that wants to use it; and then you do the same in the IDE, so
that you can use the API without having to include it in your application.
So, the big questio in this forums is: how can I load my API into Glassfish,
without including it in the application that needs to use it?
--
[Message sent by forum member 'janpla']
View Post: http://forums.java.net/node/869657