Comments on: Wicket Web Beans 2.0 Features http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/ If you don't know where you want to go, any road will take you there Sat, 19 May 2012 21:34:03 +0000 http://wordpress.org/?v=2.2.1 By: vhik http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-2151 vhik Wed, 13 Jan 2010 16:03:01 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-2151 I would strongly suggest you take a look into Jaxen. It also allows for custom object models I would strongly suggest you take a look into Jaxen. It also allows for custom object models

]]> By: Martin Schlegel http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-502 Martin Schlegel Thu, 05 Mar 2009 18:17:25 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-502 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? 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?

]]> By: Dan Syrstad http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-248 Dan Syrstad Sun, 07 Dec 2008 23:04:48 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-248 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. 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.

]]> By: Martin Schlegel http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-243 Martin Schlegel Fri, 05 Dec 2008 17:52:50 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-243 When will Wicket 1.4 be supported? When will Wicket 1.4 be supported?

]]> By: Dan Syrstad http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-159 Dan Syrstad Sat, 25 Oct 2008 00:12:53 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-159 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! 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!

]]> By: Nick H http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-158 Nick H Fri, 24 Oct 2008 20:39:12 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-158 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. 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.

]]> By: Dan Syrstad http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-88 Dan Syrstad Tue, 07 Oct 2008 01:43:15 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-88 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 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

]]> By: Jurek http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-87 Jurek Mon, 06 Oct 2008 11:04:54 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-87 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 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

]]> By: Dan Syrstad http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-69 Dan Syrstad Sat, 13 Sep 2008 00:16:27 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-69 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. 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.

]]> By: Daniel http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-68 Daniel Fri, 12 Sep 2008 22:15:34 +0000 http://dansyrstad.com/2008/08/07/wicket-web-beans-20-features/#comment-68 Will JXPath allow to use Java classes that don't conform to Java Beans ? I'm trying to use WWB to build an interface for classes generated with XMLBeans from a XSD Schema, the main problem seems to be that the classes have no non-parameters constructor, but are created using Factories. Do you think WWB will be able to deal with that case in 2.0 ? Cheers, Daniel Will JXPath allow to use Java classes that don’t conform to Java Beans ? I’m trying to use WWB to build an interface for classes generated with XMLBeans from a XSD Schema, the main problem seems to be that the classes have no non-parameters constructor, but are created using Factories. Do you think WWB will be able to deal with that case in 2.0 ?

Cheers,

Daniel

]]>