Skip to main content
A
Anonymous
February 22, 2012
Question

Difference in the load time of instance.acl between 5.3 and 5.4?

  • February 22, 2012
  • 1 reply
  • 563 views
Found something else odd in the upgrade to 5.4 M100 from 5.3 M040.

I had an ACL function in the instance.acl file that resided in a particular doctype, and it was called from the FOSI of said doctype to return a value to a savetext (occurred upon opening).

With the upgrade, opening a document of this doctype would throw an error that this function (defined in FOSI) was not found. The only way to get this func to load before the FOSI needed it was to move it to the init directory.

Doesn't hurt anything, just wondering why the change, or did I miss something (maybe a 'fix' that just showed up)? I guess I was just trying to avoid loading doctype-specific functions on startup if I didn't have to...

-Jason

    1 reply

    B
    bibach1-Visitor
    1-Visitor
    February 22, 2012
    Functions called from a doctype's FOSI should only need to be defined
    once, no matter how many documents of that type you open, so they're
    good candidates to go in a doctype.acl, rather than instance.acl. I
    don't know for sure that this will fix the problem you're seeing, but
    the doctype.acl does load earlier than instance.acl, so it might.

    The problem you describe seems rather odd and makes me wonder if
    something else is at play. You might try reverting to a completely
    stock Arbortext installation with no customizations to see if that
    fixes the issue, then add things back until you find the culprit.
    Ditto on the zipped customization thing.

    -Brandon 🙂


    On Wed, Feb 22, 2012 at 10:55 AM, Buss, Jason A
    <jabuss@cessna.textron.com> wrote:
    > Found something else odd in the upgrade to 5.4 M100 from 5.3 M040.
    >
    >
    >
    > I had an ACL function in the instance.acl file that resided in a particular
    > doctype, and it was called from the FOSI of said doctype to return a value
    > to a savetext (occurred upon opening).
    >
    >
    >
    > With the upgrade, opening a document of this doctype would throw an error
    > that this function (defined in FOSI) was not found. The only way to get
    > this func to load before the FOSI needed it was to move it to the init
    > directory.
    >
    >
    >
    > Doesn’t hurt anything, just wondering why the change, or did I miss
    > something (maybe a ‘fix’ that just showed up)? I guess I was just trying to
    > avoid loading doctype-specific functions on startup if I didn’t have to…
    >
    >
    >
    > -Jason
    >
    >
    > -----End Original Message-----
    Terms & ConditionsAccessibility statement