openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2168) Do not go through LifeCycleEventManager overhead if the Entity has declared to be excluded
Date Mon, 02 Apr 2012 14:25:21 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244220#comment-13244220
] 

Kevin Sutter commented on OPENJPA-2168:
---------------------------------------

I decided I didn't like this approach...  Instead of relying on the <exclude-default-listeners/>
element, we could just check if our LifeCycleEventManager processing has been "activated"
or not.  For example, if no callbacks, listeners, or handlers have been registered with the
runtime, then we can make the fireEvent processing more efficient  by skipping the associated
overhead.  Once one of these callbacks, listeners, or handlers have been registered, then
we go back to our normal processing.  Just a simple boolean "activated" switch.
                
> Do not go through LifeCycleEventManager overhead if the Entity has declared to be excluded
> ------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2168
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2168
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: kernel, performance
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Kevin Sutter
>            Assignee: Kevin Sutter
>             Fix For: 2.3.0, 2.2.1
>
>
> If the <exclude-default-listener> element is specified in the orm.xml, then we
can skip the listener processing in our runtime.  This capability has been in the code previously,
I'm just moving it higher in the callstack to remove the overhead of the LEMManager earlier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message