I did a test and the result shows that ear containing war and jar doesn't work. I suspected that it is due to the context root confliction, because there is a jboss-app.xml and context.xml in the jbossportal core already.
What i did was to deploy jar file directly. Portlets in war use jndi lookup by using local-ejb-ref tag in the jboss-web.xml. It works. But there is a strange problem related to the classloader: If the war file includes the interface classes of the ejbs in its lib directory, there will be a classloader exception. But if i remove the ejbs interfaces from its lib directory, it works. In my understanding, i expected that the ejb interfaces should be included in the lib directory. Is this true? Regards Yang View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885457#3885457 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885457 ------------------------------------------------------- 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
