DO NOT REPLY [Bug 32054] - Pluggable area creation: AreaFactory
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32054. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32054 Pluggable area creation: AreaFactory --- Additional Comments From [EMAIL PROTECTED] 2004-11-04 11:32 --- Created an attachment (id=13325) AreaFactory patch
DO NOT REPLY [Bug 32054] - Pluggable area creation: AreaFactory
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32054. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32054 Pluggable area creation: AreaFactory --- Additional Comments From [EMAIL PROTECTED] 2004-11-04 16:47 --- A more complete 'brief' description of this is in this POST to fop-dev: http://marc.theaimsgroup.com/?l=fop-devm=109956963917611w=2
DO NOT REPLY [Bug 32054] - Pluggable area creation: AreaFactory
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32054.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32054
Pluggable area creation: AreaFactory
--- Additional Comments From [EMAIL PROTECTED] 2004-11-04 20:34 ---
In AbstractLayoutManager:
+protected AreaFactory getAreaFactory() {
+return (userAgent != null) ? userAgent.getAreaFactory() : null;
+}
BTW, we can make AreaFactory a ThreadLocal in AbstractLayoutManager, correct?
That way we can avoid .getAreaFactory() in FOUserAgent, also save the function
call.
I understand we couldn't do ThreadLocal for FOEventHandler (potentially
recursive FO documents within the same process would need a different instances
of FOEventHandler) but this may be a good use-case for ThreadLocal here.
