I'm pasting the exact error message from weblogic weblogic.ejb20.compliance.ComplianceException: In EJB com.ascential.asb.service.test.greetingService.GreetingService, Enterprise Bean methods must not use thread synchronization primitives. The method named _setInstanceAdvisor(org.jboss.aop.InstanceAdvisor) is synchronized.
I was under the impression the spec restricted all public methods of the bean to not use the synchronized primitive and guess I'm wrong. But in any case would it not be equivalent to use some variable to synchronize on inside the body of the method ? Portability is quite high in our priorities and although we intensively use JBoss during development we end up with a lot of surprises when trying to port to weblogic or websphere. Websphere 5.1 does not complain about this issue but about something else which I'm still trying to figure out is exactly what ?? :-) Thanks Rajiv View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852989#3852989 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852989 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
