-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The class does not have a descriptor, or a descriptor that does not use inheritance or uses a ClassExtractor for inheritance #966
Comments
Bump, because it is always reproduceable and is a blocker (I cannot change database layout). |
Hi, sorry for the delay! We haven't forgotten about this issue, we're just in a particularly busy time of the year at the moment. Do you have a simple reproducer we could use to help speed things up? |
Okay, maybe I can write some, my posting may contain a basic one. Just add a few properties (class fields) to the abstract POJO and let it persist. Then implement an EJB with a named query with TYPE(someAliasOrBean) = :somePlaceholder and you should get the same message. Oh, I have one more (other) bug in the pipeline. |
Thanks, that would be a huge help! |
Sorry, running out of hands here. |
As I said above, it is some easy to reproduce:
Sorry, I have so much to do here, I cannot write a test case for you here. |
OK, no problem, we'll do our best to move it forward as quick as we can |
Thank you, very much. |
Sorry to say but this is getting urgent. :-( |
@Quix0r Did you by any chance raise this issue with EclipseLink team? |
Sorry it's taken a while @Quix0r. We are, unfortunately, unable to give any guarantees or SLAs on issues raised via GitHub, since we always have to prioritise work for paying customers (we couldn't fund any work if we didn't!). If you get in touch with us, we can give you some details on pricing for a support contract where you would get SLAs on tickets and access to our customer-only patch releases so, once an issue has been fixed and merged into the codebase, you wouldn't have to wait more than a month to get a supported build (as opposed to only getting releases once a quarter normally). |
@lprimak Okay, I can report it there and link to here. :-) Maybe worth updating EclipseLink to latest (2.6.3 on download page versus 2.6 in Payara) version? And what we talking about? Do I have to wait a month or year to have this fixed? And maybe I'm not the only one with this bug around. Sadly you cannot easily switch to e.g. Hibernate with Payara/GF because it simply doesn't work. Also switching to WildFly is not painless. :-( |
The next public release will be the 2016 Q4 (164) release, which is currently targeted to early November. The version of Eclipselink in Payara is a patched 2.6.2. If the bug is in Eclipselink like @lprimak says, then let us know on this ticket and we will get it into the next public release as soon as it's made available by Eclipselink. |
Have you thought about dropping down into Native SQL to execute the query you wanted? |
No, the query runs over more than one table and cannot be joined. |
You would need to use a Union. |
@Quix0r, can you try if Payara 164 fixes the behavior? If it is not fixed, I recommend to try with Hibernate - you can bundle it in your application as suggested here: How To configure Hibernate as a JPA provider |
@Quix0r Payara 171 is now available, can you try to reproduce with the latest version? |
Okay, had not been developing JavaEE recently. Will try to reproduce with it. |
Is this still an issue @Quix0r? |
Sorry, no longer employed with them. Still a strange database layout (even the main administrator said that!). So never mind. |
Severity: Blocker (see reason below)
Reproduceable: Always
This message comes with following JPQL:
SELECT c FROM AbstractFoo AS c WHERE TYPE(c) IN :types
The class is annotated with:
Sadly I cannot simply switch to any other inheritance type as the table design is given (I write a JavaEE application for an existing database).
Then many other concrete classes expands it:
And tons more of these. As you can see, I try to minimize my code base, else I would have been required to duplicate all the entity properties to all concrete classes.
I already use Payara 162.
An excerpt from the backtrace:
The text was updated successfully, but these errors were encountered: