<?xml version="1.0" encoding="utf-8"?>

<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
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:cc="http://web.resource.org/cc/"
xmlns="http://purl.org/rss/1.0/">

<channel rdf:about="http://weblogs.java.net/blog/boneill42/">
<title>Brian O&apos;Neill&apos;s Blog</title>
<link>http://weblogs.java.net/blog/boneill42/</link>
<description></description>
<dc:language>en-us</dc:language>
<dc:creator></dc:creator>
<dc:date>2008-04-07T19:34:15-08:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.01D" />


<items>
<rdf:Seq><rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2008/04/what_ruby_could.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2008/03/is_j2ee_dead_1.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/12/philly_emerging.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/09/communications_1.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/09/esbs_the_value.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/08/an_open_technol.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/08/jbi_catch_the_s.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/07/how_jbi_can_imp.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/07/jbi_application_1.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/06/sca_jbi_made_fo.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/06/jbi_not_just_fo.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/06/jbi_as_a_conver.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2007/06/soa_esb_jbi_sca_1.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2006/12/source_equity_m.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/boneill42/archive/2004/04/web_services_sl.html" />
</rdf:Seq>
</items>

</channel>

<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2008/04/what_ruby_could.html">
<title>What Ruby could learn from Java (and a bit of the vice-versa), is it time for a Ruby Community Process?</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2008/04/what_ruby_could.html</link>
<description>Ruby works on a much different development cycle, that relies on the code itself for documentation, and the blogosphere for consensus.  This works well for rapidly developed low-risk projects, but is it right for the enterprise?</description>
<dc:subject>Community</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2008-04-07T19:34:15-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2008/03/is_j2ee_dead_1.html">
<title>Is J2EE Dead?</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2008/03/is_j2ee_dead_1.html</link>
<description>Traditional web application development may be better suited to languages that afford more agile development (e.g. Ruby on Rails) and enterprise application integration needs a SOA &amp; ESB approach (backed by a messaging-system).  This approach isn&apos;t/wasn&apos;t the central focus of J2EE, which may just leave it out in the cold, whilst the younger up and coming specs take the reins.</description>
<dc:subject>Community: Java Enterprise</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2008-03-03T08:30:10-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/12/philly_emerging.html">
<title>Philly Emerging Technologies Event</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/12/philly_emerging.html</link>
<description>Philly Emerging Technologies Event: Call for Papers!</description>
<dc:subject>Community</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-12-06T07:04:35-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/09/communications_1.html">
<title>Communications Binding Components get upgrades</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/09/communications_1.html</link>
<description>The xmpp-bc and sip-bc projects just released new versions (0.9.1) of their binding components, now with new and improved collaboration capabilities.</description>
<dc:subject>Community: Java Communications</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-09-12T13:11:34-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/09/esbs_the_value.html">
<title>ESBs: the value of indoor plumbing, public water and sewer</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/09/esbs_the_value.html</link>
<description>Some people question the value of an Enterprise Service Bus (ESB) approach to architecture.  Those disbelievers might just need a larger restroom because the value of a plumbing system is (exponentially?) proportional to the scope of its deployment.</description>
<dc:subject></dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-09-04T14:06:40-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/08/an_open_technol.html">
<title>An Open Technology Manifesto</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/08/an_open_technol.html</link>
<description>A while back some smart people put together the Agile Manifesto.  Since, its been commercialized, productized and sometimes abused, but if internalized it makes everyone&apos;s life a little better.  It might be time for a new manifesto, for Open Technology Development.</description>
<dc:subject></dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-08-20T12:16:04-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/08/jbi_catch_the_s.html">
<title>JBI: Catch the second wave...</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/08/jbi_catch_the_s.html</link>
<description>JBI is gaining strong adoption, but the the real wave is yet to hit as the community forms, and the tooling delivers increased productivity and conveniences.
</description>
<dc:subject></dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-08-20T08:45:58-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/07/how_jbi_can_imp.html">
<title>How JBI can improve your love life. (JBI for Social Networking)</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/07/how_jbi_can_imp.html</link>
<description>The JBI specification is about rapid capabilities delivery and service composition.  If employed in just the right manner, this can significantly improve your ability to network socially, which in turn can help out your love life.  Check out this blog to see how you can use JBI to construct a social networking platform.</description>
<dc:subject>Community: Java Enterprise</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-07-12T10:53:14-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/07/jbi_application_1.html">
<title>JBI: Application Development w/o Coding, are we there yet?</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/07/jbi_application_1.html</link>
<description>Often people take a look at JBI and expect to be developing new service engines and binding components, but more often than not an application developer won&apos;t need to code anything at all! (or at least thats the vision)</description>
<dc:subject>Community</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-07-02T14:14:49-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/06/sca_jbi_made_fo.html">
<title>SCA &amp; JBI: Made for each other. (SOA Gone Wild)</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/06/sca_jbi_made_fo.html</link>
<description>After some exploration, it appears as though JBI is ideally positioned to serve as a run-time for SCA contributions.  Here are three ways that SCA and JBI complement each other.</description>
<dc:subject>Community: Java Enterprise</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-06-27T11:59:20-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/06/jbi_not_just_fo.html">
<title>JBI on your cell phone?</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/06/jbi_not_just_fo.html</link>
<description>Java Business Integration (JBI) focuses on loose coupling and rapid/dynamic application composition.  This is as applicable to mobile devices as it is the enterprise space, and JBI is by no means tied down to app servers.  </description>
<dc:subject>Community: Java Communications</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-06-21T13:56:17-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/06/jbi_as_a_conver.html">
<title>JBI as a Convergent Communication Platform</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/06/jbi_as_a_conver.html</link>
<description>Java Business Integration (JBI) may prove the best environment in which to develop convergent communications applications that (once and for all) integrate the disparate networks (XMPP + SIP). </description>
<dc:subject>Community: Java Communications</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-06-18T13:48:01-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2007/06/soa_esb_jbi_sca_1.html">
<title>SOA, ESB, JBI &amp; SCA: A caveman&apos;s perspective</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2007/06/soa_esb_jbi_sca_1.html</link>
<description>One caveman&apos;s experiences trying to achieve &quot;SOA&quot;, by implementing an ESB architecture with the Service Component Architecture (SCA), and Java Business Integration (JBI) specifications: an attempt to understand it all.</description>
<dc:subject>Community: Java Enterprise</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2007-06-14T20:34:26-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2006/12/source_equity_m.html">
<title>Source Equity: Making Open Technology Development Profitable</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2006/12/source_equity_m.html</link>
<description>Thoughts on an Open Technology Development Model that rewards contributors with equity stakes in the project that could then be used as a basis for revenue sharing: making open development models profitable for contributors, and providing the motivation for developers to invade new markets</description>
<dc:subject>Open Source</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2006-12-13T02:49:58-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/boneill42/archive/2004/04/web_services_sl.html">
<title>Web Services &amp; SLEE -- Whats the best fit?</title>
<link>http://weblogs.java.net/blog/boneill42/archive/2004/04/web_services_sl.html</link>
<description>Web Services are catching on fast and furious, but how do these things fit into a SLEE architecture?  Is a HTTP resource adapter the answer?</description>
<dc:subject>Community: Java Communications</dc:subject>
<dc:creator>boneill42</dc:creator>
<dc:date>2004-04-01T06:10:07-08:00</dc:date>
</item>


</rdf:RDF>
