DCOM-231: Lifecycle-Callback MappingExceptions for abstract functions in PHP >=5.4.8 #539

Closed
doctrinebot opened this Issue Sep 26, 2013 · 4 comments

2 participants

@doctrinebot

Jira issue originally created by user kmohrf:

Hi,

i noticed that in PHP starting with Version 5.4.8 the ReflectionService implementations returns a different result for the hasPublicMethod function than in PHP <= 5.4.7 when called on an abstract function. This prevents me from defining a lifecycle callback on an abstract function for a mapped superclass.

I think that at least for mapped supperclasses it should be checked if the class and the function is abstract so it can be assumed that every extending class has this function and it is in fact callable.

The bug was introduced by a bugfix in PHP 5.4.8.

cheers

konrad

@doctrinebot

Comment created by kmohrf:

i’ve created a pull request to fix this issue. see #301

@doctrinebot

Comment created by kmohrf:

oh… and… this bug should probably be moved to common as it affects orm but is caused in common :)

@doctrinebot

Issue was closed with resolution "Fixed"

@doctrinebot

Comment created by @doctrinebot:

A related Github Pull-Request [GH-301] was closed:
#301

@doctrinebot doctrinebot added the Bug label Dec 6, 2015
@beberlei beberlei was assigned by doctrinebot Dec 6, 2015
@doctrinebot doctrinebot added this to the 2.4.2 milestone Dec 6, 2015
@doctrinebot doctrinebot closed this Dec 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment