"[EMAIL PROTECTED]" wrote : If we fall back to the "traditional" jboss view,
then:
|
| 1) Invoking on a template for copying static libs into ./lib is not the
best way. It'd be more straightforward to have on the DeploymentService
something like:
|
| | String[] listStaticLibs();
|
A view of the static libs is not an admin view. An admin may not even know that
a datasource has a jdbc driver jar. You have to make a distinction between a
package and the installation of that package. A package is a self contained
collection of descriptors, jars, os libs, etc. that needs to be
If we fall back to the "traditional" jboss view, then:
1) Invoking on a template for copying static libs into ./lib is not the best
way. It'd be more straightforward to have on the DeploymentService something
like:
| String[] listStaticLibs();
| boolean uploadStaticLib(URL url);
|
(This
Yes, this is the correct approach.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864243#3864243
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864243
---
This SF.
