Home » Eclipse Projects » Dali » persistence.xml file not detected on restart
| | | |
| Re: persistence.xml file not detected on restart [message #434536 is a reply to message #434532] |
Thu, 02 August 2007 02:16   |
 Sanjay Kumar
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
Neil,
I don't recall if I have added a non-text annotation. I did add some
attributes. If it was non-string then it probably was a
@Temporal(TemporalType.DATE).
I have been having symptoms of Bug 195895 for quite some time and I
thought I had gotten past it that by removing "+" from the named queries
(making them cumbersome single line queries).
Right now I can't use Dali because of Bug 192675 and 195895.
I am not too familiar with WTP release process. Will 1.0.1 be part of WTP
2.0.1 or a later release ? Are any of Dali bug fixes includes in milestone
builds ?
thanks for all your help,
-Sanjay
Neil Hauge wrote:
> Sanjay,
> The persistence.xml validation error you are seeing is probably related to
> the bug mentioned above. In your case the error doesn't get cleared
> because when we try to build our model, we fail due to a problem reading
> one of your new annotation value entries. This is likely related to bug
> 195895. We are discovering that Dali is unable to read some annotation
> value usages, and in this case, the culprit appears to be
> org.eclipse.jdt.core.dom.QualifiedName.
> Did you recently add any annotation value that does not use a string
> literal? Something other than the standard @Foo(value="bar") or
> @Foo("bar").
> Neil
> Sanjay Kumar wrote:
>> I am seeing no persistence.xml in the project error - for a project that
>> was working fine. I made some minor entity changes - should not have cause
>> anything to break. But JPA validation fails. Could it have anything to do
>> with following exception in the logs ?
>> eclipse.buildId=I20070625-1500
>> java.version=1.5.0_12
>> java.vendor=Sun Microsystems Inc.
>> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
>> Command-line arguments: -os win32 -ws win32 -arch x86
>> Error
>> Sat Jul 28 11:15:44 EDT 2007
>> An error occurred while traversing resources.
>> java.lang.ClassCastException: org.eclipse.jdt.core.dom.QualifiedName
>> at
>>
>
org.eclipse.jpt.core.internal.jdtutility.StringExpressionCon verter.convert_(StringExpressionConverter.java:1)
>> at
>>
|
|
|
| Re: persistence.xml file not detected on restart [message #434538 is a reply to message #434536] |
Fri, 03 August 2007 17:59 |
Neil Hauge
Messages: 475
Registered: July 2009 |
Senior Member |
|
|
Sanjay,
The temporal setting you mention should be fine, since we handle this type
of setting without problem. Are there any instances of using constants in
your annotation values?
We are working on the fix for 195895 right now, so if things go well they
could be in a WTP I-Build in the near future. 1.0.1 will be a part of WTP
2.0.1 and yes, Dali bug fixes will be included in the milestone builds as
well. I think the best thing to do (in general for now) would be to check
out the most recent 2.0.1 I-Builds, since these would be more stable than
future milestone releases. The I-Builds are currently done every 2 weeks
and can be found here - http://download.eclipse.org/webtools/downloads/
I think once we have all the related issues for 195895 fixed, 192675 won't
be as problematic.
Thanks for helping us investigate these issues.
Neil
Sanjay Kumar wrote:
> Neil,
> I don't recall if I have added a non-text annotation. I did add some
> attributes. If it was non-string then it probably was a
> @Temporal(TemporalType.DATE).
> I have been having symptoms of Bug 195895 for quite some time and I
> thought I had gotten past it that by removing "+" from the named queries
> (making them cumbersome single line queries).
> Right now I can't use Dali because of Bug 192675 and 195895.
> I am not too familiar with WTP release process. Will 1.0.1 be part of WTP
> 2.0.1 or a later release ? Are any of Dali bug fixes includes in milestone
> builds ?
> thanks for all your help,
> -Sanjay
> Neil Hauge wrote:
>> Sanjay,
>> The persistence.xml validation error you are seeing is probably related to
>> the bug mentioned above. In your case the error doesn't get cleared
>> because when we try to build our model, we fail due to a problem reading
>> one of your new annotation value entries. This is likely related to bug
>> 195895. We are discovering that Dali is unable to read some annotation
>> value usages, and in this case, the culprit appears to be
>> org.eclipse.jdt.core.dom.QualifiedName.
>> Did you recently add any annotation value that does not use a string
>> literal? Something other than the standard @Foo(value="bar") or
>> @Foo("bar").
>> Neil
>> Sanjay Kumar wrote:
>>> I am seeing no persistence.xml in the project error - for a project that
>>> was working fine. I made some minor entity changes - should not have cause
>>> anything to break. But JPA validation fails. Could it have anything to do
>>> with following exception in the logs ?
>>> eclipse.buildId=I20070625-1500
>>> java.version=1.5.0_12
>>> java.vendor=Sun Microsystems Inc.
>>> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
>>> Command-line arguments: -os win32 -ws win32 -arch x86
>>> Error
>>> Sat Jul 28 11:15:44 EDT 2007
>>> An error occurred while traversing resources.
>>> java.lang.ClassCastException: org.eclipse.jdt.core.dom.QualifiedName
>>> at
>>>
>>
>
org.eclipse.jpt.core.internal.jdtutility.StringExpressionCon verter.convert_(StringExpressionConverter.java:1)
>>> at
>>>
|
|
| | | |
| Re: persistence.xml file not detected on restart [message #605110 is a reply to message #434532] |
Thu, 02 August 2007 02:16 |
Sanjay Kumar
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
Neil,
I don't recall if I have added a non-text annotation. I did add some
attributes. If it was non-string then it probably was a
@Temporal(TemporalType.DATE).
I have been having symptoms of Bug 195895 for quite some time and I
thought I had gotten past it that by removing "+" from the named queries
(making them cumbersome single line queries).
Right now I can't use Dali because of Bug 192675 and 195895.
I am not too familiar with WTP release process. Will 1.0.1 be part of WTP
2.0.1 or a later release ? Are any of Dali bug fixes includes in milestone
builds ?
thanks for all your help,
-Sanjay
Neil Hauge wrote:
> Sanjay,
> The persistence.xml validation error you are seeing is probably related to
> the bug mentioned above. In your case the error doesn't get cleared
> because when we try to build our model, we fail due to a problem reading
> one of your new annotation value entries. This is likely related to bug
> 195895. We are discovering that Dali is unable to read some annotation
> value usages, and in this case, the culprit appears to be
> org.eclipse.jdt.core.dom.QualifiedName.
> Did you recently add any annotation value that does not use a string
> literal? Something other than the standard @Foo(value="bar") or
> @Foo("bar").
> Neil
> Sanjay Kumar wrote:
>> I am seeing no persistence.xml in the project error - for a project that
>> was working fine. I made some minor entity changes - should not have cause
>> anything to break. But JPA validation fails. Could it have anything to do
>> with following exception in the logs ?
>> eclipse.buildId=I20070625-1500
>> java.version=1.5.0_12
>> java.vendor=Sun Microsystems Inc.
>> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
>> Command-line arguments: -os win32 -ws win32 -arch x86
>> Error
>> Sat Jul 28 11:15:44 EDT 2007
>> An error occurred while traversing resources.
>> java.lang.ClassCastException: org.eclipse.jdt.core.dom.QualifiedName
>> at
>>
>
org.eclipse.jpt.core.internal.jdtutility.StringExpressionCon verter.convert_(StringExpressionConverter.java:1)
>> at
>>
|
|
|
| Re: persistence.xml file not detected on restart [message #605122 is a reply to message #434536] |
Fri, 03 August 2007 17:59 |
Neil Hauge
Messages: 475
Registered: July 2009 |
Senior Member |
|
|
Sanjay,
The temporal setting you mention should be fine, since we handle this type
of setting without problem. Are there any instances of using constants in
your annotation values?
We are working on the fix for 195895 right now, so if things go well they
could be in a WTP I-Build in the near future. 1.0.1 will be a part of WTP
2.0.1 and yes, Dali bug fixes will be included in the milestone builds as
well. I think the best thing to do (in general for now) would be to check
out the most recent 2.0.1 I-Builds, since these would be more stable than
future milestone releases. The I-Builds are currently done every 2 weeks
and can be found here - http://download.eclipse.org/webtools/downloads/
I think once we have all the related issues for 195895 fixed, 192675 won't
be as problematic.
Thanks for helping us investigate these issues.
Neil
Sanjay Kumar wrote:
> Neil,
> I don't recall if I have added a non-text annotation. I did add some
> attributes. If it was non-string then it probably was a
> @Temporal(TemporalType.DATE).
> I have been having symptoms of Bug 195895 for quite some time and I
> thought I had gotten past it that by removing "+" from the named queries
> (making them cumbersome single line queries).
> Right now I can't use Dali because of Bug 192675 and 195895.
> I am not too familiar with WTP release process. Will 1.0.1 be part of WTP
> 2.0.1 or a later release ? Are any of Dali bug fixes includes in milestone
> builds ?
> thanks for all your help,
> -Sanjay
> Neil Hauge wrote:
>> Sanjay,
>> The persistence.xml validation error you are seeing is probably related to
>> the bug mentioned above. In your case the error doesn't get cleared
>> because when we try to build our model, we fail due to a problem reading
>> one of your new annotation value entries. This is likely related to bug
>> 195895. We are discovering that Dali is unable to read some annotation
>> value usages, and in this case, the culprit appears to be
>> org.eclipse.jdt.core.dom.QualifiedName.
>> Did you recently add any annotation value that does not use a string
>> literal? Something other than the standard @Foo(value="bar") or
>> @Foo("bar").
>> Neil
>> Sanjay Kumar wrote:
>>> I am seeing no persistence.xml in the project error - for a project that
>>> was working fine. I made some minor entity changes - should not have cause
>>> anything to break. But JPA validation fails. Could it have anything to do
>>> with following exception in the logs ?
>>> eclipse.buildId=I20070625-1500
>>> java.version=1.5.0_12
>>> java.vendor=Sun Microsystems Inc.
>>> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
>>> Command-line arguments: -os win32 -ws win32 -arch x86
>>> Error
>>> Sat Jul 28 11:15:44 EDT 2007
>>> An error occurred while traversing resources.
>>> java.lang.ClassCastException: org.eclipse.jdt.core.dom.QualifiedName
>>> at
>>>
>>
>
org.eclipse.jpt.core.internal.jdtutility.StringExpressionCon verter.convert_(StringExpressionConverter.java:1)
>>> at
>>>
|
|
|
Goto Forum:
Current Time: Thu Apr 25 09:36:49 GMT 2024
Powered by FUDForum. Page generated in 0.03619 seconds |
] 
Search
Help
Register
Login
Home
