[jbpm-issues] [JBoss JIRA] Updated: (JBPM-2989) Overrding JobExecutor not possible in another package name, due to method visibilities

Fri Jan 14 11:29:49 EST 2011

     [ https://issues.jboss.org/browse/JBPM-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kris Verlaenen updated JBPM-2989:
---------------------------------

    Fix Version/s: jBPM 3.2.x


> Overrding JobExecutor not possible in another package name, due to method visibilities
> --------------------------------------------------------------------------------------
>
>                 Key: JBPM-2989
>                 URL: https://issues.jboss.org/browse/JBPM-2989
>             Project: jBPM
>          Issue Type: Enhancement
>          Components: Runtime Engine
>    Affects Versions: jBPM 3.2.9
>            Reporter: Mathieu Ruellan
>            Priority: Minor
>             Fix For: jBPM 3.2.x
>
>
> Since the new JobExecutor modifications, it's more difficult to override methods to integrate spring's transaction manager. 
> See (http://community.jboss.org/nfm/redirectToCSForum.jspa?module=bb&op=viewtopic&p=4250508#4250508)
> At the moment, the custom parent classes must be in the same package, that's ugly ...
> That can be more elegant if  methods bellow have a protected visibility:
> startLockMonitorThread
> getLockMonitorThreadName
> createThread

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira