This problem with class visibility between subpackages of an ear should be fixed in cvs now (not in the beta release from 2-21-2002). The sample ear you sent works fine, as does a testcase.
Please check that it works with your full app. thanks david jencks On 2002.02.20 08:13:20 -0500 Stephen Davidson wrote: > Hi David. > > The first time, I started JBoss, and then Deployed my app. > > > There has been no run.log. How do I make it write to one? Cutting and > pasting my entire screen would be a bit of a nuisance, but I can if it > would help. I > have a large screen buffer... > > > >>>file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar > >>references URL > >>>file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/HRXSecurity.jar > >>which could not be opened, entry ignored > > > The HRXSecurity.jar file was deployed as 78.HRXSecurity.jar in the tmp > directory. It was never deployed into the deploy directory. The class > files were not > loaded until the servlet needed them, and then it failed. > > I made an ear file with only 3 EJB jars, and missing a large chunk of the > documentation. The fullblown ear file (not attached) is currently just > about 10MBs. > The Ear file can be made available for anyone interested. The attached > compressed text file was the output of the run. Your assistance in this > is greatly > appreciated. > > I am wondering if I should post this as a bug against JBoss? I kind of > need this working rapidly. Do you have any ideas on a work around? I am > not sure that > just copying the jar files in would work. > > Thanks, > Steve > > > David Jencks wrote: > > > On 2002.02.19 12:27:01 -0500 Stephen Davidson wrote: > > > >>Additional Details; > >>When I shut JBoss down and restarted, Ilots of errors occurred. > >> > > > > Does this mean that JBoss is acting inconsistently or that the first > time > > you started jboss and then deployed your app? > > > >>I have a couple of Jars that either have common base classes, or > >>everything else uses (or for some of the EJB-Jar files, both). > >>For instance, I have a HRXBaseEJB class that most of the EJB's in all > of > >>the jars extend, located in a jar HRXCommon.jar. It uses some EJBs > from > >>HRXSecurity.jar. Some of these EJBs extend HRXBaseEJB. > >> > >>So I set up Class-Path in the MANIFEST.MF files, with appropriate > >>settings for each EJB-Jar file. So far, so good, and generally works > in > >>Orion. (They have > >>some classloader issues that I seem to trigger with one or two of my > Jars > >>- they have open bug reports on them and workarounds are available). > >> > >>When the EAR file is unpacked, the Jar files have a number prepended > to > >>them, at random, so far as I can determine. This means that the Jar > >>files listed in the > >>MANIFEST.MF files DO NOT exist. For example, HRXCommon.jar is > renamed to > >>68.HRXCommon.jar on deployment. This is causing my application to > fail > >>to deploy. > >> > > > > I don't think you have much proof of the cause-effect relationship > here. > > Everything in your ear should be getting into the classloader system, > > however it is referenced in your manifests. > > > >>There are 12 EJB-Jar files currently, with about 130 EJBs currently > >>deployed, (will eventually be about 50 jars, with well over 500EJBs > >>total), so bundling > >>everything into one jar is not an option. > >> > >>How do I work-around/solve this? > >> > > > > some helpful things to do would be: > > -try to make a smaller, simpler example that fails > > -post the jboss log (preferably with the smaller, simpler example) > > -if you can, send me privately the (preferable simplified) ear and I > will > > take a look. > > > > david jencks > > > > > >>-Steve > >> > >><===Begin Sample Output===> > >>11:04:52,706 INFO [MainDeployer] Deploying: > >>>file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar > >>11:04:52,711 WARN [MainDeployer] The manifest entry in > >>>file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar > >>references URL > >>>file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/HRXSecurity.jar > >>which could not be opened, entry ignored > >>11:04:52,954 INFO [EJBDeployer] Deploying CodeTableEJB > >>11:04:53,882 ERROR [MainDeployer] could not deploy > >>>:file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar > >>java.lang.NoClassDefFoundError: com/hrnexus/security/shared/UserInterface > >> at java.lang.Class.getMethods0(Native Method) > >> at java.lang.Class.getMethods(Class.java:742) > >> at >org.jboss.ejb.StatefulSessionContainer.setupBeanMapping(StatefulSessionContainer.java:619) > >> at >org.jboss.ejb.StatefulSessionContainer.create(StatefulSessionContainer.java:200) > >> at org.jboss.ejb.Application.start(Application.java:223) > >> at org.jboss.ejb.EJBDeployer.deploy(EJBDeployer.java:459) > >> at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:457) > >> at >org.jboss.deployment.MainDeployer.deploySubPackages(MainDeployer.java:791) > >> at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:452) > >> at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:412) > >> at org.jboss.deployment.MainDeployer.scan(MainDeployer.java:271) > >> at org.jboss.deployment.MainDeployer.startService(MainDeployer.java:217) > >> at >org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:160) > >> at java.lang.reflect.Method.invoke(Native Method) > >> at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) > >> at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > >> at org.jboss.system.Server.<init>(Server.java:157) > >> at org.jboss.Main.boot(Main.java:263) > >> at org.jboss.Main.run(Main.java:48) > >> at java.lang.Thread.run(Thread.java:484) > >> > >>Stephen Davidson wrote: > >> > >> > >>>Greetings. > >>> > >>>I am trying to port an application from Orion to JBoss v3.0Beta. > >>> > >>>The Ear file is being read, and so far as I can tell, deployed (for > >>> > >>more > >> > >>>evidence, read on). > >>>The War file contained in the Ear file is definately being deployed, > as > >>> > >>>the static webpages and at least one of the servlets are active and > >>>available. > >>>The EJB-jar from the Ear file are listed, but their EJBs are not. > >>> > >>>There are no error messages or stack traces, but the EJB classes are > >>>never loaded by the JVM. > >>> > >>>The jboss.xml file for the EJB.jar files appear to be correct. And > the > >>> > >>>application is properly deployed on Orion. > >>> > >>>Suggestions? > >>> > >>>Thanks, > >>>Steve > >>> > >>> > >>>_______________________________________________ > >>>JBoss-user mailing list > >>>[EMAIL PROTECTED] > >>>https://lists.sourceforge.net/lists/listinfo/jboss-user > >>> > >>> > >> > >> > > > > -- > Stephen Davidson > Java Consultant > Delphi Consultants, LLC > http://www.delphis.com > Phone: 214-696-6224 x208 > > > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
