Home » Eclipse Projects » Dali » Mapping file "META-INF/orm.xml" does not have ORM content
|
| Re: Mapping file "META-INF/orm.xml" does not have ORM content [message #517233 is a reply to message #517094] |
Fri, 26 February 2010 16:15   |
 Paul Fullbright
Messages: 201
Registered: July 2009 |
Senior Member |
|
|
No, that file should be perfectly legal. The complaint is regarding whether or not Dali recognizes that file as being a legal orm.xml file.
Assuming you're using Dali 2.2 (and not a milestone), the problem may be that you're using a JPA 2.0 version of the orm.xml, which is not yet supported. If all you're doing is defining queries, a 1.0 version of the orm.xml should work just fine. Try that.
Otherwise, there could be a problem with Dali recognizing the file type, which should be solved with a project clean.
A third option is to try a milestone of Dali 2.3, which supports JPA 2.0 and EclipseLink 2.0 and also has solved some of these file content recognition issues. Being a milestone, it will have its stability problems compared to a release, but this might be tolerable in your situation.
- Paul
|
|
|
| Re: Mapping file "META-INF/orm.xml" does not have ORM content [message #517367 is a reply to message #517233] |
Sat, 27 February 2010 04:32 |
Ari Meyer
Messages: 136
Registered: July 2009 |
Senior Member |
|
|
Thanks, Paul.
Paul Fullbright wrote:
> No, that file should be perfectly legal. The complaint is regarding
> whether or not Dali recognizes that file as being a legal orm.xml file.
>
> Assuming you're using Dali 2.2 (and not a milestone), the problem may be
> that you're using a JPA 2.0 version of the orm.xml, which is not yet
> supported. If all you're doing is defining queries, a 1.0 version of
> the orm.xml should work just fine. Try that.
Yep, I'm using Dali 2.2, Eclipse 3.5.1.
I was using the JPA 1.0 version of the orm.xml when I first encountered
the validation error. I just moved to 2.0, and it's still there.
>
> Otherwise, there could be a problem with Dali recognizing the file type,
> which should be solved with a project clean.
Project clean seems to clear the error, that's correct. Whenever I
perform a JPA validation, though, the error comes up again.
>
> A third option is to try a milestone of Dali 2.3, which supports JPA 2.0
> and EclipseLink 2.0 and also has solved some of these file content
> recognition issues. Being a milestone, it will have its stability
> problems compared to a release, but this might be tolerable in your
> situation.
>
> - Paul
Thanks for the suggestion. It's not critical enough for me to switch to
a 2.3M, but good to know that 2.3 may address the problem.
Best,
Ari
|
|
|
| Re: Mapping file "META-INF/orm.xml" does not have ORM content [message #618862 is a reply to message #517094] |
Fri, 26 February 2010 16:15 |
Paul Fullbright
Messages: 201
Registered: July 2009 |
Senior Member |
|
|
No, that file should be perfectly legal. The complaint is regarding whether or not Dali recognizes that file as being a legal orm.xml file.
Assuming you're using Dali 2.2 (and not a milestone), the problem may be that you're using a JPA 2.0 version of the orm.xml, which is not yet supported. If all you're doing is defining queries, a 1.0 version of the orm.xml should work just fine. Try that.
Otherwise, there could be a problem with Dali recognizing the file type, which should be solved with a project clean.
A third option is to try a milestone of Dali 2.3, which supports JPA 2.0 and EclipseLink 2.0 and also has solved some of these file content recognition issues. Being a milestone, it will have its stability problems compared to a release, but this might be tolerable in your situation.
- Paul
|
|
|
| Re: Mapping file "META-INF/orm.xml" does not have ORM content [message #618864 is a reply to message #618862] |
Sat, 27 February 2010 09:20 |
Ari Meyer
Messages: 136
Registered: July 2009 |
Senior Member |
|
|
Thanks, Paul.
Paul Fullbright wrote:
> No, that file should be perfectly legal. The complaint is regarding
> whether or not Dali recognizes that file as being a legal orm.xml file.
>
> Assuming you're using Dali 2.2 (and not a milestone), the problem may be
> that you're using a JPA 2.0 version of the orm.xml, which is not yet
> supported. If all you're doing is defining queries, a 1.0 version of
> the orm.xml should work just fine. Try that.
Yep, I'm using Dali 2.2, Eclipse 3.5.1.
I was using the JPA 1.0 version of the orm.xml when I first encountered
the validation error. I just moved to 2.0, and it's still there.
>
> Otherwise, there could be a problem with Dali recognizing the file type,
> which should be solved with a project clean.
Project clean seems to clear the error, that's correct. Whenever I
perform a JPA validation, though, the error comes up again.
>
> A third option is to try a milestone of Dali 2.3, which supports JPA 2.0
> and EclipseLink 2.0 and also has solved some of these file content
> recognition issues. Being a milestone, it will have its stability
> problems compared to a release, but this might be tolerable in your
> situation.
>
> - Paul
Thanks for the suggestion. It's not critical enough for me to switch to
a 2.3M, but good to know that 2.3 may address the problem.
Best,
Ari
|
|
|
Goto Forum:
Current Time: Wed Apr 24 15:59:19 GMT 2024
Powered by FUDForum. Page generated in 0.02689 seconds |
] 
Search
Help
Register
Login
Home
