<?xml version="1.0" encoding="ISO-8859-1" ?>
<rss version="2.0"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
 xmlns:admin="http://webns.net/mvcb/"
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns:content="http://purl.org/rss/1.0/modules/content/"
 xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel><title>e-office Domino blog | Comments</title><description></description><link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/</link><language>en-us</language><lastBuildDate>Thu, 2 Feb 2012 11:46:27 +0200</lastBuildDate>
<item>
<title>Technical details of our new corporate website</title>
<pubDate>Thu, 2 Feb 2012 11:46:27 +0200</pubDate>
<dc:creator>online copywriters</dc:creator>
<dc:subject>Technical details of our new corporate website</dc:subject>
<description><![CDATA[This post is luminous and the complete information and the fascinations are appears to be the sparkling one, high-quality to share!]]></description>
<content:encoded><![CDATA[This post is luminous and the complete information and the fascinations are appears to be the sparkling one, high-quality to share!]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/technical-details-of-our-new-corporate-website.htm?opendocument&amp;comments#02022012114627AMSHAEN4.htm</link>
</item>
<item>
<title>Quick XPages tip: Sample xsp.properties file</title>
<pubDate>Tue, 31 Jan 2012 09:37:43 +0200</pubDate>
<dc:creator>Paul Withers</dc:creator>
<dc:subject>Quick XPages tip: Sample xsp.properties file</dc:subject>
<description><![CDATA[Yes, the xsp.properties file is very useful, lots of great settings.]]></description>
<content:encoded><![CDATA[Yes, the xsp.properties file is very useful, lots of great settings.]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/quick-xpages-tip-sample-file-of-the-xsp.properties.htm?opendocument&amp;comments#31012012093743SHAC5M.htm</link>
</item>
<item>
<title>Quick XPages tip: Sample xsp.properties file</title>
<pubDate>Mon, 30 Jan 2012 19:01:12 +0200</pubDate>
<dc:creator>Dan O&#8217;Connor</dc:creator>
<dc:subject>Quick XPages tip: Sample xsp.properties file</dc:subject>
<description><![CDATA[Shameless plug.... The XPages Portable Command Guide which is scheduled for release in mid February contains a chapter dedicated to xsp.properties and explains what each of the settings within that file does:<br /><br />www.amazon.com/XPages-Portable-Command-Guide-Application/dp/0132943050/ref=sr_1_1?ie=UTF8&qid=1327946374&sr=8-1]]></description>
<content:encoded><![CDATA[Shameless plug.... The XPages Portable Command Guide which is scheduled for release in mid February contains a chapter dedicated to xsp.properties and explains what each of the settings within that file does:<br /><br />www.amazon.com/XPages-Portable-Command-Guide-Application/dp/0132943050/ref=sr_1_1?ie=UTF8&qid=1327946374&sr=8-1]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/quick-xpages-tip-sample-file-of-the-xsp.properties.htm?opendocument&amp;comments#01302012070112PMSHAP5T.htm</link>
</item>
<item>
<title>Quick XPages tip: Sample xsp.properties file</title>
<pubDate>Mon, 30 Jan 2012 17:33:45 +0200</pubDate>
<dc:creator>Leif Lagebrand</dc:creator>
<dc:subject>Quick XPages tip: Sample xsp.properties file</dc:subject>
<description><![CDATA[Can't find no xsp-properties file. Should I create one from sample to take the settings in effect?<br /><br />What is the default for all of this properties if I have no xsp.properties file?]]></description>
<content:encoded><![CDATA[Can't find no xsp-properties file. Should I create one from sample to take the settings in effect?<br /><br />What is the default for all of this properties if I have no xsp.properties file?]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/quick-xpages-tip-sample-file-of-the-xsp.properties.htm?opendocument&amp;comments#2012-01-30173345SHAMF6.htm</link>
</item>
<item>
<title>Bug in Domino Pickers in Internet Explorer 9</title>
<pubDate>Sun, 29 Jan 2012 00:09:23 +0200</pubDate>
<dc:creator>Sean Cull</dc:creator>
<dc:subject>Bug in Domino Pickers in Internet Explorer 9</dc:subject>
<description><![CDATA[Thanks for this, I hit this problem during the week and would like to fix it properly rather than using comptability mode.]]></description>
<content:encoded><![CDATA[Thanks for this, I hit this problem during the week and would like to fix it properly rather than using comptability mode.]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/bug-in-domino-pickers-in-internet-explorer-9.htm?opendocument&amp;comments#29012012000923SHAV6E.htm</link>
</item>
<item>
<title>Bug in Domino Pickers in Internet Explorer 9</title>
<pubDate>Sat, 28 Jan 2012 22:41:12 +0200</pubDate>
<dc:creator>Paul T. Calhoun</dc:creator>
<dc:subject>Bug in Domino Pickers in Internet Explorer 9</dc:subject>
<description><![CDATA[What happens if you force just that page to "compatibility" mode by setting the mode in the xpage on load event?<br /><br />This is how we "fixed" the dojo charting for folks that were running 8.5.2 and IE9.<br /><br />That should keep you from having to replace individual library files on the server which could introduce other issues.<br /><br />Paul T. Calhoun]]></description>
<content:encoded><![CDATA[What happens if you force just that page to "compatibility" mode by setting the mode in the xpage on load event?<br /><br />This is how we "fixed" the dojo charting for folks that were running 8.5.2 and IE9.<br /><br />That should keep you from having to replace individual library files on the server which could introduce other issues.<br /><br />Paul T. Calhoun]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/bug-in-domino-pickers-in-internet-explorer-9.htm?opendocument&amp;comments#01282012104112PMSHATFB.htm</link>
</item>
<item>
<title>Installing 8.5.3 Upgrade Pack 1 and keep the SBT and JDBC extensions (Part 2)</title>
<pubDate>Tue, 24 Jan 2012 17:49:17 +0200</pubDate>
<dc:creator></dc:creator>
<dc:subject>Installing 8.5.3 Upgrade Pack 1 and keep the SBT and JDBC extensions (Part 2)</dc:subject>
<description><![CDATA[]]></description>
<content:encoded><![CDATA[]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/installing-8.5.3-upgrade-pack-1-and-keep-the-sbt-and-jdbc-extensions-part-2.htm?opendocument&amp;comments#01242012054917PMSHAMQU.htm</link>
</item>
<item>
<title>New Release of the XPages RSS Control on OpenNTF</title>
<pubDate>Thu, 5 Jan 2012 14:59:30 +0200</pubDate>
<dc:creator>Patrick Kwinten</dc:creator>
<dc:subject>New Release of the XPages RSS Control on OpenNTF</dc:subject>
<description><![CDATA[de feed is van 1 source als ik het goed begrijp? hoe moeilijk is het om meerdere sources aan de feed toe te voegen?]]></description>
<content:encoded><![CDATA[de feed is van 1 source als ik het goed begrijp? hoe moeilijk is het om meerdere sources aan de feed toe te voegen?]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/new-release-of-the-xpages-rss-control-on-openntf.htm?opendocument&amp;comments#01052012025930PMSHAJER.htm</link>
</item>
<item>
<title>Quick XPages Tip: Use view as variable with caution</title>
<pubDate>Thu, 8 Dec 2011 23:13:21 +0200</pubDate>
<dc:creator>Tim Tripcony</dc:creator>
<dc:subject>Quick XPages Tip: Use view as variable with caution</dc:subject>
<description><![CDATA["view" is a reserved word in SSJS (refers to the JSF notion of a "view root"... in other words, "view" as in "model view controller", aka "MVC", not a Domino view), as is "database", "session", "context", "param", and so on. These "intrinsic globals" should NEVER be used as variables to refer to other objects.<br /><br />There's actually a very simple way to avoid this problem: use descriptive variable names... for example, "viewSnippets". Not only does this make the code easier to read, since the variable actually indicates WHICH view it refers to - not just that it's a view - but variables named this way are extremely unlikely to collide with intrinsic global variable names.]]></description>
<content:encoded><![CDATA["view" is a reserved word in SSJS (refers to the JSF notion of a "view root"... in other words, "view" as in "model view controller", aka "MVC", not a Domino view), as is "database", "session", "context", "param", and so on. These "intrinsic globals" should NEVER be used as variables to refer to other objects.<br /><br />There's actually a very simple way to avoid this problem: use descriptive variable names... for example, "viewSnippets". Not only does this make the code easier to read, since the variable actually indicates WHICH view it refers to - not just that it's a view - but variables named this way are extremely unlikely to collide with intrinsic global variable names.]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/quick-xpages-tip-be-aware-of-the-use-of-view-as-variable.htm?opendocument&amp;comments#12082011111321PMSHAU3E.htm</link>
</item>
<item>
<title>Is it a bug: xsp.resources.aggregate = true and Firefox </title>
<pubDate>Fri, 11 Nov 2011 08:53:38 +0200</pubDate>
<dc:creator>Ulrich Krause</dc:creator>
<dc:subject>Is it a bug: xsp.resources.aggregate = true and Firefox </dc:subject>
<description><![CDATA[Wondering where the extra option "Discard Javascript ..." comes from. Don't see it in my 8.5.3 Designer.]]></description>
<content:encoded><![CDATA[Wondering where the extra option "Discard Javascript ..." comes from. Don't see it in my 8.5.3 Designer.]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/is-it-a-bug-xsp.resources.aggregate-and-firefox.htm?opendocument&amp;comments#11.11.2011085338SHABA3.htm</link>
</item>
<item>
<title>Is it a bug: xsp.resources.aggregate = true and Firefox </title>
<pubDate>Thu, 10 Nov 2011 18:40:41 +0200</pubDate>
<dc:creator>ulrich krause</dc:creator>
<dc:subject>Is it a bug: xsp.resources.aggregate = true and Firefox </dc:subject>
<description><![CDATA[Same here with jquery minimized files. Not loaded when I activate the option. Working when unchecked. Posted in design partner forum but no response so far. Great that I am not the only one.]]></description>
<content:encoded><![CDATA[Same here with jquery minimized files. Not loaded when I activate the option. Working when unchecked. Posted in design partner forum but no response so far. Great that I am not the only one.]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/is-it-a-bug-xsp.resources.aggregate-and-firefox.htm?opendocument&amp;comments#10.11.2011184041SHANQY.htm</link>
</item>
<item>
<title>Extension Library Next Generation:  oneuiv2.1  is not  oneUIv2.1 </title>
<pubDate>Wed, 9 Nov 2011 15:37:44 +0200</pubDate>
<dc:creator>Jan Krejcarek</dc:creator>
<dc:subject>Extension Library Next Generation: &quot;oneuiv2.1&quot; is not &quot;oneUIv2.1&quot;</dc:subject>
<description><![CDATA[Hi, I was wondering today why my navigator disappeared from my application which does not inherit from oneUI but uses the navigator component (using custom styling). <br /><br />I have found out that in the Extension Library there is a class ThemeUtil which checks the current oneUI version and sets a renderer accordingly. This class makes check using lower case only, so this may be the "problem".<br /><br />However, when You set the property rendererType of the navigator to "com.ibm.xsp.extlib.OneUIOutlineMenu", it will render the navigator even when the theme is not oneUI...<br /><br />regards,<br /><br />Jan]]></description>
<content:encoded><![CDATA[Hi, I was wondering today why my navigator disappeared from my application which does not inherit from oneUI but uses the navigator component (using custom styling). <br /><br />I have found out that in the Extension Library there is a class ThemeUtil which checks the current oneUI version and sets a renderer accordingly. This class makes check using lower case only, so this may be the "problem".<br /><br />However, when You set the property rendererType of the navigator to "com.ibm.xsp.extlib.OneUIOutlineMenu", it will render the navigator even when the theme is not oneUI...<br /><br />regards,<br /><br />Jan]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/extension-library-next-generation-theme-.htm?opendocument&amp;comments#09.11.2011153744SHAK6M.htm</link>
</item>
<item>
<title>What is the reason behind this?</title>
<pubDate>Wed, 19 Oct 2011 11:09:19 +0200</pubDate>
<dc:creator>Patrick Kwinten</dc:creator>
<dc:subject>Extension Library Next Generation: &quot;oneuiv2.1&quot; is not &quot;oneUIv2.1&quot;</dc:subject>
<description><![CDATA[]]></description>
<content:encoded><![CDATA[]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/extension-library-next-generation-theme-.htm?opendocument&amp;comments#19102011110919SHACRD.htm</link>
</item>
<item>
<title>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</title>
<pubDate>Tue, 11 Oct 2011 23:18:20 +0200</pubDate>
<dc:creator>Lars Berntrop-Bos</dc:creator>
<dc:subject>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</dc:subject>
<description><![CDATA[@Almar doc also says:<br /><br />8&lt;---------------------<br /><br />The second way in which PIRC prevents older documents from replicating in is by stopping the documents from being added to the database via NoteUpdate. This method occurs when a non-PIRC aware server is pushing older documents to the PIRC-aware server. In this case, NoteUpdate code will compare the SequenceTime of the document to the PIRC date. If the document is older, a DDM event will be logged and the document will be rejected. Note that the source server is unaware that the document was rejected. Therefore its logs will show that all documents were successfully replicated. However, the PIRC server will log the server name and the documents that were rejected, thus allowing the administrator to track down old replicas of the database and remove them from the environment.<br /><br />8&lt;---------------------<br /><br />In my mind, any doc with Sequence time older than PIRC date will be stopped replicating in. Not only for deleted documents. Will have to try, this is annoying source of pain in my environment...]]></description>
<content:encoded><![CDATA[@Almar doc also says:<br /><br />8&lt;---------------------<br /><br />The second way in which PIRC prevents older documents from replicating in is by stopping the documents from being added to the database via NoteUpdate. This method occurs when a non-PIRC aware server is pushing older documents to the PIRC-aware server. In this case, NoteUpdate code will compare the SequenceTime of the document to the PIRC date. If the document is older, a DDM event will be logged and the document will be rejected. Note that the source server is unaware that the document was rejected. Therefore its logs will show that all documents were successfully replicated. However, the PIRC server will log the server name and the documents that were rejected, thus allowing the administrator to track down old replicas of the database and remove them from the environment.<br /><br />8&lt;---------------------<br /><br />In my mind, any doc with Sequence time older than PIRC date will be stopped replicating in. Not only for deleted documents. Will have to try, this is annoying source of pain in my environment...]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/domino-8.5.3-introduces-a-new-life-save-pirc.htm?opendocument&amp;comments#10112011111820PMSHASYZ.htm</link>
</item>
<item>
<title>Technical details of our new corporate website</title>
<pubDate>Sat, 8 Oct 2011 08:20:10 +0200</pubDate>
<dc:creator>Web Design Company</dc:creator>
<dc:subject>Technical details of our new corporate website</dc:subject>
<description><![CDATA[Great blog.......]]></description>
<content:encoded><![CDATA[Great blog.......]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/technical-details-of-our-new-corporate-website.htm?opendocument&amp;comments#10082011082010AMSHA9FN.htm</link>
</item>
<item>
<title>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</title>
<pubDate>Fri, 7 Oct 2011 14:29:16 +0200</pubDate>
<dc:creator>Almar Diehl</dc:creator>
<dc:subject>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</dc:subject>
<description><![CDATA[@Lars the document states "to prevent old documents which may have been deleted from replicating back into a database after their deletion stubs have been purged"]]></description>
<content:encoded><![CDATA[@Lars the document states "to prevent old documents which may have been deleted from replicating back into a database after their deletion stubs have been purged"]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/domino-8.5.3-introduces-a-new-life-save-pirc.htm?opendocument&amp;comments#07102011142916SHAGNC.htm</link>
</item>
<item>
<title>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</title>
<pubDate>Fri, 7 Oct 2011 13:33:00 +0200</pubDate>
<dc:creator>Lars Berntrop-Bos</dc:creator>
<dc:subject>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</dc:subject>
<description><![CDATA[Huh? In https://www-304.ibm.com/support/docview.wss?uid=swg21501675 I cannot find it works only for deleted docs. Can you tell me what i overlooked in the technote?]]></description>
<content:encoded><![CDATA[Huh? In https://www-304.ibm.com/support/docview.wss?uid=swg21501675 I cannot find it works only for deleted docs. Can you tell me what i overlooked in the technote?]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/domino-8.5.3-introduces-a-new-life-save-pirc.htm?opendocument&amp;comments#10072011013300PMSHAFK7.htm</link>
</item>
<item>
<title>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</title>
<pubDate>Thu, 6 Oct 2011 14:45:13 +0200</pubDate>
<dc:creator>Almar Diehl</dc:creator>
<dc:subject>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</dc:subject>
<description><![CDATA[Ha Patrick,<br /><br />unfortunately PIRC only works for deleted doc.]]></description>
<content:encoded><![CDATA[Ha Patrick,<br /><br />unfortunately PIRC only works for deleted doc.]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/domino-8.5.3-introduces-a-new-life-save-pirc.htm?opendocument&amp;comments#06102011144513SHAGYB.htm</link>
</item>
<item>
<title>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</title>
<pubDate>Thu, 6 Oct 2011 13:32:18 +0200</pubDate>
<dc:creator>Patrick Kwinten</dc:creator>
<dc:subject>Domino 8.5.3 introduces a new &#8217;life saver&#8217;: PIRC</dc:subject>
<description><![CDATA[Hoi Almar,<br /><br />We have a problem with an application were old documents (not deleted ones) get replicated from local replicas into a central application. This causes problems with the application since data in the documents are out of date.<br /><br />I was wondering if these PIRC function could prevent 'old' incoming documents?<br /><br />As I understood from the presentation by Chris Miller the function focuses on deleted documents...<br /><br />Thanks for any assistance! KR / Patrick]]></description>
<content:encoded><![CDATA[Hoi Almar,<br /><br />We have a problem with an application were old documents (not deleted ones) get replicated from local replicas into a central application. This causes problems with the application since data in the documents are out of date.<br /><br />I was wondering if these PIRC function could prevent 'old' incoming documents?<br /><br />As I understood from the presentation by Chris Miller the function focuses on deleted documents...<br /><br />Thanks for any assistance! KR / Patrick]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/domino-8.5.3-introduces-a-new-life-save-pirc.htm?opendocument&amp;comments#10062011013218PMSHAFJR.htm</link>
</item>
<item>
<title>Extensions disappeared in Domino Designer 8.5.3</title>
<pubDate>Wed, 5 Oct 2011 21:00:52 +0200</pubDate>
<dc:creator>Mat Newman</dc:creator>
<dc:subject>Extensions disappeared in Domino Designer 8.5.3</dc:subject>
<description><![CDATA[Mate, do a search on your HDD for the install.xml file. Remove them from there, and go again...]]></description>
<content:encoded><![CDATA[Mate, do a search on your HDD for the install.xml file. Remove them from there, and go again...]]></content:encoded>
<link>http://www.domino-weblog.com/weblogs/domino_blog.nsf/dx/extensions-disappeared-in-domino-designer-8.5.3.htm?opendocument&amp;comments#10052011090052PMSHAQB4.htm</link>
</item>

</channel></rss>

