Bug #32466

Strange exception: Invalid annotation

Added by Daniel Ostmann over 3 years ago. Updated over 3 years ago.

Status:Resolved Start date:2011-12-12
Priority:Must have Due date:
Assigned To:Karsten Dambekalns % Done:

100%

Category:Reflection
Target version:TYPO3 Flow Base Distribution - 1.0.2
PHP Version:5.3 Complexity:
Has patch:No Affected Flow version:FLOW3 1.0.0

Description

On my localhost everything was fine. When i upload the framework to my server, i got this exception:

Uncaught Exception
  The @var annotation for
  "Pixelbrand\MemberManager\Domain\Model\Contribution::$created" seems to
  be invalid.

More Information
  Exception code      #1284132314
  File                /var/www/doms/cm.pixelbrand.biz/public_html/Packages/Framework/TYPO3.FLOW3/Classes/Reflection/ReflectionService.php line 1121
  Exception reference #201112120946518ea6d6

I tried different upload types (ASCII, binary, auto - i use FileZilla as FTP client), and i tried different linebreaks (NL,CR,both). Nothing works at all...

The lines that throw the exception are:

    /**
     * The created date
     * @var \DateTime
     */
    protected $created;

I got the same exception when i changed the annotation from DateTime to string or bool.

I think, if i remove this property, then the next one would throw another exception like above. I think so, because it is the first file in model directory and the first property in this model class.

This seems to be similar to #31087.

I'm using PHP5.3.8 with FLOW1.0.1 but this happened to 1.0.0 as well.


Related issues

related to TYPO3.Flow - Bug #31087: Uncaught Exception: invalid annotation Closed 2011-10-19
related to TYPO3.Flow - Bug #31363: Windows newline in annotation block throws exception Resolved 2011-10-27

Associated revisions

Revision 40af60c9
Added by Karsten Dambekalns over 3 years ago

[BUGFIX] "Wrong" EOL characters break parsing of doc comments

When \r\n was used as EOL instead of just \n the parsed doc comments
would retain the \r which would cause confusing exceptions in some
cases later on.

Change-Id: I632ced42f1f337cb7546ed411bcfde2e92011c2e
Fixes: #31363
Related: #32466
Related: #31087
Releases: 1.0, 1.1

Revision 6ca1f9b2
Added by Karsten Dambekalns over 3 years ago

[BUGFIX] "Wrong" EOL characters break parsing of doc comments

When \r\n was used as EOL instead of just \n the parsed doc comments
would retain the \r which would cause confusing exceptions in some
cases later on.

Change-Id: I5210bb5308558640f7b1e567eaf9a184c1f5a2d5
Fixes: #31363
Related: #32466
Related: #31087
Releases: 1.0, 1.1

History

#1 Updated by Karsten Dambekalns over 3 years ago

  • Status changed from New to Accepted
  • Assigned To set to Karsten Dambekalns
  • Target version set to 1.0.2

#2 Updated by Karsten Dambekalns over 3 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

See #31363 for the fix.

Also available in: Atom PDF