Thank you for your answer. anonymous wrote : "No resrouces are checked (but deployment descriptors and bean interfaces) an no bean is instanciated during deployment. " But if i instanceiate the class Symbol by Class.forName().newInstance() the deployment will stop with an error message, so there must be some kind of check.
anonymous wrote : "So this is not a classloader problem. Some resources are missing! Is the Symbol class available? Are all the resources/classes available Symbol needs when the classloader tries to load it (watch attributes and static initializers...) " The jar file is a standalone application which is working fine. There are no static initalizers in this class and its context. So there is no resource missing. anonymous wrote : "Do you really want to load classes in jboss out of your gui package / graphiceditor package? Rethink your assembly/deployment or packaging." No, i'am trying to migrate our standalone server application with a selfwritten service layer to jboss. This is only a prototype. Later on we do not use classes of the gui package. I wrote a sample application with the same configuration A.jar, B.jar and so on, and it works fine, but why? I don't know!! The problem occuring using the big jar and the will not occur. Do you have any other ideas what i can do or who i can ask? greetings sven View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860794#3860794 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860794 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
