In certain scenarios where transactions are controlled externally, e.g. Seam (JBPM-1135), Spring (JBPM-1130) and Portal (JBPM-1289), the DeleteJobsSynchronization is invoked after the Hibernate session closes, or isn't invoked at all.
While some Spring-specific fixes have been proposed in the forum, it'd be better to find a general solution. Why was the synchronization introduced in the first place? Can it be replaced with, say, a SaveOperation?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160651#4160651
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160651
Yes, making the deployments in a profile available to the runtime is a separate step. Just updating a profile does not imply that the current server view is going to change.
I understand what your saying about the getModifiedDeployments not behaving correctly for deployments added to the profile. Its the second PROBLEM you point out that needs to be addressed as the hasBeenModified call is just a VFS api.
Can you create a bug report for that for CR2.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160645#4160645
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160645
None of us remaining on the Remoting team (as far as I am aware) have enough experience with the JMX stuff to make an informed decision, let alone carry it out before CR1 (apart from the name, the JMX remoting implementation has little to do with JBoss Remoting as far as I can tell). If there's nobody else who is able/willing to take this code over, then I'd say we should just get rid of it, unless there's some value being added that I'm not aware of?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160635#4160635
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160635