V. Jenks wrote:
> Sure, I'd be happy to comment on that.
>
> Some constructive criticism; there are many things that JSF does easier
> and/or better (IMO) than Wicket.
>
> 1. select lists are *much* easier to populate, manipulate, and deal with. ;)
It is possible that our DropDownChoice looks a bit scary :)
But in the end all it needs is a model for where to store the selected
choice, model for all choices and choice renderer. I can't really
imagine what could we do to make it easier. We even provide convenience
constructors that wrap list in models, etc. But it is possible that it's
just too confusing.
> 2. paging and sorting tables/grids/lists are *much, much* easier to
> implement, something I wish would be made easier in Wicket. I'd do it
> myself if I had time...and tried in the past...but am just not skilled
> enough to do yet.
Implement a sortable data provider. Create bunch of columns. Create
DefaultDataTable and pass the provider and columns to the constuctor.
> 3. IDE support - both Netbeans and Eclipse have good support for JSF...it'd
> be nice if the tools supported the technology in Wicket (convenience stuff).
> I haven't tried the eclipse plugin but I'm not sure it would work well w/ a
> MyEclipse enterprise project....and I do mostly EJB3.0 architecture.
> 4. Databinding - sometimes it is nice to set it and forget it...and only use
> components when you need it. This of course, is contrary to Wicket...and
> differs too much conceptually to do anything about.
> 5. Seamless capability to go stateless.
> 6. I can inject a session bean into a JSF 1.2 managed bean using an @EJB
> annoation...quick and simple. I have to use JNDI lookups in Wicket...more
> code to manage.
> 7. The "model" concept can be tricky in certain cases and isn't intuitive...
Yeah, models can be confusing. But i think it's much better in 2.0,
after the big refactor.
>
> Things I do NOT like about JSF and therefore *still* prefer Wicket over any
> other front-end that I've tried:
>
> 1. jsf-config.xml - I don't like this concept at all...it's tedious,
> unintuitive, and cumbersome to manage. Why do they still believe we need
> XML configuration!! This is one of my favorite things about
> Wicket...simplicity.
> 2. JSTL - The slippery-slope of introducing business logic into your view.
> 3. The component model isn't simple...and it's not always consistent.
> 4. 1.2 is being adopted slowly and Glassfish is the only AS (that I know
> of?) that offers it...and I've given up on Glassfish after a few crappy
> experiences.
>
> My overall impression of JSF vs Wicket is; sometimes in Wicket it would be
> nice if some of the finer details were concealed in convenience methods or
> done automatically. The first thing that comes to mind is alternating row
> color. I have to write some gnarly (albeit short) code to do this in
> Wicket...in JSF I just specify two css classes in a single tag attribute in
> the view.
Yeah, I can see that. But what if you need e.g. different colors of rows
depending on the row objects? Say you want to have different background
color for different types of objects in table. Wouldn't that complicate
things a bit with JSF?
There are other cases like this but you get the point - sometimes
> writing separate classes and tons of code to implement something simple
> could be more easily hidden. I cited paging/sorting - I still haven't
> gotten this right in wicket...it's just complicated to implement...and is
> trivial in JSF, ASP.NET, and other front-ends I've experienced.
It's not that difficult, really :) The problem probably is that you
don't know where to start. Instead of one tag you have bunch of classes
and you don't know yet which classes will do the job.
-Matej
>
> Ultimately, JSF is more complicated and harder to manage...and not as rapid
> to develop with as Wicket has been for me in the past. Wicket is just a
> great "pick it up and run w/ it" framework w/ a short(er) learning curve.
>
>
> igor.vaynberg wrote:
>> offtopic, would like to hear about your jsf experience compared to wicket.
>> anything you found better that we can improve?
>>
>> -igor
>>
>>
>> On 1/10/07, V. Jenks <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi all, been a long hiatus for me but I'm diving back into Wicket
>>> finally.
>>>
>>> I'm a little rusty (was forced, against my will, to use JSF for the past
>>> couple of months!) - and I've got a silly question...should be a snap.
>>>
>>> I've got a DropDownChoice select list on a page I simply need to fill w/
>>> strings. It's not table-driven data, it's flat, and it's not represented
>>> as
>>> an entity/POJO...I simply need to select a single string from a list of
>>> strings.
>>>
>>> Here's a snippet:
>>>
>>>
>>> ..............................................................................................
>>>
>>> //editable entity
>>> PhoneNumber number = new PhoneNumber();
>>>
>>> //add form
>>> final Form form = new Form("editPhoneForm", new
>>> CompoundPropertyModel(number));
>>>
>>> List<String> phoneTypeItems = new ArrayList<String>();
>>> phoneTypeItems.add("office");
>>> phoneTypeItems.add("cell");
>>> phoneTypeItems.add("division");
>>>
>>> //add dropdown select form control
>>> form.add(new DropDownChoice("phoneType", new Model(),
>>> phoneTypeItems)
>>> {
>>> public String getDisplayValue(Object object)
>>> {
>>> return object.toString();
>>> }
>>>
>>> public String getIdValue(Object object, int
>>> index)
>>> {
>>> return object.toString();
>>> }
>>> }.setRequired(true));
>>>
>>>
>>> ............................................................................................
>>>
>>> Now, when I pull up the page, it displays...all the values are there.
>>> BUT...I get the value is null when the form is submitted...it isn't
>>> getting
>>> the value.
>>>
>>> I'm using JBoss/EJB3 and I get this exception:
>>>
>>> org.hibernate.PropertyValueException: not-null property references a null
>>> or
>>> transient value: com.agribeef.ed.model.PhoneNumber.phoneType
>>>
>>> Any suggestions? Thanks! Glad to be back!
>>> --
>>> View this message in context:
>>> http://www.nabble.com/plain-%27ol-DropDownChoice-of-strings---tf2955745.html#a8268348
>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>
>>>
>>> -------------------------------------------------------------------------
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>>> your
>>> opinions on IT & business topics through brief surveys - and earn cash
>>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>> _______________________________________________
>>> Wicket-user mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/wicket-user
>>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Wicket-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/wicket-user
>>
>>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
