(FIXED) ABL classes in procedure library - Forum - OpenEdge Development - Progress Community

(FIXED) ABL classes in procedure library

 Forum

(FIXED) ABL classes in procedure library

  • Hi,

    After looking more into it, I realise what the problem is, no problems at all using prolib for classes

     Very quick question, is there something specific about adding compiled classes into a r-code library?

     Is it supposed to work, including static classes?

     I have a set of classes that work perfectly fine when using a folder with all compiled code but as soon as I introduce all that code into a library and add the path of this library in the propath it is then unable to find a static class used to create other objects. 

     Has anyone found issues with this before?

     Thanks,

  • Nope. Classes work fine in PL's. Static members too (note there aren't static *classes* in ooabl).  Make sure you added the classes correctly (ie Company.Module.Class.r and not just Class.r. prolib my.pl –list is very useful for this.
     
    What problems are you seeing? Error messages etc would be useful.
     
    -- peter
     
    From: pedromarcerodriguez [mailto:bounce-pedromarcerodriguez@community.progress.com]
    Sent: Monday, 08 September, 2014 12:10
    To: TU.OE.Development@community.progress.com
    Subject: [Technical Users - OE Development] ABL classes in procedure library
     
    Thread created by pedromarcerodriguez

    Hi,

     Very quick question, is there something specific about adding compiled classes into a r-code library?

     Is it supposed to work, including static classes?

     I have a set of classes that work perfectly fine when using a folder with all compiled code but as soon as I introduce all that code into a library and add the path of this library in the propath it is then unable to find a static class used to create other objects. 

     Has anyone found issues with this before?

     Thanks,

    Stop receiving emails on this subject.

    Flag this post as spam/abuse.