<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/ist-contract/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/ist-contract/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 19 Nov 2008 11:06:53 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/ist-contract/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Concurrent modification conflict in AgentEndpoint</title><link>https://sourceforge.net/p/ist-contract/feature-requests/22/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The functionality of the method AgentEndpoint.provideData(…) is not&lt;br /&gt;
clear. As it is provided as an interface of an agent there is either&lt;br /&gt;
concurrent modification conflict or unpredictable data loosing. In a very&lt;br /&gt;
special situation when the agent puts some data to its RuntimeDataHolder&lt;br /&gt;
under some key (e.g., "TopSecretDataForBebe") and somebody else rewrite&lt;br /&gt;
them using provideData("TopSecretDataForBebe", ...) before Bebe’s&lt;br /&gt;
application requests them (using requestData("TopSecretDataForBebe", ...),&lt;br /&gt;
the data read by Bebe are the data altered by someone else but they seem to&lt;br /&gt;
be the data from the agent.&lt;/p&gt;
&lt;p&gt;This is not problem only in intended data forging, such functionality may&lt;br /&gt;
be critical e.g. during review when random events supported by “magic&lt;br /&gt;
numbers” in code may invoke emergent behavior of the system that we have&lt;br /&gt;
not seen before :o) &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Hodik</dc:creator><pubDate>Wed, 19 Nov 2008 11:06:53 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net10099fff0a488c5d60887b17edea5758e8dbeade</guid></item><item><title>Clean code from the AgentShell that does not belong</title><link>https://sourceforge.net/p/ist-contract/feature-requests/21/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Including specific things like the Contract domain XJC classes, the Sensor, the ContractWorkflow, etc.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sergio Alvarez Napagao</dc:creator><pubDate>Tue, 18 Nov 2008 20:02:32 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netb5e50fa289544215348e4597009258f2ee55bf88</guid></item><item><title>Remove depenency on exist jars.</title><link>https://sourceforge.net/p/ist-contract/feature-requests/20/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The ContractRepository interface currently returns the contact as a xmldb resource. This means we need the exist jars (several of them) in the AgentWS project. &lt;/p&gt;
&lt;p&gt;I propose we change the interface to return the contract as a String containing the xml. This would remove the need for the exist jars.&lt;/p&gt;
&lt;p&gt;It should be done in two steps: &lt;/p&gt;
&lt;p&gt;1) Introduce a new method to get the contract as a string and deprecate the old method.&lt;/p&gt;
&lt;p&gt;2) Once the Observer, Analyser, ContractStorer Agent etc. have converted to the new method remove the old method and jars.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoff Drake</dc:creator><pubDate>Tue, 18 Nov 2008 10:36:22 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net18dcb8df358bb97321a6ce62061cc85bd2397dc2</guid></item><item><title>make all operations on shared data thread-safe</title><link>https://sourceforge.net/p/ist-contract/feature-requests/19/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;All of the operations working of shared data within one agent (e.g. AgentKernel.putPercept() adding events to the queue) should be made thread-safe - i.e. either synchronize the methods working with the unsynchronized data or wrap the data by synchronized wrappers from Collections and ensure an appropriate use anywhere in the project (best by shielding such use by appropriate encapsulation). This basically requires a peer survey of the whole platform to catch all possible occurances of thread-unsafe operations.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Fri, 07 Nov 2008 15:26:55 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net32fb78714e56a6364a8a51bc33255b8c80dd041b</guid></item><item><title>tidy up build scripts + minimize/unify property/config files</title><link>https://sourceforge.net/p/ist-contract/feature-requests/18/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The build scripts should be made IDE independent (while IDE non-adversarial) and should use a minimized and unified number of property and config files. Practically it involves:&lt;/p&gt;
&lt;p&gt;- separate all building functionality of the ant scripts from NetBeans in a way not preventing IDEs (NetBeans, Eclipse, other) from their reuse (particularly remove dependency on build-impl.xml etc).&lt;/p&gt;
&lt;p&gt;- make build scripts stable on all OS (e.g. substitute the dependences on the currently unstable implementation of the apt task under windows)&lt;/p&gt;
&lt;p&gt;- remove unnecessary repetitive invocation of targets caused by their inappropriate sequencing&lt;/p&gt;
&lt;p&gt;- move copying of libs from ConractLibraries into project folders from the clean targets into pre-compile targets&lt;/p&gt;
&lt;p&gt;- make everything explicitely configurable in property and config files (e.g. removing javac classpath definitions from the code of build scripts and either pushing the  enumeration of libraries to be included into a property files like NetBeans scripts do or making the build script to take as classpath definition content of the project lib folder)&lt;/p&gt;
&lt;p&gt;- make a small number of property/config files common for all projects available in trunk to which all build scripts would referer to (either remove copies of the property files from the projects and use those in trunk by refering to the parent folder - like ../agent.properties) or make a build target in trunk distributing the configuration conistently into all project folders so that those project properties/config files would not need to be maintained itself, but instead the trunk property/config files only)&lt;/p&gt;
&lt;p&gt;- add targets for remote deployment into build scripts if possible (I quess Geoffrey knows how to do it)&lt;/p&gt;
&lt;p&gt;- swap contents of the cont and contrib folders in AgentWSGui (the only project having an inconsistent policy on this with respect to the rest of the projects)&lt;/p&gt;
&lt;p&gt;- add a target in AgentWS for building the web service stubs into a standalone jar&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Fri, 07 Nov 2008 15:16:14 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net91878e5017d1edf118424b3b585d71ecd8c15364</guid></item><item><title>Remove code of the Sensor from agent shell</title><link>https://sourceforge.net/p/ist-contract/feature-requests/17/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The code of the Sensor should be removed from the agent shell and should remain as a standalone jar. This is currently prevented by the web service stubs being non-separable from the platform - i.e. depends on resolutuion of the feature 2137564 - see &lt;a href="https://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137564&amp;amp;group_id=206620&amp;amp;atid=998331"&gt;https://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137564&amp;amp;group_id=206620&amp;amp;atid=998331&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Fri, 07 Nov 2008 12:52:08 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netf922a46b47c445a43637b435ca852d9308e4fcb8</guid></item><item><title>Redundant files in ContractLibraries</title><link>https://sourceforge.net/p/ist-contract/feature-requests/16/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;In the ContractLibraries at least following files are multiple times there in various directories. Some of them also seem to be in different versions:&lt;/p&gt;
&lt;p&gt;activation.jar &lt;br /&gt;
jaxb-xjc.jar &lt;br /&gt;
ContractRepository.jar &lt;br /&gt;
AgentWebServiceLib.jar &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Hodik</dc:creator><pubDate>Tue, 30 Sep 2008 07:37:33 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net4549fc2369aa56e4c41d28ddb5f55714452dfe05</guid></item><item><title>Modular deployment of the Contracting Environment</title><link>https://sourceforge.net/p/ist-contract/feature-requests/15/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently we lack a possibility to deploy more AWSPlatformBuilder-derived projects concurently to a single server instance (i.e. one running glassfish) due to necessity for keeping "AgentWebServiceLib" name in all such projects which results in mutual redeployment of sequentially deployed projects so that the last one survives. This should be possible. This feature requests relates to request &lt;a href="http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137564&amp;amp;group_id=206620&amp;amp;atid=998331"&gt;http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137564&amp;amp;group_id=206620&amp;amp;atid=998331&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Tue, 30 Sep 2008 07:02:05 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6fbc4f388ef72f0b9985d942b2ba3e46bdad26fc</guid></item><item><title>Configurable module-dependent lib deployent</title><link>https://sourceforge.net/p/ist-contract/feature-requests/14/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Besides separation of sth-specific modules from AgentWS, the libraries required by such modules should be separable as well, unless already used by AgentWS. Specification of the libraries, i.e. a list should be a part of the module descriptor and should be used on deployment. This request is related to the request &lt;a href="http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137564&amp;amp;group_id=206620&amp;amp;atid=998331"&gt;http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=2137564&amp;amp;group_id=206620&amp;amp;atid=998331&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Tue, 30 Sep 2008 06:56:22 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7088e19d47ad3eeda2effb71a7232613a8b14035</guid></item><item><title>Configurable module management</title><link>https://sourceforge.net/p/ist-contract/feature-requests/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Besides the minimal set of modules to be always loaded (like communication manager, message manager, etc.) the rest of the modules like workflow manager, contract manager, monitor, etc. should be loaded and initialized only of needed which should be specified in a module configuration file. Each module should have a descriptor stating what modules it depends on so that modules ould be loaded in a proper order.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jiri Biba</dc:creator><pubDate>Tue, 30 Sep 2008 06:32:58 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net303ed4eccfd8d10194b3267f87a856610291ab5f</guid></item></channel></rss>