You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Adrian Crum <ad...@sandglass-software.com> on 2014/10/04 09:48:35 UTC
Delegator.getNextSeqIdLong
I use the Delegator sequencer any time I need a unique value, and many
times the sequence name is not an entity name. This causes a lot of
stack traces in the log because GenericDelegator considers that to be an
error.
I would like to make a small change to GenericDelegator so that sequence
names that don't match an entity name will log an INFO message instead
of an ERROR stack trace.
What do you think?
--
Adrian Crum
Sandglass Software
www.sandglass-software.com
Re: Delegator.getNextSeqIdLong
Posted by Jacopo Cappellato <ja...@hotwaxmedia.com>.
cool
On Oct 4, 2014, at 11:04 AM, Adrian Crum <ad...@sandglass-software.com> wrote:
> No, I will leave that method as-is. I plan to C&P that method's code to getNextSeqIdLong and log an INFO message instead of an ERROR stack trace.
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 10/4/2014 9:57 AM, Jacopo Cappellato wrote:
>> +1
>>
>> I guess you are going to modify the method getModelEntity(...)
>>
>> Jacopo
>>
>> On Oct 4, 2014, at 9:48 AM, Adrian Crum <ad...@sandglass-software.com> wrote:
>>
>>> I use the Delegator sequencer any time I need a unique value, and many times the sequence name is not an entity name. This causes a lot of stack traces in the log because GenericDelegator considers that to be an error.
>>>
>>> I would like to make a small change to GenericDelegator so that sequence names that don't match an entity name will log an INFO message instead of an ERROR stack trace.
>>>
>>> What do you think?
>>>
>>> --
>>> Adrian Crum
>>> Sandglass Software
>>> www.sandglass-software.com
>>
Re: Delegator.getNextSeqIdLong
Posted by Adrian Crum <ad...@sandglass-software.com>.
No, I will leave that method as-is. I plan to C&P that method's code to
getNextSeqIdLong and log an INFO message instead of an ERROR stack trace.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/4/2014 9:57 AM, Jacopo Cappellato wrote:
> +1
>
> I guess you are going to modify the method getModelEntity(...)
>
> Jacopo
>
> On Oct 4, 2014, at 9:48 AM, Adrian Crum <ad...@sandglass-software.com> wrote:
>
>> I use the Delegator sequencer any time I need a unique value, and many times the sequence name is not an entity name. This causes a lot of stack traces in the log because GenericDelegator considers that to be an error.
>>
>> I would like to make a small change to GenericDelegator so that sequence names that don't match an entity name will log an INFO message instead of an ERROR stack trace.
>>
>> What do you think?
>>
>> --
>> Adrian Crum
>> Sandglass Software
>> www.sandglass-software.com
>
Re: Delegator.getNextSeqIdLong
Posted by Jacopo Cappellato <ja...@hotwaxmedia.com>.
+1
I guess you are going to modify the method getModelEntity(...)
Jacopo
On Oct 4, 2014, at 9:48 AM, Adrian Crum <ad...@sandglass-software.com> wrote:
> I use the Delegator sequencer any time I need a unique value, and many times the sequence name is not an entity name. This causes a lot of stack traces in the log because GenericDelegator considers that to be an error.
>
> I would like to make a small change to GenericDelegator so that sequence names that don't match an entity name will log an INFO message instead of an ERROR stack trace.
>
> What do you think?
>
> --
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com