Jaikiran,
Thank you, I tried this before, not via jboss-service.xml but by adding the classpath on the command line.
This way I get different errors. For external jars any dependent Jar is loaded also from the external repository, instead from the JBoss installation. If not found external, it throws an error. For example it loads commons-fileupload.jar from the external directory because this is also contained there. I then get NoClassDefFoundError or ClassNotFound because other jars needed in my app are not in the external directory but in my JBoss installation.
java.lang.NoClassDefFoundError: javax/portlet/ActionRequest
at org.apache.commons.fileupload.portlet.PortletRequestContext.getContentType(PortletRequestContext.java:73)
at org.apache.commons.fileupload.FileUploadBase$FileItemIteratorImpl.<init>(FileUploadBase.java:882)
...
portlet.jar and commons-fileupload.jar are contained in server\default\lib, but JBoss does not find portlet.jar because commons-fileupload.jar is loaded from the external jar repository. Any dependent jar specified on the command line must also be in the external repository. I need a way that JBoss looks for dependent jars in the JBoss installation first, if there is a dependency.
Thank you
Hubert
P.S.
And this way I will probably get in trouble if I have (what I do) wars of other vendors which contain different versions of the jars that I currently use.