<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for Taking a Different Road</title>
	<link>http://dansyrstad.com</link>
	<description>If you don't know where you want to go, any road will take you there</description>
	<pubDate>Thu, 11 Mar 2010 09:38:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>Comment on The Light Side of the Moon by TS</title>
		<link>http://dansyrstad.com/2010/02/28/the-light-side-of-the-moon/#comment-2746</link>
		<author>TS</author>
		<pubDate>Mon, 01 Mar 2010 17:53:14 +0000</pubDate>
		<guid>http://dansyrstad.com/2010/02/28/the-light-side-of-the-moon/#comment-2746</guid>
		<description>I do agree with most of the poits you've made.  The only one I could argue - what if Russia went to the Moon first.  See, the fact that Gagarin was the first in space, prompted US to go further.  So, if a Russian was  on the Moon first, US would have set even bigger goal.   

I think, when one is motivated by a grand idea or vision, it always benefits all, not just one.  But, if you only think of your "own" benefit, it most likely will harm the rest.</description>
		<content:encoded><![CDATA[<p>I do agree with most of the poits you&#8217;ve made.  The only one I could argue - what if Russia went to the Moon first.  See, the fact that Gagarin was the first in space, prompted US to go further.  So, if a Russian was  on the Moon first, US would have set even bigger goal.   </p>
<p>I think, when one is motivated by a grand idea or vision, it always benefits all, not just one.  But, if you only think of your &#8220;own&#8221; benefit, it most likely will harm the rest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wicket Web Beans 2.0 Features by vhik</title>
		<link>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-2151</link>
		<author>vhik</author>
		<pubDate>Wed, 13 Jan 2010 16:03:01 +0000</pubDate>
		<guid>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-2151</guid>
		<description>I would strongly suggest you take a look into Jaxen. It also allows for custom object models</description>
		<content:encoded><![CDATA[<p>I would strongly suggest you take a look into Jaxen. It also allows for custom object models</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wicket Web Beans 2.0 Features by Martin Schlegel</title>
		<link>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-502</link>
		<author>Martin Schlegel</author>
		<pubDate>Thu, 05 Mar 2009 18:17:25 +0000</pubDate>
		<guid>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-502</guid>
		<description>Maybe you could make a 1.4 branch. I've played a bit, to push wwb to wicket 1.4 but the DatePicker is making troubles.
What about the DatePicker?
It disappeared at wicket-stuff.

How do I get commit rights?</description>
		<content:encoded><![CDATA[<p>Maybe you could make a 1.4 branch. I&#8217;ve played a bit, to push wwb to wicket 1.4 but the DatePicker is making troubles.<br />
What about the DatePicker?<br />
It disappeared at wicket-stuff.</p>
<p>How do I get commit rights?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wicket Web Beans 2.0 Features by Dan Syrstad</title>
		<link>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-248</link>
		<author>Dan Syrstad</author>
		<pubDate>Sun, 07 Dec 2008 23:04:48 +0000</pubDate>
		<guid>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-248</guid>
		<description>I'll try to add support for Wicket 1.4 when it goes final. I'm really looking for someone interested in taking over the WWB 1.x code. I'm currently putting any time I have available (not much) into 2.0.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll try to add support for Wicket 1.4 when it goes final. I&#8217;m really looking for someone interested in taking over the WWB 1.x code. I&#8217;m currently putting any time I have available (not much) into 2.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wicket Web Beans 2.0 Features by Martin Schlegel</title>
		<link>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-243</link>
		<author>Martin Schlegel</author>
		<pubDate>Fri, 05 Dec 2008 17:52:50 +0000</pubDate>
		<guid>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-243</guid>
		<description>When will Wicket 1.4 be supported?</description>
		<content:encoded><![CDATA[<p>When will Wicket 1.4 be supported?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wicket Web Beans 2.0 Features by Dan Syrstad</title>
		<link>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-159</link>
		<author>Dan Syrstad</author>
		<pubDate>Sat, 25 Oct 2008 00:12:53 +0000</pubDate>
		<guid>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-159</guid>
		<description>You should work with the trunk (1.1). The wwb-2.0 branch is still experimental right now. I'm always happy to take in patches!</description>
		<content:encoded><![CDATA[<p>You should work with the trunk (1.1). The wwb-2.0 branch is still experimental right now. I&#8217;m always happy to take in patches!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wicket Web Beans 2.0 Features by Nick H</title>
		<link>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-158</link>
		<author>Nick H</author>
		<pubDate>Fri, 24 Oct 2008 20:39:12 +0000</pubDate>
		<guid>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-158</guid>
		<description>WWB looks interesting and I'd like to start extending it to meet some of my immediate needs.  Which branch should I be hacking on?  Do you want patches?  Feel free to contact me by email for more info.</description>
		<content:encoded><![CDATA[<p>WWB looks interesting and I&#8217;d like to start extending it to meet some of my immediate needs.  Which branch should I be hacking on?  Do you want patches?  Feel free to contact me by email for more info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wicket Web Beans 2.0 Features by Dan Syrstad</title>
		<link>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-88</link>
		<author>Dan Syrstad</author>
		<pubDate>Tue, 07 Oct 2008 01:43:15 +0000</pubDate>
		<guid>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-88</guid>
		<description>Jurek:

Thank you for your comments. WWB 2.0 will be a departure from 1.x.  It will be much more of a bean-binding and component composition framework.

To your question, drop-downs will be bound to a current value from the bean and have a second binding to a list of possible values (possibly from another bean). NonJavaEnum has gone away in 2.0.

In 1.x you don't need to change your beans, you can implement new components and register them with ComponentRegistry. Your new component can know how to deal with your custom enum type.

I do realize the limitations of 1.x and that's what I'm trying to address in 2.0. But it should be understood that POJO does not necessarily mean Hibernate/persistent/domain object. WWB POJOs represent a model for the UI. Sometimes your UI model will not map directly to domain objects. Hence, you may need to write additional POJOs to complete the model.

-Dan</description>
		<content:encoded><![CDATA[<p>Jurek:</p>
<p>Thank you for your comments. WWB 2.0 will be a departure from 1.x.  It will be much more of a bean-binding and component composition framework.</p>
<p>To your question, drop-downs will be bound to a current value from the bean and have a second binding to a list of possible values (possibly from another bean). NonJavaEnum has gone away in 2.0.</p>
<p>In 1.x you don&#8217;t need to change your beans, you can implement new components and register them with ComponentRegistry. Your new component can know how to deal with your custom enum type.</p>
<p>I do realize the limitations of 1.x and that&#8217;s what I&#8217;m trying to address in 2.0. But it should be understood that POJO does not necessarily mean Hibernate/persistent/domain object. WWB POJOs represent a model for the UI. Sometimes your UI model will not map directly to domain objects. Hence, you may need to write additional POJOs to complete the model.</p>
<p>-Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wicket Web Beans 2.0 Features by Jurek</title>
		<link>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-87</link>
		<author>Jurek</author>
		<pubDate>Mon, 06 Oct 2008 11:04:54 +0000</pubDate>
		<guid>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-87</guid>
		<description>I just discovered web beans. My compliments on your work. 

I was wondering if you had given any thought to non-Java enumeration in the new version. Is it possible that annotations could be used to implement custom/dynamic runtime enums? 

Otherwise it seems that requires a fair amount of work to get fields to work on existing beans. One either has to go back and refactor many of one's existing classes or one must write a class that shadows the original (in my case) hibernate pojo. 

Thanks,
Jurek</description>
		<content:encoded><![CDATA[<p>I just discovered web beans. My compliments on your work. </p>
<p>I was wondering if you had given any thought to non-Java enumeration in the new version. Is it possible that annotations could be used to implement custom/dynamic runtime enums? </p>
<p>Otherwise it seems that requires a fair amount of work to get fields to work on existing beans. One either has to go back and refactor many of one&#8217;s existing classes or one must write a class that shadows the original (in my case) hibernate pojo. </p>
<p>Thanks,<br />
Jurek</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wicket Web Beans 2.0 Features by Dan Syrstad</title>
		<link>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-69</link>
		<author>Dan Syrstad</author>
		<pubDate>Sat, 13 Sep 2008 00:16:27 +0000</pubDate>
		<guid>http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-69</guid>
		<description>I'm currently fleshing out the design, but the current plan is that a pluggable bean factory will be supported. Also, JXPath will be supported via a pluggable PropertyResolver interface. This will allow other types of expressions to be used, not just JXPath expressions.</description>
		<content:encoded><![CDATA[<p>I&#8217;m currently fleshing out the design, but the current plan is that a pluggable bean factory will be supported. Also, JXPath will be supported via a pluggable PropertyResolver interface. This will allow other types of expressions to be used, not just JXPath expressions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
