Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368514 - java.lang.NullPointerException at buildAttributeValue in AttributeTransformer resp. SELECT returns nothing
Summary: java.lang.NullPointerException at buildAttributeValue in AttributeTransformer...
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P2 major (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-13 03:39 EST by Marco Descher CLA
Modified: 2022-06-09 10:21 EDT (History)
2 users (show)

See Also:


Attachments
Entity where the described problem occurs (12.41 KB, text/plain)
2012-01-13 03:41 EST, Marco Descher CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Descher CLA 2012-01-13 03:39:57 EST
Build Identifier: 2.3.1.v20111018-r10243 AND 2.3.2

I have an entity which uses several convert methods etc. this all works fine within EclipseLink/OSGi in an Eclipse RCP environment when usign EclipseLink 2.3.0!

If I update to 2.3.1 or 2.3.2 however the SELECT statement does not seem to return anything, which leads to the NPE.

I already debugged and saw that the content of row in
public ContactType buildAttributeValue(Record row, Object object, Session session){

is empty for all columns! (Although there certainly is content in the database!)

-->
[EL Info]: 2012-01-13 09:38:04.985--ServerSession(1373539035)--elexis login successful
[EL Fine]: 2012-01-13 09:38:05.044--ServerSession(1373539035)--Connection(292624752)--SELECT ID, ALLERGIEN, ... FROM KONTAKT
[EL Warning]: 2012-01-13 09:38:05.065--UnitOfWork(1363346070)--java.lang.NullPointerException

Reproducible: Always

Steps to Reproduce:
1. Use enclosed class in a EclipseLink 2.3.0 environment ... be happy!
2. Update to EclipseLink 2.3.1 or 2.3.2
3. NPE, resp. no values returned from the select!
Comment 1 Marco Descher CLA 2012-01-13 03:41:59 EST
Created attachment 209436 [details]
Entity where the described problem occurs
Comment 2 Tom Ware CLA 2012-02-09 10:28:17 EST
Setting target and priority.  See the following page for the meanings of these fields:

http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines

Community: Please vote for this bug if it is important to you.  Votes are one of the main criteria we use to determine which bugs to fix next.
Comment 3 Andrei Ilitchev CLA 2012-04-02 16:53:24 EDT
Could you please provide a complete simple test case that reproduces the problem.

The attached entity uses lots of classes and has lots of attributes.
Would it be possible to trim it down to the simplest configuration which still could be used to reproduce the problem.
Also please include all the referenced classes.
A script to create and populate the db would be helpful, too.
Finally, the test itself; what exactly should be done to reproduce the problem.
Comment 4 Andrei Ilitchev CLA 2012-05-30 10:44:20 EDT
Need more information.
Retargeting for 2.4 and closing.
Please reopen if more information is available.
Comment 5 Eclipse Webmaster CLA 2022-06-09 10:21:56 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink