Hi Stan, thanx for your answer. In meantime there is coming another question up. Is it also possible to configure it without using a SAR. "It" means, again I would like to isolate the EAR file from the application server and I would also like to access some global libraries.
My directory structure would then look like this: | mydeploy | -jboss-service.xml | -myear.ear | -META-INF | -jboss-app.xml | ... | Deployment is done by adding the directory mydeploy to the DeploymentScanner. The content of jboss-service.xml file looks like that: | <!DOCTYPE server PUBLIC "-//JBoss//DTD MBean Service 4.0//EN" | "http://www.jboss.org/j2ee/dtd/jboss-service_4_0.dtd";> | <server> | <loader-repository>dot.com:loader=jpi-jboss-iv-ejbs.ear | <loader-repository-config>java2ParentDelegation=false | </loader-repository-config> | </loader-repository> | <!-- this is just an example do not care that which library it is --> | <classpath | codebase="file:/C:/common/lib/" | archives="mycommon.jar"/> | | </server> The content of the file jboss-app.xml looks like this: | <!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN" | "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd";> | <jboss-app> | <loader-repository>dot.com:loader=jpi-jboss-iv-ejbs.ear | <loader-repository-config>java2ParentDelegation=false | </loader-repository-config> | </loader-repository> | </jboss-app> | This time I checked if the xml files are valid ;-)) Ok, during deployment I receive the following log messages | 14:24:07,203 WARN [DeploymentInfo] Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: dot.com:loader=jpi-jboss-iv-ejbs.earimjboss-service.xml, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false) | 14:24:07,243 INFO [EARDeployer] Init J2EE application: file:/C:/eplatform/ews/R_3.0/jboss-4.0/jpi-jboss-iv/deploy/mydeploy/jpi-jboss-iv.ear/ | 14:24:07,263 WARN [DeploymentInfo] Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: dot.com:loader=jpi-jboss-iv-ejbs.ear, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false) | 14:24:07,634 INFO [EjbModule] Deploying PropagatorTest | 14:24:08,535 INFO [EARDeployer] Started J2EE application: file:/C:/eplatform/ews/R_3.0/jboss-4.0/jpi-jboss-iv/deploy/mydeploy/jpi-jboss-iv.ear/ So it seems that it was not possible to declare the loader-repository by means of the jboss-service.xml. How can I declare it. Or is there another possibility of declaring a loader-repository for my ear file and in parallel accessing global libraries that do not have to be part of the ear. Regards Karin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863719#3863719 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863719 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
