<?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/jacson/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/jacson/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/jacson/feature-requests/</id><updated>2006-03-13T10:53:53Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Create SLF4JReport</title><link href="https://sourceforge.net/p/jacson/feature-requests/28/" rel="alternate"/><published>2006-03-13T10:53:53Z</published><updated>2006-03-13T10:53:53Z</updated><author><name>Patrick Carl</name><uri>https://sourceforge.net/u/userid-613247/</uri></author><id>https://sourceforge.net7e08c5140607ec641c89539e8b27b1ac1cf76eba</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;There exists a wrapper library for the various existing &lt;br /&gt;
logging librarys SLF4J created by the founder of log4j. &lt;br /&gt;
Since Jacson already supports log4j we could use this &lt;br /&gt;
library to support different logging libraries as well.&lt;br /&gt;
Details &lt;a href="http://www.slf4j.org." rel="nofollow"&gt;http://www.slf4j.org.&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Input source which groups lines</title><link href="https://sourceforge.net/p/jacson/feature-requests/27/" rel="alternate"/><published>2005-09-20T12:54:58Z</published><updated>2005-09-20T12:54:58Z</updated><author><name>Gerald Glocker</name><uri>https://sourceforge.net/u/glocker/</uri></author><id>https://sourceforge.net157663d8cb63f479ffee081a74261414c43ccd60</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be useful to have a source which group&lt;br /&gt;
multiple lines into one chunk. The grouping could be&lt;br /&gt;
done by delimiters.&lt;/p&gt;
&lt;p&gt;It should be possible to group the following file&lt;/p&gt;
&lt;p&gt;-----&lt;br /&gt;
create table x (&lt;br /&gt;
...&lt;br /&gt;
...&lt;br /&gt;
);&lt;/p&gt;
&lt;p&gt;create table y (&lt;br /&gt;
...&lt;br /&gt;
...&lt;br /&gt;
);&lt;br /&gt;
-----&lt;/p&gt;
&lt;p&gt;into two chunks by the delimiter ";".&lt;/p&gt;
&lt;p&gt;The implementation could collect lines until the&lt;br /&gt;
delimiter is contained in a line.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>LuceneSource</title><link href="https://sourceforge.net/p/jacson/feature-requests/26/" rel="alternate"/><published>2004-11-10T09:00:41Z</published><updated>2004-11-10T09:00:41Z</updated><author><name>Patrick Carl</name><uri>https://sourceforge.net/u/userid-613247/</uri></author><id>https://sourceforge.net18121ce221665cb48b0b6c213b2b8b43ce401f54</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Implement a JacsonSouce for a Lucene Index.&lt;br /&gt;
Inspired by LuceneDesktop &lt;a href="http://www.peerfear.org/rss/permalink/" rel="nofollow"&gt;http://www.peerfear.org/rss/permalink/&lt;/a&gt;&lt;br /&gt;
2004/10/28/LotsOfInterestInLuceneDesktop.&lt;/p&gt;
&lt;p&gt;Could it be possible to create such an application with the above &lt;br /&gt;
source and some XML using jacson?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>KeyWordFilter</title><link href="https://sourceforge.net/p/jacson/feature-requests/25/" rel="alternate"/><published>2004-06-17T11:31:22Z</published><updated>2004-06-17T11:31:22Z</updated><author><name>Patrick Carl</name><uri>https://sourceforge.net/u/userid-613247/</uri></author><id>https://sourceforge.net4ad9d07bba989ed0366a9f9783a858d789843767</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;A Filter filtering out a configurable number of key words.&lt;br /&gt;
The resulting key words could be used in a search request in a web &lt;br /&gt;
search engine.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>BrokenLinkFilter</title><link href="https://sourceforge.net/p/jacson/feature-requests/24/" rel="alternate"/><published>2004-03-30T12:42:36Z</published><updated>2004-03-30T12:42:36Z</updated><author><name>Patrick Carl</name><uri>https://sourceforge.net/u/userid-613247/</uri></author><id>https://sourceforge.net717f1fd8ca02078da6cec139692e44f12480f61c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Filter checking if a given link is still working. &lt;/p&gt;
&lt;p&gt;Use Cases: Checking bookmark files, web pages, ...&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Make Jacson create multiple Mail</title><link href="https://sourceforge.net/p/jacson/feature-requests/23/" rel="alternate"/><published>2003-05-16T22:08:21Z</published><updated>2003-05-16T22:08:21Z</updated><author><name>Frank Nestel</name><uri>https://sourceforge.net/u/nestefan/</uri></author><id>https://sourceforge.netad12a1771d68c976209e809bff062b5eb83ec1ab</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;If one could extends the Jacson MailReport to create&lt;br /&gt;
mails not only on summary time, but in between (when?&lt;br /&gt;
on every event?), this in combination with the&lt;br /&gt;
JacsonTail file watching feature could make Jacson a&lt;br /&gt;
controll device for remote servers.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Integrate Jacson into JJacket</title><link href="https://sourceforge.net/p/jacson/feature-requests/22/" rel="alternate"/><published>2003-05-12T22:06:45Z</published><updated>2003-05-12T22:06:45Z</updated><author><name>Frank Nestel</name><uri>https://sourceforge.net/u/nestefan/</uri></author><id>https://sourceforge.net1b35046d3e48845cbf00d4afe917053fe25e12be</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;JJacket seems to be a very interesting device. With&lt;br /&gt;
some deep integration Jacson could become the file&lt;br /&gt;
filtering language of JJacket..&lt;/p&gt;
&lt;p&gt;Integrations could be:&lt;br /&gt;
* Commandline (as in the usual shell, done).&lt;br /&gt;
* Special JJacket commandline (more efficent, and&lt;br /&gt;
interact with the JJacket environment)&lt;br /&gt;
* Think about making jjacket plugable into JJacket&lt;br /&gt;
pipes. But pipes in Jjacket seem to be fairly new yet.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Make Sources pluggable</title><link href="https://sourceforge.net/p/jacson/feature-requests/21/" rel="alternate"/><published>2003-05-12T20:52:22Z</published><updated>2003-05-12T20:52:22Z</updated><author><name>Patrick Carl</name><uri>https://sourceforge.net/u/userid-613247/</uri></author><id>https://sourceforge.netc1b727ceb107705e0a691d871a340905eddbd032</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;To include a source other than the default LineChunkSource you have &lt;br /&gt;
to do hacking. There are different feature requests which deal with &lt;br /&gt;
hacking Jacson-Applications that work with different sources.&lt;/p&gt;
&lt;p&gt;Why do we use a different approach to Sources than to every other &lt;br /&gt;
component of Jacson? Filters, Evaluators, Reports - everything &lt;br /&gt;
pluggable? &lt;/p&gt;
&lt;p&gt;So why not extend JacsonChunkSource with a method &lt;br /&gt;
init(ConfigNode config) and plug in Sources like everything else?&lt;/p&gt;
&lt;p&gt;It could be possible to include multiple sources by dealing with them &lt;br /&gt;
one after another.&lt;/p&gt;
&lt;p&gt;Are there any design principles that would be injured if I would try &lt;br /&gt;
this?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Javadoc</title><link href="https://sourceforge.net/p/jacson/feature-requests/20/" rel="alternate"/><published>2003-04-25T10:44:20Z</published><updated>2003-04-25T10:44:20Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net9354c8b06aa2e78d74a0f0f188e9c382f117fb18</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The javadoc is very poor and it does not help &lt;br /&gt;
extending the framework&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Documentation</title><link href="https://sourceforge.net/p/jacson/feature-requests/19/" rel="alternate"/><published>2003-04-08T12:24:29Z</published><updated>2003-04-08T12:24:29Z</updated><author><name>Frank Nestel</name><uri>https://sourceforge.net/u/nestefan/</uri></author><id>https://sourceforge.net6237cc2c3966abdf1f6d4c2c56bc8d69a05bf241</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Jacson consists of many plugabble components. To&lt;br /&gt;
fullfill the &amp;amp;quot;configure not program&amp;amp;quot; paradigm, a user&lt;br /&gt;
documentation of these&lt;br /&gt;
would be necessary.&lt;/p&gt;
&lt;p&gt;The xslt documentation system allready includes some&lt;br /&gt;
hooks, so the idea would be to insert the user&lt;br /&gt;
documentation in the plugin class main JavaDoc section.&lt;br /&gt;
That would work immediately. Unfortunately there isn't&lt;br /&gt;
much helpful information in those sections yet and the&lt;br /&gt;
information is very different.&lt;/p&gt;
&lt;p&gt;A style quide how the information should look should be&lt;br /&gt;
the Ant-Task documentation which has also been used by&lt;br /&gt;
the Jacson documentation on the Jacson Ant task.&lt;/p&gt;
&lt;p&gt;To make the effort useful ASAP, the order of proceeding&lt;br /&gt;
should be per plugin type in that particular order:&lt;br /&gt;
1. Filters&lt;br /&gt;
2. Selections&lt;br /&gt;
3. Reports&lt;br /&gt;
4. Evaluators&lt;br /&gt;
5. Sources (not really plugins I know)&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>