the application is never serialized, so you are free to hold any references
there you like.
-igor
On 4/17/07, nlif <[EMAIL PROTECTED]> wrote:
Very well. But, this means that not even the Application holds the
services
as members. Every call to getService() will go to the spring context, and
Very well. But, this means that not even the Application holds the services
as members. Every call to getService() will go to the spring context, and
create a new proxy, right? This seems sub-optimal. Is the Application object
ever serialized? If it is not, and I make sure never to hold reference
On 4/17/07, nlif <[EMAIL PROTECTED]> wrote:
If I go with (1), then it makes sense to use the fact that the Application
instance is created by Spring, to also inject it with the Services: I just
provide setters. But then - how do I implement the getters so that they
return the proxies?
then
Hi,
I am using Wicket 1.2.5 with the Wicket-Spring extension, but without the
annotation support (I am on JDK 1.4).
It seems there are two ways to integrate with Spring:
1) In my web.xml, to use the SpringWebApplicationFactory, and to define
MyWicketApplication as a bean in my Spring context XML
ean that didn't have a no-args constructor.
Will try to stick to interfaces.
Thanks again,
Derek
-Original Message-
From: [EMAIL PROTECTED] on behalf of Peter Thomas
Sent: Fri 4/13/2007 10:29 AM
To: [EMAIL PROTECTED]
Subject: Re: [Wicket-user] Spring integration and which wicket ve
; > wicket
> > wicket
> > 1.2.5
> > compile
> >
> >
> > wicket
> > wicket-spring
> > 1.2.5
> > compile
> >
> >
> > wicket
> > wicket-spring-a
ehalf of Martijn Dashorst
> Sent: Fri 4/13/2007 9:12 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Wicket-user] Spring integration and which wicket version
>
> So you're still using wicket-spring-1.2.5 :)
>
> >
> > wicket
> > wicket
>
of Martijn Dashorst
Sent: Fri 4/13/2007 9:12 AM
To: [EMAIL PROTECTED]
Subject: Re: [Wicket-user] Spring integration and which wicket version
So you're still using wicket-spring-1.2.5 :)
>
> wicket
> wicket
> 1.2.5
> compile
>
>
12 AM
To: [EMAIL PROTECTED]
Subject: Re: [Wicket-user] Spring integration and which wicket version
So you're still using wicket-spring-1.2.5 :)
>
> wicket
> wicket
> 1.2.5
> compile
>
>
> wicket
> wicket-spr
>
> package wicket.spring.injection does not exist
>
>
> Regards,
> Derek
>
>
> -Original Message-
> From: [EMAIL PROTECTED] on behalf of Martijn Dashorst
> Sent: Fri 4/13/2007 8:41 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Wicket-user] Sprin
pring-annot
1.2.5
compile
and get:
package wicket.spring.injection does not exist
Regards,
Derek
-Original Message-
From: [EMAIL PROTECTED] on behalf of Martijn Dashorst
Sent: Fri 4/13/2007 8:41 AM
To: [EMAIL PROTECTED]
Subject: Re: [Wicket-user] Spring integration and
Use wicket-spring 1.2.4 It is compatible with wicket 1.2.5.
Martijn
On 4/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Setting out with Wicket for the first time and looking for some advice on
> which version to use.
>
> Have started out with the latest release (1.2.5) but that
Hi,
Setting out with Wicket for the first time and looking for some advice on which
version to use.
Have started out with the latest release (1.2.5) but that doesn't seem to
include the
wicket.spring.injection package needed for the annotation based approach to
Spring integration
described he
Hi all,
as there is an open jira (
http://opensource.atlassian.com/projects/spring/browse/SPR-2484) for
pacthing @Configurable to support before-construction injection I decided to
wait for this fix instead of duplicating the provided aspects and
annotations just to change the advice type.
I hav
> Well, to be precise, there is this minor complication of redefining the
> advice to configure the bean before constructor execution. And you can take
> advantage of spring-annotations to avoid cluttering your xml app context
> (that's if you are reluctant to autowiring). What I can do is to updat
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
a project for what? there is nothing to do but to configure spring in the
> context xml file, put @Configurable on your page/component, and configure
> the aspectj agent in your launch config.
:) . Yep, that's everything .
Well, to be p
a project for what? there is nothing to do but to configure spring in the
context xml file, put @Configurable on your page/component, and configure
the aspectj agent in your launch config.
:) . Yep, that's everything .
-igor
On 3/23/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> > > I
Right.
Eelco
On 3/23/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> a project for what? there is nothing to do but to configure spring in the
> context xml file, put @Configurable on your page/component, and configure
> the aspectj agent in your launch config.
>
> -igor
>
>
> On 3/23/07, Eelco H
a project for what? there is nothing to do but to configure spring in the
context xml file, put @Configurable on your page/component, and configure
the aspectj agent in your launch config.
-igor
On 3/23/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > It's cool that it can be done like that
> > It's cool that it can be done like that. However, it's still not clear
> > to me what the advantage (besides giving people more choice if they
>
> It isn't clear to me either. But as I know of some people (including myself)
> that i's using @Configurable to inject their domain objects (this is
It's cool that it can be done like that. However, it's still not clear
to me what the advantage (besides giving people more choice if they
It isn't clear to me either. But as I know of some people (including myself)
that i's using @Configurable to inject their domain objects (this is the
spring
thats why you use the aspectj weaver/loader, it weaves a deserialization
handler into the object to reinject the dependencies.
-igor
On 3/23/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
It's cool that it can be done like that. However, it's still not clear
to me what the advantage (besides
It's cool that it can be done like that. However, it's still not clear
to me what the advantage (besides giving people more choice if they
like) of this would be... Whereas wicket-spring works right out of the
box now, in your case users would have to do something extra (set up
AspectJ).
Also, for
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
heh, the biggest advantage of @SpringBean is that it is done _before_ the
> constructor. i use services in the constructor all the time. maybe you can
> tweak the aspectj aspect to also do it before as well.
(But do you explicitly invoke the
heh, the biggest advantage of @SpringBean is that it is done _before_ the
constructor. i use services in the constructor all the time. maybe you can
tweak the aspectj aspect to also do it before as well.
(But do you explicitly invoke these services from inside the constructor or
just delay exe
heh, the biggest advantage of @SpringBean is that it is done _before_ the
constructor. i use services in the constructor all the time. maybe you can
tweak the aspectj aspect to also do it before as well.
-igor
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
Here is an example of using @Con
Here is an example of using @Configurable to integrate spring with wicket as
some people has asked me for one. To launch it just:
1) set MAVEN_OPTS=-javaagent:/aspectjweaver.jar in
the env.
2) run 'mvn jetty:run'
Notice that dependencies are injected *after* constructor execution, so for
this si
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
> i wouldnt be able to do this with @Configurable because since my
> genericdataprovider is not @Configurable and there is no way to make it so
> it cannot restore its, what would have to be a transient, reference to the
> genericfinder.
>
I c
> Yes, you need one prototype bean definition for each injected page
> and/or component. That's the spring way after all. You get all the power of
> XmlApplicationContext (with which you can do more that vanilla injection) at
> the expense of dealing with xmls.
>
in my apps i use a lot of panels
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
Hi Igor, I see your points. Here's what I think about them.
1) @Configurable is a type-level annotation. so if you want any control
> over what is injected you have to declare it in the applicationcontext. i
> have a ton of pages and components
Hi Igor, I see your points. Here's what I think about them.
1) @Configurable is a type-level annotation. so if you want any control over
what is injected you have to declare it in the applicationcontext. i have a
ton of pages and components that get injected and i would really hate to
have to ma
there are a couple of things i personally dont like about it
1) @Configurable is a type-level annotation. so if you want any control over
what is injected you have to declare it in the applicationcontext. i have a
ton of pages and components that get injected and i would really hate to
have to ma
On 23/03/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
> >
> > Maybe it's a silly question, but how did you find that page about Spring?
> I see nothing from the main wiki page that would lead to that page.
>
> I arrived there from a link in the wicket-spring demo applications :).
Hmm - I'll have to
Maybe it's a silly question, but how did you find that page about Spring?
I see nothing from the main wiki page that would lead to that page.
I arrived there from a link in the wicket-spring demo applications :).
Cheers,
Carlos
Robert
it provides proxies in order to make serialization for clustering and
backbutton support as cheap as possible.
Yep, that's why I suggested to keed dependencies transient (as the targets
of the wicket-spring proxies are). So you don't even need to serialize a
thin proxy.
. So you can declare
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
I'm very new to Wicket (with no more than a few hours of fly). I would
like to integrate it with the spring AplicationContext/BeanFactory so I've
been reading the solutions described in
http://www.wicket-wiki.org.uk/wiki/index.php/Spring.
Ma
I think Igor and the others who have been working on Spring
integration can answer this better, but Wicket's special sauce is that
it provides proxies in order to make serialization for clustering and
backbutton support as cheap as possible.
Eelco
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrot
Hi all,
I'm very new to Wicket (with no more than a few hours of fly). I would like
to integrate it with the spring AplicationContext/BeanFactory so I've been
reading the solutions described in
http://www.wicket-wiki.org.uk/wiki/index.php/Spring. I've nothing to object
to them but I think it woul
jip i noticed this also. I guess it is something that the commented source
code that is removed from
the page after rendering did or whatever.
Can anybody look at the last thing that got stuck:
http://wicketstuff.org/bamboo/browse/WICKET2X-EXTENSIONS-11/test/wicket.extensions.markup.html.tree.Tr
Now it works here as well. :)
Good job
On 1/23/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
yes and i rechecked it in.
Because the file you checked in is just plain wrong.
Those extra empty spaces don't make any sense!
Please recheck if it fails again for you and then test why those extra
sp
Johan Compagner wrote:
> So i guess Windows Rules.. others just suck! :)
To rule and to suck can go hand in hand as well :)
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'
yes and i rechecked it in.
Because the file you checked in is just plain wrong.
Those extra empty spaces don't make any sense!
Please recheck if it fails again for you and then test why those extra
spaces are in front of every empty line.
So i guess Windows Rules.. others just suck! :)
johan
O
On 1/23/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
it is strange isn't it
now you fixed it so it works on the server
Hmm.. and it works on my machine as well. Windows Sucks(tm)
Frank
-
Take Surveys. Earn Cash. Influe
it is strange isn't it
now you fixed it so it works on the server
and now i get the error:
---
Battery: wicket.markup.html.basic.SimplePageTest
-
Hehe ok. I guess "I'll fix it tonight" is to late for you, huh? ;o)
Frank
On 1/22/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
I already fixed it
The surefire plugin now uses a bit older version:
2.1.3
And suddenly everything is cleaned up (see bamboo)
now really only one thing is failing.
I already fixed it
The surefire plugin now uses a bit older version:
2.1.3
And suddenly everything is cleaned up (see bamboo)
now really only one thing is failing.
johan
On 1/22/07, Frank Bille <[EMAIL PROTECTED]> wrote:
On 1/22/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
>
> yes:
>
> ht
On 1/22/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
yes:
http://jira.atlassian.com/browse/BAM-732
they say it is a maven error???
Yeah it looks like it. Have never seen it before. Take a look at the
attached file which is taken from the latest build.
I'll take a look at this as well ton
yes:
http://jira.atlassian.com/browse/BAM-732
they say it is a maven error???
johan
On 1/22/07, Frank Bille <[EMAIL PROTECTED]> wrote:
On 1/22/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
>
> http://wicketstuff.org/bamboo/browse/WICKET2X-WICKET/latest
>
Ok, that one. I'll take a look a
On 1/22/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
http://wicketstuff.org/bamboo/browse/WICKET2X-WICKET/latest
Ok, that one. I'll take a look at that tonight. Btw has anyone reported that
test count bug in bamboo?
Frank
see: http://wicketstuff.org/bamboo/start.action
and then:
http://wicketstuff.org/bamboo/browse/WICKET2X-WICKET/latest
don't look at the 85 errors. as far as i can see it is only one. But thats a
Bamboo bug.
johan
On 1/22/07, Frank Bille <[EMAIL PROTECTED]> wrote:
On 1/22/07, Johan Compag
On 1/22/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
i already fixed this by not using a file at all but just directly the
inputstream
Yeah saw that. :)
All test are running fine now on my windows machine. Can somebody with a mac
or linux
look why there are still one or two test failing?
i already fixed this by not using a file at all but just directly the
inputstream
All test are running fine now on my windows machine. Can somebody with a mac
or linux
look why there are still one or two test failing?
It has to do something with encoding i guess.
johan
On 1/16/07, Frank Bille
On 1/15/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
The licence header test fails. If you provide parameter
-Dmaven.test.skip=true, the project builds and works fine.
Frank, if you are reading this, wouldn't
licenseHeader = url.getFile();
work better than
licenseHeader = new wicket.util.f
The licence header test fails. If you provide parameter
-Dmaven.test.skip=true, the project builds and works fine.
Frank, if you are reading this, wouldn't
licenseHeader = url.getFile();
work better than
licenseHeader = new wicket.util.file.File(new
URI(url.toString())).readString(); ?
Current
Thanks Mats, yes I agree.
I am also reporting (refer original message) that wicket-spring-annot is
broken for Maven 2 users, so at the moment I cannot use it even if I wanted
to. Can anyone comment on this?
Thanks,
Peter.
On 1/15/07, Mats Norén <[EMAIL PROTECTED]> wrote:
Oops, sorry, didn'
Oops, sorry, didn't read your entire mail.
However, I do feel that the extra dependency is worth it in the long
run. You very seldom have only one DAO in your application... :) Let's
say you have 50 beans that you want to use in different parts of the
system, the code bloat in the Application class
Thanks Mats, I totally agree that that is a pretty clean option. This does
mean that you have to include wicket-spring and wicket-spring-annot though -
which I avoided.
I am trying to figure if the alternate approach is workable and then I do
feel it is worth adding to the wiki. Also it may be
I personally think it is easer to override the init method of your application:
protected void init() {
super.init();
addComponentInstantiationListener(new SpringComponentInjector(this));
...
}
and use the @SpringBean where you want to use your DAO.
@SpringBean
ContactDao
Hi,
I was thinking that more option can be added to the official wicket-spring
integration documentation. Something like this:
1) normal wicket servlet config in web.xml, with applicationClassName
init-param
2) Application class uses Spring API to get hold of dependency like this:
class MyApp
hi people,there is now a wicket-spring-cattr project that integrates spring injection with the commons attributes through the use of a @@SpringBean commons attribute. great for people on jdk1.4 that wont annotation-like functioanlity and dont mine a post-compilation step.
http://jakarta.apache.org/
hello all,the spring integration packages moved from wicket-stuff project to wicket project and are available aswicket-spring
wicket-spring-examples
wicket-spring-annot
wicket-spring-annot-examples there is a request to cleanup the wicket-stuff cvs already in progress.there are a couple of new feat
just added an AnnotApplicationContextMock that does all the init for the AnnotSpringInjector. also updated the wiki to show the new and reduced test case.-IgorOn 12/12/05,
Igor Vaynberg <[EMAIL PROTECTED]> wrote:
My version of the mock is very small still. so far it only supports pulling out beans
My version of the mock is very small still. so far it only supports pulling out beans by name, i need to add by class when i have a bit of time - soon though.Yes those 3 lines are repetitive. I will probably subclass the mock app context and roll those into the constructor. I think it will be nice
if you bore yourself at one time at javapolis!Please come visit us!On 12/12/05, Per Ejeklint <[EMAIL PROTECTED]
> wrote:Nice work, many thanks!I'll plunge in to it as soon as there is a boring session here at
JavaPolis. :-)/Per12 dec 2005 kl. 12-12 | v.50 |09.09 skrev Igor Vaynberg:> i just refacto
Nice work, many thanks!
I'll plunge in to it as soon as there is a boring session here at
JavaPolis. :-)
/Per
12 dec 2005 kl. 12-12 | v.50 |09.09 skrev Igor Vaynberg:
i just refactored the wicket-contrib-spring project, here are the
changes
<|>
Per Ejeklint
Mobile: +46 (0)70-5090052
We
Very good! I started to use mock version of application context too. The
version which i did looks probably very similar than
ApplicationContextMock (couldn't get it from anoncvs yet). The only
visible difference is that I had put these lines:
SpringContextLocatorMock ctxLocator=ne
i just refactored the wicket-contrib-spring project, here are the changes* all jdk 5 stuff has been factored out into wicket-contrib-spring-jdk5 project so wicket-contrib-spring can compile with 1.4* the injector for automatic dependencies is now aquired through a static methods of the InjectorHold
Martijn Dashorst wrote:
I could ask my employer to host the wicket wiki on one of our (test)
servers. That would speed up the wiki thing. I'm -1 on JIRA and
confluence. I don't want to keep switching constantly between wiki's.
We have decided for mediawiki, and I like to stick with it, until a
> [mailto:
[EMAIL PROTECTED]] On Behalf Of> Gwyn Evans> Sent: Monday, September 05, 2005 12:06 PM> To: [email protected]
> Subject: Re: [Wicket-user] Spring Integration>> Hmm, the (cheap) hosting I was looking at has LAMP, but not Java!>> /Gwyn>> On
That sucks, oh well :)
-Igor
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Gwyn Evans
> Sent: Monday, September 05, 2005 12:06 PM
> To: [email protected]
> Subject: Re: [Wicket-user] Spring Integration
eap.
> -Igor
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > Gwyn Evans
> > Sent: Monday, September 05, 2005 11:58 AM
> > To: [email protected]
> > Subject: Re: [Wicket-user] Spring I
y, September 05, 2005 11:58 AM
> To: [email protected]
> Subject: Re: [Wicket-user] Spring Integration
>
> I've been waiting in the hope that SF do get round to
> upgrading their DB servers - if there's no movement soon
> though, I might have to look i
gt; Sent: Monday, September 05, 2005 1:17 AM
> > To: [email protected]
> > Subject: Re: [Wicket-user] Spring Integration
> >
> > In light of documentation, I've created a Spring integration
> > Wiki web page, and put your comment there, I hope you
t; Sent: Monday, September 05, 2005 1:17 AM
> To: [email protected]
> Subject: Re: [Wicket-user] Spring Integration
>
> In light of documentation, I've created a Spring integration
> Wiki web page, and put your comment there, I hope you don't mind!
>
&g
ginal Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Cameron Taggart
> Sent: Sunday, September 04, 2005 9:07 PM
> To: [email protected]
> Subject: Re: Re: Re: [Wicket-user] Spring Integration
>
> I found out about Wicket at t
Cameron,
did you already find the wicket-stuff project? It contains at least
two means on how to use Spring, a example and quite some utility
classes to access databases with hibernate and spring.
http://www.gmane.org provides a mail archive of this mailling list.
You'll find some mail threads ab
I found out about Wicket at the web framework smackdown at JavaOne.
I've been poking around the documentation and mailing list since then,
but I'm truly evaluating Wicket this week. I've customized a couple
of the examples and like what I see so far very much!
Spring integration is a requirement
Martin Fey's SpringAwareModel / SpringBeanModel seem to be a pretty good
solution to the whole Spring integration issue. [There might be lots more
that can be done, but I'm not enough of an expert at Spring or Wicket to
think of anything better.]
When I get a chance, I'll add some notes on th
Well, Wicket does have a few call back methods that could be used for
insertion. And if we would need more, we could consider it. I think
the callback methods (like beginRequest) are a better match for
webapplications than construction time as we are still in a request
driven environment.
Eelco
That is the point: Wicket does not require it. There is no special rule. I
guess, at the latest when the page will be rendered, all components had to be
added to a page. (I don't know exactly when Wicket needs the complete component
tree of a page).
But there is no initialising method as in Sp
Wicket doesn't require anything. And that is both good and bad. It is
good because it gives you - the developer - complete freedom on how
you do things, including building in support for Spring integratoin.
It is bad because, as we don't manage the lifecycle, it is harder to
come with a default sch
On Mon, 2005-08-22 at 12:31 +0200, Martin Fey wrote:
> The serializable-thing is one reason why there is a integration contribution
> in form of a pull model: SpringBeanModel
>
> I'm not yet convinced that Spring-managing Wicket-components (or parts of
> them) is a really good idea, because of
The serializable-thing is one reason why there is a integration contribution in
form of a pull model: SpringBeanModel
I'm not yet convinced that Spring-managing Wicket-components (or parts of them)
is a really good idea, because of all the issues discussed earlier in this
mailing list (e.g. un
I think that shouldn't be too much of a problem really. I forgot about
the transient keyword, but it was in my line of thought re-inject on
every request.
Eelco
On 8/22/05, Joni Suominen <[EMAIL PROTECTED]> wrote:
> Note, you do not need to use XML when using Spring. While that's a
> default cho
Yeah, Wicket would look more like Tapestry then. And what would the
advantage be? Your XML would look horrible (like with access paths for
individual components), and it would just serve the purpose of
avoiding the service lookup pattern (which in my opinion really isn't
that bad when done right).
Note, you do not need to use XML when using Spring. While that's a
default choice for many developers, I will almost always use autowire
feature + programmatic bean factory manipulation + custom annotations to
drive the dependency injection. Why not let developers choose which IOC
mechanism to use?
Hi,
I seem to agree with Huy since not all developers are already too
anxious to start using annotations or jdk1.5 for that matter, although
it would be a good solution for say wicket 2.0.
As for the XML, wouldn't that be like tapestry'ing wicket? I keep to my
original though of having somet
Eelco Hillenius wrote:
Sorry guys, but I wasn't able to reserve enough free time to do an irc
chat.
I have been thinking about Spring integration a bit more though, and
the only thing I can think of to make it really nice is to use
(runtime) annotations. I was thinking about letting Wicket (
Not yet, but it sounds like an idea to open one. Though mailing lists
are superiour for the history. Good for stats too.
Eelco
On 8/22/05, Gili <[EMAIL PROTECTED]> wrote:
>
> Does Wicket have an official IRC channel? A lot of these conversations
> would go faster on IRC :)
>
> Gili
>
Does Wicket have an official IRC channel? A lot of these conversations
would go faster on IRC :)
Gili
Eelco Hillenius wrote:
Sorry guys, but I wasn't able to reserve enough free time to do an irc
chat.
I have been thinking about Spring integration a bit more though, and the
only thing I
Sorry guys, but I wasn't able to reserve enough free time to do an irc chat.
I have been thinking about Spring integration a bit more though, and the
only thing I can think of to make it really nice is to use (runtime)
annotations. I was thinking about letting Wicket (actually a few utility
cl
> 2 here.
>
> :alex |.::the_mindstorm::.|
>
> > -Oorspronkelijk bericht-
> > Van: Koen Serry [mailto:[EMAIL PROTECTED]
> > Verzonden: vr 19-8-2005 14:56
> > Aan: [email protected]
> > CC:
> >
: Friday, August 19, 2005 5:34 AMTo:
[email protected]: Re: [Wicket-user] Spring
Integration
Hi I did before posting to this mailing list, but as I
found the construct a bit weird to me I was thinking if an alternative would
be possible.Like the
This is very true in terms of "not using" spring to inject every little
property/attribute. I use spring mvc and there are things like setting
primitive/simple properties which they recommend using xml to configure
which doesn't really make much sense, especially when these things dont
change
, but looking to ;-). I would like to participate: GMT + 2
here.
:alex |.::the_mindstorm::.|
-Oorspronkelijk bericht-
Van: Koen Serry [mailto:[EMAIL PROTECTED]
Verzonden: vr 19-8-2005 14:56
Aan: [email protected]
CC:
Onderwerp: Re: [Wicket-user] Spring Integr
e
> zones.
>
> Eelco
>
>
>-Oorspronkelijk bericht-
>Van: Koen Serry [mailto:[EMAIL PROTECTED]
>Verzonden: vr 19-8-2005 14:56
>Aan: [email protected]
> CC:
>Onderwerp: Re: [Wicket-user] Spring Integration
&
There are people on the list knowing Spring much much better than I
do. But I remember some people tried this approach and finally decided
that it is much easier to use "new MyPage(whatever)" and "add(new
MyPanel(..)" than configuring it in some xml file. I assume there some
email in the archiv (gm
-2005 14:56
Aan: [email protected]
CC:
Onderwerp: Re: [Wicket-user] Spring Integration
I'd like to participate,
what irc server/channel?
Koen
Eelco Hillenius wrote:
The only problem with doing the real IOC with the pages in wicket would
be that it requires wicket to either do it through annotations or
through an XML. And both options are now really an advantage of using
wicket. So having something like a global map sound like having the
best of both worlds
n Serry [mailto:[EMAIL PROTECTED]
Verzonden: vr 19-8-2005 14:33
Aan: [email protected]
CC:
Onderwerp: Re: [Wicket-user] Spring Integration
Hi
I did before
1 - 100 of 154 matches
Mail list logo
