Or perhaps several questions. I am working on an interface to STAF in a web application, written in Java and deployed on a GlassFish server. This works very well as such, but every time I make even the smallest change to the code, I have to re-deploy the application, and then GlassFish wants to load another instance of libJSTAF.so, which fails; and the only cure is to restart the GlassFish software. This means that it is incredibly frustrating to work with.
What do other people do? I would have imagined that one could tell the server to load JSTAF.jar and the shared library as part of its configuration, and that one could tell the IDE (I use NetBeans) to do the same, so I won't have to include JSTAF.so in the application package; after all, that is how things like JDBC works, more or less. Why is it that libJSTAF.so gets loaded when JSTAF.jar is included? Is there a way to avoid this? ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ staf-users mailing list staf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/staf-users
