> what do you mean by that:
> hmm .. looking at that code in Wonder, it's:
> seems a little weird and unnecessary?
> Should I search in Wonder to use another way to controle the locking?
> My Application is freezing if I include that routine, it is not
> without the update.
That was a general question to the list about that lock warning ...
However, in your code:
wObject = new Webtext();
is wrong, you are violating at least one of the commandments here ...
you are calling setWebtext before wObject is in the editing context.
You're also calling validateForSave, which you don't do -- the
framework does that:
wObject = (Webtext)EOUtilities.createAndInsertInstance(ec,
lwObject = new LanguageWebtext();
is totally suffering from this ... I don't know if this is your
problem, but it WILL screw you eventually. You need to change your
ways on this one. Always createAndInsertInstance. Or EOGenerate
a .createXxx(..) method that does this for you -- I have some of our
sample templates in the wikibook that do this.
Get latest updates about Open Source Projects, Conferences and News.