The EJBProxyFactoryImpl related working is indeed insignificat. Webservices are well deployed even when this warning occurs.
As mentioned before, removing: <invoker-proxy-binding> session-webservice-invoker ... </invoker-proxy-binding> and multiple instances of: <invoker-proxy-binding-name>session-webservice-invoker</invoker-proxy-binding-name> from standardjboss.xml removes the warning. As for the IncompatibleClassChangeError that Merten (mesc) mentions. This is a result of incompatible axis.jar that is found in the jboss-net.sar deployment. It may also result an IllegalAccessException when trying to access a web service or its wsdl. Silmply remove jboss-net.sar from the "deploy" directory and restart jboss. I hope this helps. Cheers, Nir. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844795#3844795 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844795 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
