"[EMAIL PROTECTED]" wrote : I am eager to see this deployment that works in jboss-4.0.1 and fails in jboss-4.0.2. | | Please create a jira issue and attach a sample deployment (with source) that shows your problem.
Ok... after hours of deploying and undeploying - and testing and what not... it came down to a classloader issue. Apparently, 4.0.2 was throwing this error because as I surmised earlier, one of the loaders was getting confused about the classes since I packaged the same class in both the web service war/ejb jar. I resolved this issue by using the Class-Path in the manifest files to point to one jar file in the .ear and *poof*, the application doesn't throw any errors anymore. I still found it interesting that 4.0.1, the application worked fine, then in 4.0.2, the application didn't. :P Now... all I have to figure out is when I make a call to a local home interface of a session bean... it's taking like 17 seconds, when on 4.0.1, the call took like 2 seconds. =/ Anyone else seen this? :P _Ryan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882183#3882183 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882183 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
