<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/gsa-japi/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/gsa-japi/feature-requests/</id><updated>2011-05-17T06:24:29Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Support for Dynamic Navigation</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/10/" rel="alternate"/><published>2011-05-17T06:24:29Z</published><updated>2011-05-17T06:24:29Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net73a4975d6776c23936f0bc3cafe502fe648f58ca</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Since the 6.8 release, Dynamic Navigation is a feature of the GSA. This affects the response XML and thus, the gsa-japi needs to be updated to support this.&lt;/p&gt;
&lt;p&gt;At my company we have extended the gsa-japi to handle Dynamic Navigation and would be happy to contribute if that's possible&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support for KeyMatches</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/9/" rel="alternate"/><published>2008-02-08T15:23:53Z</published><updated>2008-02-08T15:23:53Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net16c80b029bcfd25973bf1e41491f4f8868ae7359</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, it appears the GSA keyMatches are returned in the XML from the Google Appliances and are dropped on the floor by the GSA-JAPI. I would like support to gain access to the KeyMatch feature of the Google Search Appliances from Java.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add Keymatch results</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/8/" rel="alternate"/><published>2007-11-09T20:21:39Z</published><updated>2007-11-09T20:21:39Z</updated><author><name>Shaun Farrugia</name><uri>https://sourceforge.net/u/dier0b0t/</uri></author><id>https://sourceforge.net3d16fc26a79723694a7a8da3639af499b691fb9c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Add keymatch results to the GSAResults object so that keymatch results can be retrieved from the API.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add getters/setters for custom search parameters</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/7/" rel="alternate"/><published>2007-05-02T18:37:05Z</published><updated>2007-05-02T18:37:05Z</updated><author><name>David Tiller</name><uri>https://sourceforge.net/u/dtiller/</uri></author><id>https://sourceforge.net43ce999e1f2d12d117f8db4adfc4fab8947ff3cc</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;For search frontends with custom XSLTs, it is sometimes necessary to pass custom search parameters to the GSA device. An example would be:&lt;/p&gt;
&lt;p&gt;.../search?q=News&amp;amp;myGreeting=Hello&lt;/p&gt;
&lt;p&gt;In the XSLT this is accessed with:&lt;/p&gt;
&lt;p&gt;&amp;lt;xsl:variable name="greeting"&amp;gt;&lt;br /&gt;
&amp;lt;xsl:value-of select="GSP/PARAM[@name='myGreeting']/@value"/&amp;gt;&lt;br /&gt;
&amp;lt;/xsl:variable&amp;gt;&lt;/p&gt;
&lt;p&gt;These custom parameters are available in the XML output of the device under the GSP/PARAM section.&lt;/p&gt;
&lt;p&gt;It would be nice to have&lt;/p&gt;
&lt;p&gt;public void setCustomParameters(Properties params)&lt;br /&gt;
public Properties getCustomParameters()&lt;/p&gt;
&lt;p&gt;methods on the GSAQuery object. They would be used like:&lt;/p&gt;
&lt;p&gt;Properties props = new Properties();&lt;br /&gt;
props.put("myGreeting", "Hello");&lt;br /&gt;
query.setCustomParameters(props);&lt;/p&gt;
&lt;p&gt;The result would be each name/value pair being appended to the URL.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add throws clause to GSAClientDelegate.getResponseStream</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/6/" rel="alternate"/><published>2007-04-23T14:51:34Z</published><updated>2007-04-23T14:51:34Z</updated><author><name>David Tiller</name><uri>https://sourceforge.net/u/dtiller/</uri></author><id>https://sourceforge.net39bb1b29c967e71e5acc4917784b309e36570ece</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Please add a 'throws IOException' clause to the method signature getResponseStream on the interface GSAClientDelegate. This will allow errors to be handled uniformly by the API. Note that the GSAClient method that calls the delegate throws an IOException and propagates IOExceptions upward if no delegate is used.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Provide a way to get link to previous page of results</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/5/" rel="alternate"/><published>2007-03-12T02:05:42Z</published><updated>2007-03-12T02:05:42Z</updated><author><name>Amol Deshmukh</name><uri>https://sourceforge.net/u/amolweb/</uri></author><id>https://sourceforge.net0b3db962389e553e0e7c111d73e015a64efeb27e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;GSA response includes both: url to previous as well as url to next page of results. As of release 1.7, the java api provides access only to the next page url.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Subcollections missing from Query Object</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/4/" rel="alternate"/><published>2006-12-06T17:19:02Z</published><updated>2006-12-06T17:19:02Z</updated><author><name>Brad Bernstein</name><uri>https://sourceforge.net/u/bbern/</uri></author><id>https://sourceforge.net791baad8961a96c023464ce4a8f77ec2844435fa</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I just noticed there is no GSA query parameter 'restrict' to define a subcollection for a query. Its absolutely trivial to add this into the source.&lt;/p&gt;
&lt;p&gt;Why were subcollection restrictions left out of the API? Is there something I'm missing?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>GSAQueryTerm.queryString setter</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/3/" rel="alternate"/><published>2006-05-19T11:21:17Z</published><updated>2006-05-19T11:21:17Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.neta23b1412d91e2b2c379f4a8461352a19e275802f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;There's no way to change the queryString attribute of&lt;br /&gt;
the GSAQueryTerm without having to make another&lt;br /&gt;
GSAQueryTerm object by GSAQueryTerm(String) constructor.&lt;/p&gt;
&lt;p&gt;Víctor.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>AS_EQ search parameter</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/2/" rel="alternate"/><published>2006-05-19T11:07:15Z</published><updated>2006-05-19T11:07:15Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.nete43a39c170c72eb86325ce02f5dc80a39ce5d43e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Query.java got &lt;br /&gt;
void setAs_eq(String as_eq) {&lt;br /&gt;
this.as_eq = as_eq;&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;But there's no way to change it from GSAQuery. just&lt;br /&gt;
need to implement SETer on GSAQuery.java&lt;/p&gt;
&lt;p&gt;Víctor&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>AS_DT search parameter</title><link href="https://sourceforge.net/p/gsa-japi/feature-requests/1/" rel="alternate"/><published>2006-05-19T11:02:09Z</published><updated>2006-05-19T11:02:09Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netf22075362625e77efea6e08a2c279831a1db0e29</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The GSAQuery doesn't got a method to change the&lt;br /&gt;
query.setAs_dt()&lt;/p&gt;
&lt;p&gt;Would be a GSAQuery Method that updates the&lt;br /&gt;
query.setAs_dt()&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Víctor&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>