You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by Jean-Baptiste BRIAUD -- Novlog <j-...@novlog.com> on 2011/02/07 10:50:51 UTC
Error message improvement suggestion
Hi the list,
I got the following exception :
Caused by: <openjpa-2.0.1-r422266:989424 nonfatal user error> org.apache.openjpa.persistence.ArgumentException: cant-set-value
at org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.insert(HandlerFieldStrategy.java:132)
at org.apache.openjpa.jdbc.meta.FieldMapping.insert(FieldMapping.java:623)
at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.insert(AbstractUpdateManager.java:230)
at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.populateRowManager(AbstractUpdateManager.java:162)
at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:95)
at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:731)
at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
... 35 more
Would it be possible to add the field/column name which the value can't be set ?
Re: Error message improvement suggestion
Posted by Jean-Baptiste BRIAUD -- Novlog <j-...@novlog.com>.
Just come back from holidays.
Thanks !
On 11 févr. 2011, at 15:22, Michael Dick wrote:
> Hi Jean-Baptiste,
>
> It's published to the apache snapshot repository now. Let me know if if
> doesn't have the info that you need.
>
> -mike
>
> On Wed, Feb 9, 2011 at 9:04 AM, Michael Dick <mi...@gmail.com>wrote:
>
>> We've been having problems with the Hudson builds lately (they publish to
>> the maven repository).
>>
>> So, yes it should be there, but no it isn't. Yet. I'll requested another
>> hudson build but I'm not sure where it is in the queue. If it isn't
>> published in a hour or so I'll look into doing a manual build.
>>
>> Sorry this took so long, I'll reply to this thread when I know it's in the
>> maven repo.
>>
>> -mike
>>
>>
>> On Wed, Feb 9, 2011 at 7:30 AM, Jean-Baptiste BRIAUD -- Novlog <
>> j-b.briaud@novlog.com> wrote:
>>
>>> Would it be in the 2.0 branch trunk currently ?
>>> In other words, if I checkout the 2.0.x nightly build will I have the new
>>> message ?
>>>
>>>
>>> https://repository.apache.org/snapshots/org/apache/openjpa/apache-openjpa/2.0.2-SNAPSHOT/
>>>
>>> I'm in the dark to debug some code and I think I do need this helpful
>>> information :-)
>>>
>>> Thanks !
>>>
>>> On 7 févr. 2011, at 17:04, Michael Dick wrote:
>>>
>>>> Looks like the message text was removed between version 1.2 and 2.0.
>>> I've
>>>> restored it in trunk and I'll put it back in 2.0 and 2.1 too.
>>>>
>>>> Thanks for reporting the problem.
>>>>
>>>> -mike
>>>>
>>>> On Mon, Feb 7, 2011 at 3:50 AM, Jean-Baptiste BRIAUD -- Novlog <
>>>> j-b.briaud@novlog.com> wrote:
>>>>
>>>>> Hi the list,
>>>>>
>>>>> I got the following exception :
>>>>> Caused by: <openjpa-2.0.1-r422266:989424 nonfatal user error>
>>>>> org.apache.openjpa.persistence.ArgumentException: cant-set-value
>>>>> at
>>>>>
>>> org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.insert(HandlerFieldStrategy.java:132)
>>>>> at
>>>>> org.apache.openjpa.jdbc.meta.FieldMapping.insert(FieldMapping.java:623)
>>>>> at
>>>>>
>>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.insert(AbstractUpdateManager.java:230)
>>>>> at
>>>>>
>>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.populateRowManager(AbstractUpdateManager.java:162)
>>>>> at
>>>>>
>>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:95)
>>>>> at
>>>>>
>>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76)
>>>>> at
>>>>>
>>> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:731)
>>>>> at
>>>>>
>>> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
>>>>> ... 35 more
>>>>>
>>>>> Would it be possible to add the field/column name which the value can't
>>> be
>>>>> set ?
>>>>>
>>>>>
>>>
>>>
>>
Re: Error message improvement suggestion
Posted by Michael Dick <mi...@gmail.com>.
Hi Jean-Baptiste,
It's published to the apache snapshot repository now. Let me know if if
doesn't have the info that you need.
-mike
On Wed, Feb 9, 2011 at 9:04 AM, Michael Dick <mi...@gmail.com>wrote:
> We've been having problems with the Hudson builds lately (they publish to
> the maven repository).
>
> So, yes it should be there, but no it isn't. Yet. I'll requested another
> hudson build but I'm not sure where it is in the queue. If it isn't
> published in a hour or so I'll look into doing a manual build.
>
> Sorry this took so long, I'll reply to this thread when I know it's in the
> maven repo.
>
> -mike
>
>
> On Wed, Feb 9, 2011 at 7:30 AM, Jean-Baptiste BRIAUD -- Novlog <
> j-b.briaud@novlog.com> wrote:
>
>> Would it be in the 2.0 branch trunk currently ?
>> In other words, if I checkout the 2.0.x nightly build will I have the new
>> message ?
>>
>>
>> https://repository.apache.org/snapshots/org/apache/openjpa/apache-openjpa/2.0.2-SNAPSHOT/
>>
>> I'm in the dark to debug some code and I think I do need this helpful
>> information :-)
>>
>> Thanks !
>>
>> On 7 févr. 2011, at 17:04, Michael Dick wrote:
>>
>> > Looks like the message text was removed between version 1.2 and 2.0.
>> I've
>> > restored it in trunk and I'll put it back in 2.0 and 2.1 too.
>> >
>> > Thanks for reporting the problem.
>> >
>> > -mike
>> >
>> > On Mon, Feb 7, 2011 at 3:50 AM, Jean-Baptiste BRIAUD -- Novlog <
>> > j-b.briaud@novlog.com> wrote:
>> >
>> >> Hi the list,
>> >>
>> >> I got the following exception :
>> >> Caused by: <openjpa-2.0.1-r422266:989424 nonfatal user error>
>> >> org.apache.openjpa.persistence.ArgumentException: cant-set-value
>> >> at
>> >>
>> org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.insert(HandlerFieldStrategy.java:132)
>> >> at
>> >> org.apache.openjpa.jdbc.meta.FieldMapping.insert(FieldMapping.java:623)
>> >> at
>> >>
>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.insert(AbstractUpdateManager.java:230)
>> >> at
>> >>
>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.populateRowManager(AbstractUpdateManager.java:162)
>> >> at
>> >>
>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:95)
>> >> at
>> >>
>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76)
>> >> at
>> >>
>> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:731)
>> >> at
>> >>
>> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
>> >> ... 35 more
>> >>
>> >> Would it be possible to add the field/column name which the value can't
>> be
>> >> set ?
>> >>
>> >>
>>
>>
>
Re: Error message improvement suggestion
Posted by Michael Dick <mi...@gmail.com>.
We've been having problems with the Hudson builds lately (they publish to
the maven repository).
So, yes it should be there, but no it isn't. Yet. I'll requested another
hudson build but I'm not sure where it is in the queue. If it isn't
published in a hour or so I'll look into doing a manual build.
Sorry this took so long, I'll reply to this thread when I know it's in the
maven repo.
-mike
On Wed, Feb 9, 2011 at 7:30 AM, Jean-Baptiste BRIAUD -- Novlog <
j-b.briaud@novlog.com> wrote:
> Would it be in the 2.0 branch trunk currently ?
> In other words, if I checkout the 2.0.x nightly build will I have the new
> message ?
>
>
> https://repository.apache.org/snapshots/org/apache/openjpa/apache-openjpa/2.0.2-SNAPSHOT/
>
> I'm in the dark to debug some code and I think I do need this helpful
> information :-)
>
> Thanks !
>
> On 7 févr. 2011, at 17:04, Michael Dick wrote:
>
> > Looks like the message text was removed between version 1.2 and 2.0. I've
> > restored it in trunk and I'll put it back in 2.0 and 2.1 too.
> >
> > Thanks for reporting the problem.
> >
> > -mike
> >
> > On Mon, Feb 7, 2011 at 3:50 AM, Jean-Baptiste BRIAUD -- Novlog <
> > j-b.briaud@novlog.com> wrote:
> >
> >> Hi the list,
> >>
> >> I got the following exception :
> >> Caused by: <openjpa-2.0.1-r422266:989424 nonfatal user error>
> >> org.apache.openjpa.persistence.ArgumentException: cant-set-value
> >> at
> >>
> org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.insert(HandlerFieldStrategy.java:132)
> >> at
> >> org.apache.openjpa.jdbc.meta.FieldMapping.insert(FieldMapping.java:623)
> >> at
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.insert(AbstractUpdateManager.java:230)
> >> at
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.populateRowManager(AbstractUpdateManager.java:162)
> >> at
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:95)
> >> at
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76)
> >> at
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:731)
> >> at
> >>
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
> >> ... 35 more
> >>
> >> Would it be possible to add the field/column name which the value can't
> be
> >> set ?
> >>
> >>
>
>
Re: Error message improvement suggestion
Posted by Jean-Baptiste BRIAUD -- Novlog <j-...@novlog.com>.
Would it be in the 2.0 branch trunk currently ?
In other words, if I checkout the 2.0.x nightly build will I have the new message ?
https://repository.apache.org/snapshots/org/apache/openjpa/apache-openjpa/2.0.2-SNAPSHOT/
I'm in the dark to debug some code and I think I do need this helpful information :-)
Thanks !
On 7 févr. 2011, at 17:04, Michael Dick wrote:
> Looks like the message text was removed between version 1.2 and 2.0. I've
> restored it in trunk and I'll put it back in 2.0 and 2.1 too.
>
> Thanks for reporting the problem.
>
> -mike
>
> On Mon, Feb 7, 2011 at 3:50 AM, Jean-Baptiste BRIAUD -- Novlog <
> j-b.briaud@novlog.com> wrote:
>
>> Hi the list,
>>
>> I got the following exception :
>> Caused by: <openjpa-2.0.1-r422266:989424 nonfatal user error>
>> org.apache.openjpa.persistence.ArgumentException: cant-set-value
>> at
>> org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.insert(HandlerFieldStrategy.java:132)
>> at
>> org.apache.openjpa.jdbc.meta.FieldMapping.insert(FieldMapping.java:623)
>> at
>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.insert(AbstractUpdateManager.java:230)
>> at
>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.populateRowManager(AbstractUpdateManager.java:162)
>> at
>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:95)
>> at
>> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76)
>> at
>> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:731)
>> at
>> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
>> ... 35 more
>>
>> Would it be possible to add the field/column name which the value can't be
>> set ?
>>
>>
Re: Error message improvement suggestion
Posted by Michael Dick <mi...@gmail.com>.
Looks like the message text was removed between version 1.2 and 2.0. I've
restored it in trunk and I'll put it back in 2.0 and 2.1 too.
Thanks for reporting the problem.
-mike
On Mon, Feb 7, 2011 at 3:50 AM, Jean-Baptiste BRIAUD -- Novlog <
j-b.briaud@novlog.com> wrote:
> Hi the list,
>
> I got the following exception :
> Caused by: <openjpa-2.0.1-r422266:989424 nonfatal user error>
> org.apache.openjpa.persistence.ArgumentException: cant-set-value
> at
> org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.insert(HandlerFieldStrategy.java:132)
> at
> org.apache.openjpa.jdbc.meta.FieldMapping.insert(FieldMapping.java:623)
> at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.insert(AbstractUpdateManager.java:230)
> at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.populateRowManager(AbstractUpdateManager.java:162)
> at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:95)
> at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:731)
> at
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
> ... 35 more
>
> Would it be possible to add the field/column name which the value can't be
> set ?
>
>