<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Apache Beehive 1.0</title>
	<atom:link href="http://almaer.com/blog/apache-beehive-10/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/apache-beehive-10</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Sat, 08 Sep 2012 07:06:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rich Feit</title>
		<link>http://almaer.com/blog/apache-beehive-10/comment-page-1#comment-28861</link>
		<dc:creator>Rich Feit</dc:creator>
		<pubDate>Sun, 09 Oct 2005 01:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/apache-beehive-10#comment-28861</guid>
		<description>Thank you for the compliments.  :)  And I understand where you&#039;re coming from.  The previous incarnation of Beehive (WLW Runtime) was production-ready in 2003 (and is still in production now for WebLogic Portal/Workshop 8.1 customers), but I agree that until Apache Beehive went 1.0, it wasn&#039;t something most people would have put into production.  Pre-1.0 releases are mainly for toying with.

You&#039;re right about the potential for JSF; since it&#039;s an actual Java standard, it has an automatic base level of acceptance.  We actually aren&#039;t trying to convince anyone to use Beehive over JSF, though.  Beehive Page Flow integrates with JSF as its Navigation layer.  JSF is really useful as view tier technology -- components and events work great for intra-page interactions (across multiple server requests), but it needs a real controller tier, and its NavigationHandler is easily swapped out for this purpose.  Beehive took the approach that JSF should be encouraged as a view layer, peer to JSP.
</description>
		<content:encoded><![CDATA[<p>Thank you for the compliments.  :)  And I understand where you&#8217;re coming from.  The previous incarnation of Beehive (WLW Runtime) was production-ready in 2003 (and is still in production now for WebLogic Portal/Workshop 8.1 customers), but I agree that until Apache Beehive went 1.0, it wasn&#8217;t something most people would have put into production.  Pre-1.0 releases are mainly for toying with.</p>
<p>You&#8217;re right about the potential for JSF; since it&#8217;s an actual Java standard, it has an automatic base level of acceptance.  We actually aren&#8217;t trying to convince anyone to use Beehive over JSF, though.  Beehive Page Flow integrates with JSF as its Navigation layer.  JSF is really useful as view tier technology &#8212; components and events work great for intra-page interactions (across multiple server requests), but it needs a real controller tier, and its NavigationHandler is easily swapped out for this purpose.  Beehive took the approach that JSF should be encouraged as a view layer, peer to JSP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bumble Bee</title>
		<link>http://almaer.com/blog/apache-beehive-10/comment-page-1#comment-28860</link>
		<dc:creator>Bumble Bee</dc:creator>
		<pubDate>Fri, 07 Oct 2005 22:37:20 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/apache-beehive-10#comment-28860</guid>
		<description>Rich,

Thanks for your response. Actually I knew that Beehive first debuted a few years ago, however it wasn&#039;t a V1.0, or you may say, a production ready release. I usually prefer not to use pre-1.0 versions of tools, frameworks, and libraries in customer projects.

A few months ago I took a quick look at Beehive and I really liked it. I liked it more than Struts and I liked it more than WebWork as well.

But the problem is, now that the JSF has become the de facto standard Web framework for J2EE, rarely someone would use Beehive in a J2EE project.

I mean, Beehive might be even technically better than JSF, but it&#039;s very hard to convince someone, or to be convinced, to choose Beehive over JSF.

Regards,
Bumble Bee
</description>
		<content:encoded><![CDATA[<p>Rich,</p>
<p>Thanks for your response. Actually I knew that Beehive first debuted a few years ago, however it wasn&#8217;t a V1.0, or you may say, a production ready release. I usually prefer not to use pre-1.0 versions of tools, frameworks, and libraries in customer projects.</p>
<p>A few months ago I took a quick look at Beehive and I really liked it. I liked it more than Struts and I liked it more than WebWork as well.</p>
<p>But the problem is, now that the JSF has become the de facto standard Web framework for J2EE, rarely someone would use Beehive in a J2EE project.</p>
<p>I mean, Beehive might be even technically better than JSF, but it&#8217;s very hard to convince someone, or to be convinced, to choose Beehive over JSF.</p>
<p>Regards,<br />
Bumble Bee</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Feit</title>
		<link>http://almaer.com/blog/apache-beehive-10/comment-page-1#comment-28859</link>
		<dc:creator>Rich Feit</dc:creator>
		<pubDate>Fri, 07 Oct 2005 04:53:06 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/apache-beehive-10#comment-28859</guid>
		<description>It *was* released several years ago.  :)  It originated as the WebLogic Workshop 8.1 runtime, with a debut in July of 2003.  But... your question certainly is valid -- Beehive has only just now become &quot;real&quot; in the open source world.

The piece of Beehive that plays in the space of those frameworks (WebWork, etc.) is NetUI.  Reasons to use it include its annotations, its &quot;v2&quot; controller features, like reusable page flows that can be nested in other flows, or its UI features, like AJAX-enabled Tree/Grid.  It really adds to the action-based model rather than competing directly with it (and it integrates well as the controller tier for JSF, which is mainly useful as view tier technology).

In some cases, traditional action-based frameworks are sufficient if you&#039;re already invested in them (but then, the same could have been said of plain Servlet/JSP :) ).  If you try out Beehive, the team would definitely be interested to get your feedback on whether its advantages make it worth the wait (user@beehive.apache.org).

Cheers,
Rich
</description>
		<content:encoded><![CDATA[<p>It *was* released several years ago.  :)  It originated as the WebLogic Workshop 8.1 runtime, with a debut in July of 2003.  But&#8230; your question certainly is valid &#8212; Beehive has only just now become &#8220;real&#8221; in the open source world.</p>
<p>The piece of Beehive that plays in the space of those frameworks (WebWork, etc.) is NetUI.  Reasons to use it include its annotations, its &#8220;v2&#8243; controller features, like reusable page flows that can be nested in other flows, or its UI features, like AJAX-enabled Tree/Grid.  It really adds to the action-based model rather than competing directly with it (and it integrates well as the controller tier for JSF, which is mainly useful as view tier technology).</p>
<p>In some cases, traditional action-based frameworks are sufficient if you&#8217;re already invested in them (but then, the same could have been said of plain Servlet/JSP :) ).  If you try out Beehive, the team would definitely be interested to get your feedback on whether its advantages make it worth the wait (user@beehive.apache.org).</p>
<p>Cheers,<br />
Rich</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bumble Bee</title>
		<link>http://almaer.com/blog/apache-beehive-10/comment-page-1#comment-28858</link>
		<dc:creator>Bumble Bee</dc:creator>
		<pubDate>Tue, 04 Oct 2005 22:08:31 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/apache-beehive-10#comment-28858</guid>
		<description>Beehive could be an important player in the field of Web frameworks if it was released a few years ago, but who will ever want to use Beehive when there are such mature Web frameworks as WebWork, Tapestry, and JSF (not to mention the obsolete Struts framework)?
</description>
		<content:encoded><![CDATA[<p>Beehive could be an important player in the field of Web frameworks if it was released a few years ago, but who will ever want to use Beehive when there are such mature Web frameworks as WebWork, Tapestry, and JSF (not to mention the obsolete Struts framework)?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
