[ http://thecla.homeftp.net:8380/jira/browse/MISC-26?page=comments#action_11070 ] skabeat commented on MISC-26: -----------------------------
you're right after a quick look I saw that there is no need to "synchronize" session ejb methods. According to the spec: "An enterprise Bean must not use thread synchronization primitives to synchronize execution of multiple instances." "This rule is required to ensure consistent runtime semantics because while some EJB Containers may use a single JVM to execute all enterprise bean's instances, others may distribute the instances across multiple JVMs." "Synchronization would not work if the EJB Container distributed enterprise bean's instances across multiple JVMs." We might close this issue... ;-) > synchronized methods in <<Services>> > ------------------------------------ > > Key: MISC-26 > URL: http://thecla.homeftp.net:8380/jira/browse/MISC-26 > Project: Miscellaneous > Type: New Feature > Environment: any > Reporter: skabeat > Assignee: Wouter Zoons > > > add the possibility to have synchronized method in <<Services>> using the > 'concurrency' modifier -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://thecla.homeftp.net:8380/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-devel
