Honestly I think the wicket presentation could be better when it comes
about 1.) true OOP, and 2.) when it comes about tools integration support.
1.) Wicket brings back into it's right the true OOP approaches in the
serverside java programming. I think this is almost all the time
overlooked
Yes, with the proxy based solution it is not necessary (transient
fields). I was saying that with the AOP implementation it is
necessary, since there is no proxy working. What the AOP and proxy
solutions have in common is the code to inject the beans.
2005/12/2, Igor Vaynberg [EMAIL PROTECTED]:
My opinions are similar to Christian : - How much faster or easier it would be to use wicket - Spring/Hibernate Integration (almost on everybody's list) - Testability - Performance comparisonI guess you might as well get ready for some complaints :
- Lack of good and thorough documentation - Not
Thanks,
I guess you might as well get ready for some complaints :
- Not so good Spring integration
Why? Igor and a couple of others build some pretty decent Spring
support now? It's all in HEAD, and there has to be a proper build for
it made, but I think we now have Spring integration that
Why? Igor and a couple of others build some pretty decent Springsupport now? It's all in HEAD, and there has to be a proper build forit made, but I think we now have Spring integration that most people
are happy with.I'm looking forward to see a real final solution to the spring integration
Honestly, I don't think there ever was a Spring Integration problem. I think people were just looking for a cookie-cutter approach to using Spring within Wicket. It's actually quite easy to do without using any of the Spring stuff that Igor and others wrote, but it's always a good thing to have a
Oh and one more thing. Everyone keeps bringing up Spring/Hibernate integration. I'm not sure I understand why this is. If you are building your app, IMHO, properly, Wicket should know absolutely nothing about the use of Hibernate. All Hibernate integration should occur within Spring, and Wicket
I am thinking of dumping the wicket-contrib-spring-examples in favor of wicket-phonebook since it demonstrates spring integration. any developers reading with us, what do you think?also see
http://www.wicket-wiki.org.uk/wiki/index.php/Spring for explanation of the wicket-contrib-spring
i guess that was the point of redoing wicket-contrib-spring - to have a final solution that the wicket team is willing to support. so there it is. check out wicket-contrib-spring. of course suggestions for improvements are always welcome.
-IgorOn 12/1/05, Iman RahmatiZadeh [EMAIL PROTECTED] wrote:
I'm fine with it. I constantly send people to the phone book example,
so might as well make it the primary example.
Martijn
On 12/1/05, Igor Vaynberg [EMAIL PROTECTED] wrote:
I am thinking of dumping the wicket-contrib-spring-examples in favor of
wicket-phonebook since it demonstrates spring
Sure. Does the phone book example covers all the basic Spring support things?
Eelco
On 12/1/05, Martijn Dashorst [EMAIL PROTECTED] wrote:
I'm fine with it. I constantly send people to the phone book example,
so might as well make it the primary example.
Martijn
On 12/1/05, Igor Vaynberg
Phone book does not make use of wicket-contrib-spring.
2005/12/1, Eelco Hillenius [EMAIL PROTECTED]:
Sure. Does the phone book example covers all the basic Spring support things?
Eelco
On 12/1/05, Martijn Dashorst [EMAIL PROTECTED] wrote:
I'm fine with it. I constantly send people to the
Indeed. Don't we want some example on your annotation stuff Igor?
Eelco
On 12/1/05, Eduardo Rocha [EMAIL PROTECTED] wrote:
Phone book does not make use of wicket-contrib-spring.
2005/12/1, Eelco Hillenius [EMAIL PROTECTED]:
Sure. Does the phone book example covers all the basic Spring
Igor,
I checked out wicket-contrib-spring and I could not find a example
using SpringWebPage. I think it is pretty easy to use, but if
wicket-contrib-spring-examples was updated it would nice.
2005/12/1, Igor Vaynberg [EMAIL PROTECTED]:
i guess that was the point of redoing
i think that many MVC developers should really check there session what they store in itmost webapps i see do store a lot of information also in it and i think this is pretty common.
On 12/1/05, Iman RahmatiZadeh [EMAIL PROTECTED] wrote:
My opinions are similar to Christian : - How much faster or
Honestly, it wasnt just me, you and the others helped out a lot.-IgorOn 12/1/05, Christian Essl [EMAIL PROTECTED]
wrote:On Thu, 1 Dec 2005 14:24:20 -0500, Andrew Berman
[EMAIL PROTECTED]wrote: Honestly, I don't think there ever was a Spring Integration problem.I think people were just looking
You are right, it doesnt use it directly. it reimplements the first approach discussed on the wiki page. if we decide to dump the spring-example project i can relink the phonebook to use contrib-spring.-Igor
On 12/1/05, Eduardo Rocha [EMAIL PROTECTED] wrote:
Phone book does not make use of
No, the phonebook example is small. currently it covers the first approach discussed on that wiki page. I can convert it to the second approach since that is something people might like more, but i dont see a way or need to do both in that app. the wiki article pretty much walks you through
If phonebook is supposed to sample spring/hibernate usage with Wicket,
I think it is more natural the code being in
wicket-contrib-spring-examples, and remove the phonebook (although
many people must be using phonebook as reference by now...). It is a
nice pattern to have wicket-contrib-xxx and
so how about upgrading phonebook to use contrib-spring and then making a java5 version of phonebook that uses the annotation feature. does that sound like a game plan?-Igor
On 12/1/05, Eelco Hillenius [EMAIL PROTECTED] wrote:
Indeed. Don't we want some example on your annotation stuff Igor?EelcoOn
On Thu, 1 Dec 2005 14:24:20 -0500, Andrew Berman [EMAIL PROTECTED]
wrote:
Honestly, I don't think there ever was a Spring Integration problem. I
think people were just looking for a cookie-cutter approach to using
Spring
within Wicket. It's actually quite easy to do without using any of
Not having looked (yet), is this spring support JDk5 only? (I think I saw mention of using annotations for injection)?On 12/2/05, Eelco Hillenius
[EMAIL PROTECTED] wrote:
Why? Igor and a couple of others build some pretty decent Springsupport now? It's all in HEAD, and there has to be a proper
the way the new integration works you do not need to have your bean holding fields transient, thats the whole point. we create a small /serializable/ proxy that contains just enough information to retrieve the bean from spring context or somewhere else (jndi/ejb3/servletcontext/wherever). so you
the default implementation of IFieldValueFactory (used by the proxy strategy) that is used to locate fields that hold spring references is jdk5 specific. but it is easy to create your own that stores this metadata somewhere else. wicket has a nice metadata system that can be used for this, or
If you were able to go to JavaOne, and was deciding which framework to
use, and one of the presentations is about Wicket, what kind of
information do you want to hear so you would give it a try? Or even
better, what kind of info are you looking for in the program so you
attend such a session?
I'm
Just out of my head:
- ease of development
- basic CRUD app with Spring/Hibernate or EJB3
- how to test
- AJAX support
- in light of this comparison to Tapestry and JSF
Hope you get more feedback,
Christian
On Wed, 30 Nov 2005 20:48:04 +0100, Martijn Dashorst
[EMAIL PROTECTED] wrote:
If
I'd like to see a big picture overview of how it works and what's
required from the development standpoint. And I'm actually talking
about pictures and graphics.
On 11/30/05, Martijn Dashorst [EMAIL PROTECTED] wrote:
If you were able to go to JavaOne, and was deciding which framework to
use,
27 matches
Mail list logo
