I have had this happen to me before, but I don't recall why. Logging out a
stack trace (or setting a breakpoint if you are feeling modern) when
setQtyForSynthManifestTransaction is called with a null value is the quickest
way to solve this.
Chuck
On 2012-11-14, at 6:14 PM, prob...@macti.ca w
Envoyé de mon iPhone
Le 2012-11-14 à 21:00, "Chuck Hill" a écrit :
> Does BuildManifest have a reset() method.
Yes, I reset the variables that holds the values from the bindings in reset()
but I don't do anything for QtyForSynthManifestTransaction in reset()
> What is the stack trace when
I too have trouble with this stuff all the time...
if it is a stateless components where does qtyForSynthManifestTransaction get
stored? Do you have automatic binding turned off as well?
On Nov 14, 2012, at 3:51 PM, Pascal Robert wrote:
> I think I still have to understand a couple of things
Does BuildManifest have a reset() method. What is the stack trace when
setQtyForSynthManifestTransaction is called with a null value?
On 2012-11-14, at 5:51 PM, Pascal Robert wrote:
> I think I still have to understand a couple of things about components. So I
> have a component that display
I think I still have to understand a couple of things about components. So I
have a component that display a table where each row is coming from a
WORepetition. Inside each row, I have a column that calls a stateless
sub-component:
In BuildManifest, I have the following code:
On 15/11/2012, at 4:55 AM, Theodore Petrosky wrote:
> If I understand correctly, my local repository is now up to date with the
> projectwonder/wonder.git repo. However, my fork in my user account on github
> is not.
All correct. (To update your fork on Github, you would push from your local
On 2012-11-14, at 11:49 AM, Maik Musall wrote:
> Am 14.11.2012 um 17:57 schrieb Jesse Tayler :
>> you got some backtrace on that funky action?
>
> Happens also when a method using that attribute is directly invoked by a wod
> binding, in a component using autolocking.
Any chance something in y
Hi Ted:
That sounds about right. I just went through this with our company. If
you never want to commit an enhancement to Wonder you don't even need to
create a fork on github. You could just clone
https://github.com/projectwonder/wonder.git.
Now if you want to make changes to Wonder, then y
Am 14.11.2012 um 17:57 schrieb Jesse Tayler :
> you got some backtrace on that funky action?
Happens also when a method using that attribute is directly invoked by a wod
binding, in a component using autolocking.
Am 14.11.2012 um 18:21 schrieb Chuck Hill :
> Also the EOModel checks are only enf
I hope I have this correctly setup, I just want to confirm it with you git guys.
I forked the wonder repo to my own area on github, then I created a folder on
the root area of my user on my mac and cd'd into it.
cd ~/Repository and cloned my fork:
git clone https://github.com/tedpet/wonder.git
Also the EOModel checks are only enforced when saveChanges() runs. So it is
possible that a bug in your code is setting these to null before you try to use
them.
Chuck
On 2012-11-14, at 9:16 AM, Ramsey Gurley wrote:
>
> On Nov 14, 2012, at 8:54 AM, Maik Musall wrote:
>
>> Hi,
>>
>> occas
On Nov 14, 2012, at 8:54 AM, Maik Musall wrote:
> Hi,
>
> occasionally I get a NullPointerException on an attribute of a fetched EO
> that is
> * set to not nullable in EOModel
> * guarded to be not null by a NOT NULL constraint in the database
> * and actually has a value there.
>
> This happ
you got some backtrace on that funky action?
On Nov 14, 2012, at 10:54 AM, Maik Musall wrote:
> Hi,
>
> occasionally I get a NullPointerException on an attribute of a fetched EO
> that is
> * set to not nullable in EOModel
> * guarded to be not null by a NOT NULL constraint in the database
>
Hi,
occasionally I get a NullPointerException on an attribute of a fetched EO that
is
* set to not nullable in EOModel
* guarded to be not null by a NOT NULL constraint in the database
* and actually has a value there.
This happens with both simple values like BigDecimals, as well as with
relat
14 matches
Mail list logo