Delegator.getNextSeqIdLong

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Delegator.getNextSeqIdLong

Adrian Crum-3
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
Reply | Threaded
Open this post in threaded view
|

Re: Delegator.getNextSeqIdLong

Jacopo Cappellato-4
+1

I guess you are going to modify the method getModelEntity(...)

Jacopo

On Oct 4, 2014, at 9:48 AM, Adrian Crum <[hidden email]> 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

Reply | Threaded
Open this post in threaded view
|

Re: Delegator.getNextSeqIdLong

Adrian Crum-3
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 <[hidden email]> 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
>
Reply | Threaded
Open this post in threaded view
|

Re: Delegator.getNextSeqIdLong

Jacopo Cappellato-4
cool

On Oct 4, 2014, at 11:04 AM, Adrian Crum <[hidden email]> 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 <[hidden email]> 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
>>