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=42558>. 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=42558 ------- Additional Comments From [EMAIL PROTECTED] 2007-08-21 13:20 ------- Just realized that I made a really stupid mistake: I replied to some of the above posts on the dev mailing list instead of bugzilla. Really silly. I apologize for this. The state of this issue is as follows: 1.0 The publication properties cannot be read in the initialization phase. At least I don't know how. The approach with Request request = contextUtility.getRequest(); DocumentFactory factory = DocumentUtil.getDocumentFactory(serviceManager, request); Publication[] pubs = publicationManager.getPublications(factory); cannot be used in the initialization phase. You get "Unable to get the request object from the context" when you try it. Being able to call publicationManager.getPublications() without the factory parameter could maybe help, but this doesn't seem to be possible unless some of the recent changes of Andreas have changed this. 1.1 This leads to the workaround with loadPublicationPropertiesIfNotDone, called from all get* methods which circumvents the problem by lazy loading the publication properties. 1.2 This in turn led to the question if this could cause synchronization problems. I don't think calling loadPublicationPropertiesIfNotDone twice in parallel would be very dangerous but I am not fit enough to judge this. 2.0 Jörn suggested to (re-)use aggregating fallback for properties of templated publications. 2.1 I found AggregatingFallbackSourceFactory which provides the protocol called "aggregate-fallback://". I think to be able to reuse it some of the code of getSource would have to be refactored. I am not able to do this myself without help. If anybody with a better understanding of the big picture could have a look at it and tell me if this is the right way to go i would give it a try. (There are some similarities in code with FallbackSourceFactory.getSource, so maybe this would have to be taken into account as well.) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
