P
Peter Judge
Guest
Assuming nothing changed between then and now ... Make sure you (manually) delete all r-code first – there are times when the compiler (or PDSOE) puts rcode where you don't expect/want it. I was more after the 'super' or 'this-object' calls and the constructor signatures. -- peter From: toomaskask [mailto:bounce-toomaskask@community.progress.com] Sent: Friday, 14 November, 2014 13:03 To: TU.OE.Development@community.progress.com Subject: RE: [Technical Users - OE Development] Strange error: Cannot use NEW statement with class 'xxx' using a protected constructor. (12959) RE: Strange error: Cannot use NEW statement with class 'xxx' using a protected constructor. (12959) Reply by toomaskask schas: yes, I have public constructor with no parameters in Class A . Thomas: because PDS generates such a code? Peter: full code is too big to post it here. But you can trust me, there is no protected constructor. 
I have strange feeling that this problem is somehow related to how our code is compiled & cached in client side. Because same code worked yesterday, but started to fail occasionally today ie sometimes it worked, sometimes not. I'll investigate this theory further. Wbr, Toomas Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
I have strange feeling that this problem is somehow related to how our code is compiled & cached in client side. Because same code worked yesterday, but started to fail occasionally today ie sometimes it worked, sometimes not. I'll investigate this theory further. Wbr, Toomas Stop receiving emails on this subject. Flag this post as spam/abuse.Continue reading...