<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Csergiy%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
</w:LatentStyles>
</xml><![endif]--><!--[if !mso]><object
classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></object>
<style>
st1\:*{behavior:url(#ieooui) }
</style>
<![endif]--><style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
pre
{margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Courier New";
mso-fareast-font-family:"Times New Roman";}
span.mxmlcomponent
{mso-style-name:mxmlcomponent;}
span.mxmlstring
{mso-style-name:mxmlstring;}
span.xmltagsymbols
{mso-style-name:xml_tag_symbols;}
span.xmltagname
{mso-style-name:xml_tag_name;}
span.xmlplain
{mso-style-name:xml_plain;}
span.xmlattributename
{mso-style-name:xml_attribute_name;}
span.xmlattributevalue
{mso-style-name:xml_attribute_value;}
@page Section1
{size:595.3pt 841.9pt;
margin:44.95pt 55.3pt 44.95pt 45.0pt;
mso-header-margin:35.4pt;
mso-footer-margin:35.4pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
</style>
<![endif]-->
<p class="MsoNormal"><b style=""><span style="background: yellow none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">>FLEX can be driven entirely
from data.<span style=""> </span>Could Seam and Rich Faces be
used this way?</span><o:p></o:p></b></p>
<p class="MsoNormal">Sure. Did you have any chance to look at <span style="font-size: 11pt;"><a href="https://www.jboss.org/community/docs/DOC-12952" target="_blank">https://www.jboss.org/community/docs/DOC-12952</a>
(especially <span style="font-weight: bold;">RichFaces live demo links</span> and RichFaces UI components - <a href="http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/docs/devguide/en/html/RichFacesComponentsLibrary.html">http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/docs/devguide/en/html/RichFacesComponentsLibrary.html</a>
)? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-weight: bold;">Seam + JSF API + Facelets</span> (XHTML templating)+ <span style="font-weight: bold;">RichFaces</span> (JSF
impl) are very flexible, have extension points and can implement majority of
RIA use cases (including an integration with plenty of other frameworks that
I’ve mentioned on the wiki page). <br></p><p class="MsoNormal"><br></p><p class="MsoNormal"><span style="font-weight: bold;">Seam/JSF/RichFaces</span> integrated with other RIA frameworks like <span style="font-weight: bold;">JQuery</span> - <a href="http://jquery.com">http://jquery.com</a>. Exadel proved that it is possible to integrate <span lang="EN-US"><strong>Flex and JavaFX</strong> with <span style="font-weight: bold;">JBoss Seam</span> </span>(<span lang="EN-US"><a class="jive-link-external-small" href="http://exadel.com/web/portal/flamingo">Exadel Flamingo</a> and </span><span lang="EN-US"> <a class="jive-link-external-small" href="http://exadel.com/web/portal/fiji">Exadel Fiji</a></span>) - this addresses your concerns about "<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word
11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Csergiy%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
</w:LatentStyles>
</xml><![endif]--><style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;
mso-header-margin:36.0pt;
mso-footer-margin:36.0pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
</style>
<![endif]--><span style="font-size: 12pt; font-family: "Times New Roman";">allowing graphical navigation</span>".<br></p><p class="MsoNormal"><br></p><p class="MsoNormal">However some “glue” code might be needed
depending of specific use case(s) – or we can make it generic.<span style=""> </span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In fact, <span style="font-weight: bold;">Seam/JSF/RichFaces</span> frameworks are very similar to <span style="font-weight: bold;">Flex</span> by
functionality but RichFaces/JSF relying on more generic, widely sources like
(X)HTML, JS, <st1:place w:st="on"><st1:city w:st="on">AJAX</st1:city></st1:place>,
CSS.<span style=""> </span>For example, both frameworks using
view described in XML; <b style="">data binding</b>
in Flex (<a href="http://www.adobe.com/devnet/flex/quickstart/using_data_binding/">http://www.adobe.com/devnet/flex/quickstart/using_data_binding/</a>)
is almost identical to JSF. For example, an input text UI control described as following:</p>
<pre><span class="mxmlcomponent"><o:p> </o:p></span></pre><pre><span class="mxmlcomponent">FLEX: <span style=""> </span><mx:Text</span> text="<span class="mxmlstring">{</span>myData.value<span class="mxmlstring">}</span>"<span class="mxmlcomponent">/><o:p></o:p></span></pre>
<p class="MsoNormal">Pure JSF: <span style=""> </span><span style=""> </span><h:inputText value="#{myData.value}"/><span style=""> </span></p>
<pre>RichFaces: <span style=""> </span><span class="xmltagsymbols"><</span><span class="xmltagname">rich:inplaceInput</span><span class="xmlplain"> </span><span class="xmlattributename">value</span><span class="xmltagsymbols">=</span><span class="xmlattributevalue">"#{</span>myData.value<span class="xmlattributevalue">}"</span><span class="xmltagsymbols">/></span></pre>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Plus we can combine Flex + JSF too if needed.</p>
<p class="MsoNormal">IMO, what we should do first – regardless of preferred UI
choice - is that we would need to <b style="">define
few critical/major use cases</b> <b style="">in
details</b> in terms of <b style="">pure
requirements</b> (e.g. using language not specific to view frameworks) and
generic UI controls. And then see how it fits onto features of available
frameworks. This would help to understand what is really needed and jumpstart
on development of web app infrastructure.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">><b style=""><span style="background: yellow none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"> What if we put the REST service
on top of the Graph API (new to 0.3), which operates on top of a connector</span>?<o:p></o:p></b></p>
<p class="MsoNormal">I agree that we need to consider both approaches side by
side and they impact on REST service implementation, and agree that both
mapping types might be twin brothers. So why don't we have core semi abstract class(es) that handles REST requiests based of <a href="http://jcp.org/en/jsr/detail?id=311">http://jcp.org/en/jsr/detail?id=311</a> annotations and JBoss RestEasy implementation. And then two direct implementations based on Graph API (preffered?) and on JNDI/JCR API. <br></p>
<p class="MsoNormal"><u><o:p><span style="text-decoration: none;"> </span></o:p></u></p>
<p class="MsoNormal"><b style=""><u>Basic question #1 to
answer</u></b>: is REST service shall be considered an external component of
JBoss DNA that threat it as another JCR repository (black box), or is it
integrated part of DNA with some knowledge of internal processing/model? </p>
<p class="MsoNormal">BTW, same question is valid for other services (reporting,
analysis, etc), Web UI application.</p>
<p class="MsoNormal"><b style=""><u><o:p><span style="text-decoration: none;"> </span></o:p></u></b></p>
<p class="MsoNormal"><b style=""><u>Basic question #2 to
answer</u></b>: shall we consider using Graph API for REST service, where we’ll
stop? In other words, do we need to use JCR API at all for components?<span style=""> </span>What the boundaries between internal engine’s
code, and services. </p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">IMO, we could use Graph API if it covers all traversal
access provided by JCR API + <b style="">Query API</b>
(provided by JCR)? IMO, this bit is as much as important as federated tree of
nodes + traversal. It helps client to quickly find an important metadata in a
same way like Google does for internet search.</p>
<p class="MsoNormal">The clear advantage of using Graph API is that it can
provide some functionality behind the JCR API coverage.</p>
<p class="MsoNormal">On the other hand, considering that Graph API is the “core engine”
of JCR implementation, I doubt that using JCR API on top of Graph API will have
any visible impact on a performance (since JCR layer is extra thin and just
converts JCR call to Graph API call(s)). <span style=""> </span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I like an idea using Graph API but worrying about question
#2.</p>
</div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Randall Hauch <rhauch@redhat.com><br><b><span style="font-weight: bold;">To:</span></b> Sergey Litsenko <litsenko_sergey@yahoo.com>; JBoss DNA <dna-dev@lists.jboss.org><br><b><span style="font-weight: bold;">Sent:</span></b> Monday, 17 November, 2008 4:24:48 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [dna-dev] Re: JBoss DNA 0.4 planning<br></font><br><br><div><div>On Nov 16, 2008, at 4:25 AM, Sergey Litsenko wrote:</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><div style="margin: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"><b>Regarding JDBC metadata</b>.</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">...</div></div></div></div></span></blockquote><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div><div style="margin: 0px; font-family: 'times new roman','new
york',times,serif; font-size: 12pt;"><div style="margin: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">1) I'll review new chapter "how to write custom connectors"and use the<span class="Apple-converted-space"> </span><b>dna-connector-svn</b><span class="Apple-converted-space"> </span>as a reference to implement the<span class="Apple-converted-space"> </span><b>dna-connector-jdbc<span class="Apple-converted-space"> </span></b>in<b><span class="Apple-converted-space"> </span></b>extensions<b>.<span class="Apple-converted-space"> </span></b>It will<b><span class="Apple-converted-space"> </span>accept<span class="Apple-converted-space"> </span></b>two configuration styles to specify JDBC configuration<b><span class="Apple-converted-space"> </span>- javax.sql.DataSource<span class="Apple-converted-space"> </span></b>and<b><span
class="Apple-converted-space"> </span></b>more generic<b><span class="Apple-converted-space"> </span>java.sql.Driver<span class="Apple-converted-space"> </span></b>(connection URL, username/password, etc).<span class="Apple-converted-space"> </span></div></div></div></div></span></blockquote><div><br></div><div>Maybe this would help or give you some ideas: this weekend I've created a prototype connector that uses Hibernate for persistent storage. (Not quite ready for committing to SVN, but should be this week). The RepositorySource implementation just has JavaBean properties for the regular connection properties for Driver-based connection, and another JavaBean property for the JNDI name of the DataSource. The RepositorySource has a transient Hibernate Ejb3Configuration, which it creates lazily (and stores as a transient attribute) before creating a RepositoryConnection. The Ejb3Configuration is created
programmatically, so the Driver properties are set as properties, but the DataSource has to be set as a reference. (Yeah, the JNDI name could be set as a Ejb3Configuration property, but in order to support the XAResource, I need to get the DataSource object in the RepositorySource, which holds onto it via a transient attribute. This works with Hibernate, since the config also has a setDataSource(DataSource) method. Oh, and to make testing easier (by eliminating requirement for JNDI), I also added a package-level setter for a DataSource object, which sets the transient attribute value. Let me know if you want to see code.</div><div><br></div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><div style="margin: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">2) create<span> <span class="Apple-converted-space"> </span></span><b>dna-sequencer-jdbc-metadata</b><span class="Apple-converted-space"> </span>subproject in extensions that will implement an interface<span class="Apple-converted-space"> </span><b>similar to</b><span class="Apple-converted-space"> </span>org.jboss.dna.graph.sequencers.<b>StreamSequencer</b><span class="Apple-converted-space"> </span>except for the “stream” input parameter because it is irrelevant for JDBC based conversations:</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New Roman';">package org.jboss.dna.graph.sequencers;</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">public interface JdbcSequencer {</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"><span> <span class="Apple-converted-space"> </span></span>void sequence(java.sql.Connection jdbcConnection,</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"><span> <span class="Apple-converted-space"> </span></span>SequencerOutput output,</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman';"><span> <span class="Apple-converted-space"> </span></span>SequencerContext context);</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">}</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">The main purpose – is to make it generic enough to allow implementing different JDBC sequencers.</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">How it sounds?<span class="Apple-converted-space"> </span><span> </span><span> </span><span> </span></div></div></div></div></span></blockquote><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0);
font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><div style="margin: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">Basically, what I need to do is to port my<span class="Apple-converted-space"> </span><b>DatabaseMetadata Extractor</b><span class="Apple-converted-space"> </span>(I did it few years ago, and tested against Oracle9i, MS SQL Server 2005, and MySQL) into org.jboss.dna space. The extractor as whole package is a bit too heavy to just simply copy it – it is relying on several
Apache\Jacarta libraries (notably on Jacarta commons<span class="Apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://commons.apache.org/chain/" style="color: blue; text-decoration: underline;">Chain</a><span class="Apple-converted-space"> </span>(Chain of Responsibility" pattern) + generates JDBC drivers comparison reports in XML and HTML. So, I’m trying to refactor it in the same time.<span class="Apple-converted-space"> <span class="Apple-style-span" style="color: rgb(20, 79, 174); font-size: 12px;"> </span></span></div></div></div></div></span></blockquote><div><br></div><div><div>Okay, I think I see what you're trying to do. Very interesting idea. This would all be in the connector, then? And the connector would essentially cache the metadata graph extracted from the database metadata, so it could respond to the different ReadNodeRequest (or other requests) coming into the connector?
(If I don't have this right, please let me know.) Also, if you're refactoring the extractor, would it be possible for the extractor to be used directly the connector to obtain only part of the metadata? </div><div><br></div><div>BTW, the musings I've had in the past about this connector is that it might use Hibernate (to automatically get support for the many database management systems that Hibernate already supports; see <a rel="nofollow" target="_blank" href="http://www.hibernate.org/80.html%29">http://www.hibernate.org/80.html</a>). Hibernate Tool's DatabaseMetadata class works on top of the many dialects that Hibernate has (<a rel="nofollow" target="_blank" href="http://www.hibernate.org/hib_docs/v3/api/org/hibernate/tool/hbm2ddl/DatabaseMetadata.html">http://www.hibernate.org/hib_docs/v3/api/org/hibernate/tool/hbm2ddl/DatabaseMetadata.html</a>). Again, not sure if this would even work or provide everything we'd
want. For example, it may not provide much (if any) of the database-specific metadata.</div><div><br></div><div><br></div></div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><div style="margin: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"><b>Regarding REST mapping</b>. My intention was to just describe “<i>prior art</i>” for reference purposes only – let others to they work - while
it sounds like Jerome K. Jerome’s famous quote about his addiction to work ;) - we may save more time on analysis of possible REST mapping strategies.</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">My point is simple (and btw, it didn’t changed for years) – “<i>program to interfaces</i>”, likely standards based and setup transparent links (inject, configure, etc) to open source software implementations (preferably) of those interfaces where appropriate and possible.</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 12pt; font-family: 'Times New Roman';">I’m completely agree with your comments on that, and even more – inspired by your feeling towards choosing right balance
between writing own code and reusing available libraries and frameworks I decided to spend some time analysing possible choices and wrote a wiki page about<span class="Apple-converted-space"> </span><b>prospective ways</b><span class="Apple-converted-space"> </span>to integrate/implement various JBoss DNA components in the future. Basically its small review of technologies available in<span class="Apple-converted-space"> </span> OSS community (especially in JBOSS community) that might be related to JBoss DNA concept and might be reused in its implementation – have a look at it here<span class="Apple-converted-space"> </span><a rel="nofollow" target="_blank" href="https://www.jboss.org/community/docs/DOC-12952" style="color: blue; text-decoration: underline;">https://www.jboss.org/community/docs/DOC-12952</a><span class="Apple-converted-space"> </span>– your comments are greatly appreciated. The<span
class="Apple-converted-space"> </span><b>main purpose of that review was to make the DNA implementation technology(s) / framework(s) choices broader and to address time to market requirement<span class="Apple-converted-space"> </span></b>(while I love those frameworks and JEE in particular - I don’t want to push it too hard). The bottom line is that one of the main JBoss DNA/JCR and JBoss DNA/Web purposes shall be to simplify metadata management things, not to complicate them – from client prospective. Plus (I guess) serve as JBoss technology stack show case (to some reasonable degree).</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">So, basically we will stick with JCR API for traversal, search, update nodes and map it onto URL, right?</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt;
font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">The beauty of JCR API is that we don’t need to wait till our JCR implementation will be ready to integrate with other frameworks or services. As long as all components will rely strictly on JCR API interfaces and access it through standard way (e.g. JNDI lookup, dependency injection, etc) – we can easily use JackRabbit embedded in a meantime, and then substitute it with our JCR implementation when it became ready. We would need to address performance limitations of JackRabbit in our implementation of JCR API – in order to make it better (since it mean to be enterprise wide repository – e.g. thousands of nodes, subnodes, properties).</div></div></div></div></span></blockquote><div><br></div><div>Yes, that is an entirely valid, and maybe preferred approach. Yes, we could start working on the REST service
today. But a disadvantage is that we couldn't use the REST API on top of DNA repositories until our JCR API was finished (or at least those parts that the REST service would use).</div><div><br></div><div>Also, it doesn't seem like the REST service would use much of the JCR API. (Yes, this may make it easier to get our JCR implementation complete enough to put the REST service on top of DNA repositories.) But are we making it more complicated than it needs to be? What if we put the REST service on top of the Graph API (new to 0.3), which operates on top of a connector. This is essentially all that our JCR implementation is doing. The Graph API can read and write today, and it basically just consists of nodes with properties and children. And my intuition (nothing more than that!) is that the REST mapping to JCR would also map similarly/identically to the Graph API. The benefit is that this would be more
efficient, since the extra JCR layer is eliminated.</div><div><br></div><div>I'm not sure what my preference would be. Both have advantages and disadvantages. But maybe we could consider both before we decide. Anyone have thoughts here?</div><div><br></div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><div style="margin: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">I have the
same opinion like you that RESTful service in not the equal to web app UI.<span class="Apple-converted-space"> </span><span> </span>We need separate JIRA ticket(s) for Web UI app, each panned/proposed WS (e.g.<span class="Apple-converted-space"> </span><a rel="nofollow" target="_blank" href="https://jira.jboss.org/jira/browse/DNA-55" style="color: blue; text-decoration: underline;"></a><a rel="nofollow" target="_blank" href="https://jira.jboss.org/jira/browse/DNA-55" style="color: blue; text-decoration: underline;"><span style="text-decoration: none;">REST-based API for remote access and usage</span></a>).</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">Also, we would need to<span class="Apple-converted-space"> </span><b>clarify deployment scenarios</b><span
class="Apple-converted-space"> </span>of JBoss DNA stack in detail (like JackRabbit’s team did) – also highlighted on my wiki page.</div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"> </div><div style="margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 12pt; font-family: 'Times New Roman';"><b>Regarding Web application UI</b>.<span> <span class="Apple-converted-space"> </span></span>I’m not against Flex as one of possible UI rendering but I’m just not sold on the fact that Flex is the first or preferable choice for DNA UI. Reasons explained in more detail on the s<a rel="nofollow" target="_blank" href="https://www.jboss.org/community/docs/DOC-12952" style="color: blue; text-decoration: underline;">ame wiki page</a><span class="Apple-converted-space"> </span>– but
basically it is all about<span class="Apple-converted-space"> </span><b>infrastructure and technology/feature enablers</b><span class="Apple-converted-space"> </span><b>that btw already part of JBoss stack.</b><span class="Apple-converted-space"> </span>For instance, thin and rich JSF framework like<span class="Apple-converted-space"> </span><b>RichFaces<span class="Apple-converted-space"> </span></b>that nicely integrates with<b><span class="Apple-converted-space"> </span>JBoss Seam<span class="Apple-converted-space"> </span></b>as a web infrastructural component might implement all required UI functionality. It is easy to use, understand how it works (both projects have comprehensive documentation) + my past experience with both frameworks might help in setting up quickly web infrastructure for JBoss DNA web.<span
class="Apple-converted-space"> </span></div></div></div></div></span></blockquote><div><br></div><div>I would agree that it's very important for other technologies (like Seam, RichFaces, GWT, even plain-old JSPs) to use JBoss DNA, because people writing web applications should be able to use JBoss DNA. However, I believe that we also need to provide an out-of-the-box ready-to-use metadata management repository web application, and that this will likely need to be offer rich interaction model (maybe even allowing graphical navigation). But perhaps the most critical need is for the application to over ways of customizing and extending how it views information, by not changing the application but by adding/changing data. This is content-driven, and not many frameworks make this possible. For example, GWT does not, since everything must be coded in Java and then compiled into the application. FLEX can be driven entirely
from data. Could Seam and Rich Faces be used this way?</div><div><br></div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><div style="margin: 0px;"><div style="margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 12pt; font-family: 'Times New Roman';"><br></div><div style="margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 12pt; font-family: 'Times New Roman';"><br></div><div style="margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 12pt; font-family: 'Times New Roman';">Best regards,</div><div style="margin: 0cm 0cm
0.0001pt; text-align: justify; font-size: 12pt; font-family: 'Times New Roman';"> Sergiy<br></div></div><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><br><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b><span class="Apple-converted-space"> </span>Randall Hauch <<a rel="nofollow" ymailto="mailto:rhauch@redhat.com" target="_blank" href="mailto:rhauch@redhat.com" style="color: blue; text-decoration: underline;">rhauch@redhat.com</a>><br><b><span style="font-weight: bold;">To:</span></b><span class="Apple-converted-space"> </span>Sergey Litsenko <<a rel="nofollow" ymailto="mailto:litsenko_sergey@yahoo.com" target="_blank" href="mailto:litsenko_sergey@yahoo.com" style="color: blue; text-decoration:
underline;">litsenko_sergey@yahoo.com</a>>; JBoss DNA <<a rel="nofollow" ymailto="mailto:dna-dev@lists.jboss.org" target="_blank" href="mailto:dna-dev@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev@lists.jboss.org</a>><br><b><span style="font-weight: bold;">Sent:</span></b><span class="Apple-converted-space"> </span>Tuesday, 11 November, 2008 2:57:38 AM<br><b><span style="font-weight: bold;">Subject:</span></b><span class="Apple-converted-space"> </span>Re: [dna-dev] Re: JBoss DNA 0.4 planning<br></font><br><div style="margin: 0px;">Excellent! Can't wait to see what you have. You're right that we could code to JSR 311 and use any valid implementation, but I have no problem relying upon RESTeasy, since we could leverage new features (e.g., <a rel="nofollow" target="_blank" href="http://bill.burkecentral.com/2008/11/10/jax-rs-atom-support-with-resteasy/" style="color: blue; text-decoration:
underline;">http://bill.burkecentral.com/2008/11/10/jax-rs-atom-support-with-resteasy/</a>), and since the RESTful service would certainly be packaged to run in a servlet container and thus shouldn't have any problems with clashes in dependencies. Plus, RESTeasy is another JBoss technology.</div><div style="margin: 0px;"><br></div><div style="margin: 0px;">I'm wondering if you meant to say a JDBC Metadata "connector" (rather than "sequencer"). If you did mean "sequencer", I'd be interested in hearing about how that might work (what might be sequenced so the sequencer knows how to establish the connection and retrieve the metadata).</div><div style="margin: 0px;"><br></div><div style="margin: 0px;">Now, regarding a REST mapping. I've looked at Sling (which has other features besides just a REST service), and based upon the documentation (which may very well be out of date), the client specifies the content type in the URL - that's not
very appealing. I would much rather see standard content negotiation via the standard accept header. Now, the other two examples don't always look very RESTful (or at least "resource oriented"). For example, Alfresco's REST API's login method (<a rel="nofollow" target="_blank" href="http://wiki.alfresco.com/wiki/Repository_RESTful_API_Reference#Login" style="color: blue; text-decoration: underline;">http://wiki.alfresco.com/wiki/Repository_RESTful_API_Reference#Login</a>) uses GET even though it's not idempotent. POST would seem to be better here. I would love to see a more detailed discussion on the REST mapping. Perhaps you could start off with what you've used in your prototype?</div><div style="margin: 0px;"><br></div><div style="margin: 0px;">Another important topic is this: will we want to build a content-driven application framework or will we want to use Sling or Alfresco's WebScripts (or other)? Some
advantages of reusing an existing system are: </div><ul class="MailOutline"><li>more functionality out of the box (i.e., we're not 1+ years behind)</li><li>reuse existing technology</li><li>leveraging existing community and possibly expand DNA community via participation in the other community</li></ul><div style="margin: 0px;">There are probably others, too. Some disadvantages are:</div><div style="margin: 0px;"><ul class="MailOutline"><li>must choose a technology</li><li>must live with their interface and design</li><li>little or no value-add over the existing technology</li><li>our JCR support must be close-to-complete before we can do this</li></ul><div style="margin: 0px;"><br></div><div style="margin: 0px;">I'm a bit conflicted: I think we could do better, but just because we can doesn't mean we should. There's something to be said about focusing on what makes DNA unique and advantageous (primarily federation and sequencing), and
just using Sling or Alfresco to build out some great useable applications. In fact, I think that a really usable and really useful content-driven rich internet application (perhaps using Flex) is another potential focus area for DNA. </div><div style="margin: 0px;"><br></div><div style="margin: 0px;">So, as long as as have a correct and complete (enough) JCR implementation, then we (or anyone else) should be able to use DNA in combination with Sling and/or Alfresco. We may even win over the Alfresco community, if DNA's repository implementation is better than Jackrabbit. (Jackrabbit does a lot of things well, but there are some things it doesn't do well. All we need to do is be better at how Alfresco uses JCR.)</div><div style="margin: 0px;"><br></div><div style="margin: 0px;">Now, having said that, I think that a RESTful service is not the same as a content-driven application framework. I think DNA should offer
a lightweight, full-functioning RESTful service that doesn't depend on the larger content-driven applications. After all, I think many embedded use cases will simply want a deployable RESTful service so that client apps can work with a remote (federated) repository. And I think we can achieve this with very little code using RESTeasy (or maybe even other JSR-311 implementations). So we definitely need to do this.</div><div style="margin: 0px;"><br></div><div style="margin: 0px;"><br></div></div><div style="margin: 0px;">Best regards,</div><div style="margin: 0px;"><br></div><div style="margin: 0px;">Randall</div><br><div style="margin: 0px;"><div style="margin: 0px;">On Nov 10, 2008, at 6:04 AM, Sergey Litsenko wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div style="margin: 0px;"><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><div style="margin: 0px;">Hi All,<br> I've already started working on (not yet in SVN - will wait till 0.3 release):<br> 1) JDBC Metadata sequencer (POJO model is ready, working on extraction of metadata)<br><span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN"> 2) JAX-RS prototype.<span class="Apple-converted-space"> </span><br> IMO, we would need to start working on REST mapping for JCR resources.<span class="Apple-converted-space"> </span></span><span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN">Basicaly, any implementation of <span
class="Apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://jcp.org/en/jsr/summary?id=311" style="color: blue; text-decoration: underline;">http://jcp.org/en/jsr/summary?id=311</a><span class="Apple-converted-space"> </span>may be used as a core of the REST-JCR integration (RestEasy?)</span><br><span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN"> There are at least few available implementations exists that we may review:<br> 1) Sling project<span class="Apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://incubator.apache.org/sling/site/resources.html#Resources-JCRbasedResources%29" style="color: blue; text-decoration: underline;">http://incubator.apache.org/sling/site/resources.html#Resources-JCRbasedResources)</a><span class="Apple-converted-space"> </span><br> 2) Alfresco REST API for JCR at<span class="Apple-converted-space"> </span><a
rel="nofollow" target="_blank" href="http://wiki.alfresco.com/wiki/HTTP_API#Alfresco_RESTful_API_Reference" style="color: blue; text-decoration: underline;">http://wiki.alfresco.com/wiki/HTTP_API#Alfresco_RESTful_API_Reference</a><br> 3)<span class="Apple-converted-space"> </span></span><span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN">Alfresco <span class="Apple-converted-space"> </span></span>Content Management Interoperability Services (<span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN">CMIS) API <span class="Apple-converted-space"> </span></span><span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN"><a rel="nofollow" target="_blank" href="http://wiki.alfresco.com/wiki/CMIS_Web_Scripts_Reference" style="color: blue; text-decoration: underline;">http://wiki.alfresco.com/wiki/CMIS_Web_Scripts_Reference</a><br><br>It would be nice to see<span
class="Apple-converted-space"> </span></span><span style="font-size: 12pt;" lang="EN">as one of future features of DNA<span class="Apple-converted-space"> </span></span><span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN"><span style="font-weight: bold;">auto-discovery (zeroconf)</span><span class="Apple-converted-space"> </span>of some<span class="Apple-converted-space"> </span></span><span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN">resources<span class="Apple-converted-space"> </span></span><span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN">as well as DNA repository self advertizing<span class="Apple-converted-space"> </span></span><span style="font-size: 12pt; font-family: 'Times New Roman';" lang="EN">(for example -<span class="Apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://activemq.apache.org/zeroconf.html%29"
style="color: blue; text-decoration: underline;">http://activemq.apache.org/zeroconf.html)</a>.<span class="Apple-converted-space"> </span><br><br></span></div><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;">Best regards,<br>Sergiy<br><div style="margin: 0px; font-family: arial,helvetica,sans-serif; font-size: 13px;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b><span class="Apple-converted-space"> </span>"<a rel="nofollow" ymailto="mailto:dna-dev-request@lists.jboss.org" target="_blank" href="mailto:dna-dev-request@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev-request@lists.jboss.org</a>" <<a rel="nofollow" ymailto="mailto:dna-dev-request@lists.jboss.org" target="_blank" href="mailto:dna-dev-request@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev-request@lists.jboss.org</a>><br><b><span
style="font-weight: bold;">To:</span></b><span class="Apple-converted-space"> </span><a rel="nofollow" ymailto="mailto:dna-dev@lists.jboss.org" target="_blank" href="mailto:dna-dev@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev@lists.jboss.org</a><br><b><span style="font-weight: bold;">Sent:</span></b><span class="Apple-converted-space"> </span>Thursday, 6 November, 2008 4:00:27 AM<br><b><span style="font-weight: bold;">Subject:</span></b><span class="Apple-converted-space"> </span>dna-dev Digest, Vol 8, Issue 3<br></font><br>Send dna-dev mailing list submissions to<br> <span class="Apple-converted-space"> </span><a rel="nofollow" ymailto="mailto:dna-dev@lists.jboss.org" target="_blank" href="mailto:dna-dev@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev@lists.jboss.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <span
class="Apple-converted-space"> </span><a rel="nofollow" target="_blank" href="https://lists.jboss.org/mailman/listinfo/dna-dev" style="color: blue; text-decoration: underline;">https://lists.jboss.org/mailman/listinfo/dna-dev</a><br>or, via email, send a message with subject or body 'help' to<br> <span class="Apple-converted-space"> </span><a rel="nofollow" ymailto="mailto:dna-dev-request@lists.jboss.org" target="_blank" href="mailto:dna-dev-request@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev-request@lists.jboss.org</a><br><br>You can reach the person managing the list at<br> <span class="Apple-converted-space"> </span><a rel="nofollow" ymailto="mailto:dna-dev-owner@lists.jboss.org" target="_blank" href="mailto:dna-dev-owner@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev-owner@lists.jboss.org</a><br><br>When replying, please edit your Subject line
so it is more specific<br>than "Re: Contents of dna-dev digest..."<br><br><br>Today's Topics:<br><br> 1. Preparing for the 0.3 release (Randall Hauch)<br> 2. JBoss DNA 0.4 planning (Randall Hauch)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 4 Nov 2008 12:18:59 -0600<br>From: Randall Hauch <<a rel="nofollow" ymailto="mailto:rhauch@redhat.com" target="_blank" href="mailto:rhauch@redhat.com" style="color: blue; text-decoration: underline;">rhauch@redhat.com</a>><br>Subject: [dna-dev] Preparing for the 0.3 release<br>To: JBoss DNA <<a rel="nofollow" ymailto="mailto:dna-dev@lists.jboss.org" target="_blank" href="mailto:dna-dev@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev@lists.jboss.org</a>><br>Message-ID: <<a rel="nofollow" ymailto="mailto:92A505A6-0D05-47BF-813B-438181005D27@redhat.com" target="_blank"
href="mailto:92A505A6-0D05-47BF-813B-438181005D27@redhat.com" style="color: blue; text-decoration: underline;">92A505A6-0D05-47BF-813B-438181005D27@redhat.com</a>><br>Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes<br><br>We're down to just a handful of outstanding issues targeted to 0.3, <span class="Apple-converted-space"> </span><br>and all of the big fish issues were completed. I'll be working my two <span class="Apple-converted-space"> </span><br>issues over the next few days, but I should be ready for releasing as <span class="Apple-converted-space"> </span><br>early as this week. Serge has the other outstanding issues, which are <span class="Apple-converted-space"> </span><br>all regarding the SVN connector. Serge, where do we stand on this? <span class="Apple-converted-space"> </span><br>Do you want more time to get some functionality finished, or is
the <span class="Apple-converted-space"> </span><br>connector fairly close?<br><br>Anybody else have anything to discuss?<br><br>Best regards,<br><br>Randall<br><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 4 Nov 2008 12:37:05 -0600<br>From: Randall Hauch <<a rel="nofollow" ymailto="mailto:rhauch@redhat.com" target="_blank" href="mailto:rhauch@redhat.com" style="color: blue; text-decoration: underline;">rhauch@redhat.com</a>><br>Subject: [dna-dev] JBoss DNA 0.4 planning<br>To: JBoss DNA <<a rel="nofollow" ymailto="mailto:dna-dev@lists.jboss.org" target="_blank" href="mailto:dna-dev@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev@lists.jboss.org</a>><br>Message-ID: <<a rel="nofollow" ymailto="mailto:9643F3D3-5E3F-4219-A492-6BC1F6196C73@redhat.com" target="_blank" href="mailto:9643F3D3-5E3F-4219-A492-6BC1F6196C73@redhat.com" style="color: blue; text-decoration:
underline;">9643F3D3-5E3F-4219-A492-6BC1F6196C73@redhat.com</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>Now that 0.3 is almost out the door, I'd like to start discussing the <span class="Apple-converted-space"> </span><br>goals for the next release.<br><br>I'd love to see the JCR implementation take more shape. Right now <span class="Apple-converted-space"> </span><br>it's read-only, so getting that much farther along would be <span class="Apple-converted-space"> </span><br>outstanding. Anybody interested? I think we could easily put several <span class="Apple-converted-space"> </span><br>people to work here. The graph API is pretty good, and should make <span class="Apple-converted-space"> </span><br>implementing JCR relatively straightforward. Any interest, Michael <span class="Apple-converted-space"> </span><br>Trezzi and Alexandre and
Serge?<br>We need to add events to the connector framework. That should be <span class="Apple-converted-space"> </span><br>pretty straightforward. Also versioning, which will require a bit <span class="Apple-converted-space"> </span><br>more work. Plus, there are a couple of connectors that we may want to <span class="Apple-converted-space"> </span><br>start working on. This is something I'd be happy to continue with. <span class="Apple-converted-space"> </span><br>Serge P. also has expressed interest in working on some connectors (in <span class="Apple-converted-space"> </span><br>fact his SVN connector is coming along great!).<br>The CND sequencer could use some love and attention. Dan was stuck in <span class="Apple-converted-space"> </span><br>some ANLTR hell, and got pulled off onto a different project. Since <span
class="Apple-converted-space"> </span><br>it uses ANTLR, maybe you might be interested in it, Alexandre?<br>We also have a need to start working on a REST/WebDAV layer that <span class="Apple-converted-space"> </span><br>allows other client apps to access a DNA repository. There's a couple <span class="Apple-converted-space"> </span><br>of things we can do, including looking at Apache Sling, or using <span class="Apple-converted-space"> </span><br>RESTeasy for a more simple implementation, or something else. Sergiy <span class="Apple-converted-space"> </span><br>and John both expressed interest in this.<br><br>Anything else?<br><br>We can either tackle several things at once and move them all <span class="Apple-converted-space"> </span><br>incrementally, or we can do more in just a few areas. Ideally, we're <span class="Apple-converted-space"> </span><br>looking at a 4-5
week cycle (finishing before the year-end holidays.) <span class="Apple-converted-space"> </span><br>A lot will depend on how much effort people might be able to dedicate <span class="Apple-converted-space"> </span><br>to the project.<br><br>Please respond with your thoughts and comments!<br><br>Best regards,<br><br>Randall<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<span class="Apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://lists.jboss.org/pipermail/dna-dev/attachments/20081104/90ff822f/attachment-0001.html" style="color: blue; text-decoration: underline;">http://lists.jboss.org/pipermail/dna-dev/attachments/20081104/90ff822f/attachment-0001.html</a><br><br>------------------------------<br><br>_______________________________________________<br>dna-dev mailing list<br><a rel="nofollow" ymailto="mailto:dna-dev@lists.jboss.org" target="_blank"
href="mailto:dna-dev@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev@lists.jboss.org</a><br><a rel="nofollow" target="_blank" href="https://lists.jboss.org/mailman/listinfo/dna-dev" style="color: blue; text-decoration: underline;">https://lists.jboss.org/mailman/listinfo/dna-dev</a><br><br><br>End of dna-dev Digest, Vol 8, Issue 3<br>*************************************<br></div></div></div><br><p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';"></p><div class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; text-align: center; font-size: 12pt; font-family: 'Times New Roman';" align="center"><font size="3" face="Arial"><span style="font-size: 12pt;"><hr size="1" width="100%" align="center"></span></font></div><div style="margin: 0px; font-size: 12pt; font-family: 'Times New Roman';"><img id="_x0000_i1026" width="25" align="absbottom" border="0" height="25" hspace="4"><font
size="2" face="Arial">Search 1000's of available singles in your area at the new Yahoo!7 Dating.<span class="Apple-converted-space"> </span><span style="font-size: 10pt;"><a rel="nofollow" target="_blank" href="http://au.rd.yahoo.com/dating/mail/tagline2/*http://au.dating.yahoo.com/?cid=53151&pid=1012" style="color: blue; text-decoration: underline;"><b><span style="font-weight: bold;" lang="NO-BOK"></span></b><span lang="NO-BOK">Get Started.</span></a></span></font><span lang="NO-BOK"></span></div>_______________________________________________<br>dna-dev mailing list<br><a rel="nofollow" ymailto="mailto:dna-dev@lists.jboss.org" target="_blank" href="mailto:dna-dev@lists.jboss.org" style="color: blue; text-decoration: underline;">dna-dev@lists.jboss.org</a><br><a rel="nofollow" target="_blank" href="https://lists.jboss.org/mailman/listinfo/dna-dev" style="color: blue; text-decoration:
underline;">https://lists.jboss.org/mailman/listinfo/dna-dev</a><br></div></span></blockquote></div><br></div></div></div><br><hr size="1">Make the switch to the world's best email.<span class="Apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://au.rd.yahoo.com/mail/taglines/au/mail/default/*http://au.yahoo.com/y7mail" style="color: blue; text-decoration: underline;">Get Yahoo!7 Mail</a>.</div></span></blockquote></div><br></div></div></div><br>
<hr size=1> Make the switch to the world's best email.
<a href="http://au.rd.yahoo.com/mail/taglines/au/mail/default/*http://au.yahoo.com/y7mail">Get Yahoo!7 Mail</a>.</body></html>