As an alternative, I place all my properties in an LDAP server. In the
Application, I have a class that retrieves the properties.
On Sun, Mar 7, 2010 at 8:33 PM, James Carman ja...@carmanconsulting.comwrote:
And if you want live redeployment, you could use jrebel and their spring
plugin. I
That's an interesting idea. Ldap support is built into the jdk. Does that
make unit testing interesting or do you have all that stuff abstracted out?
On Mar 8, 2010 8:48 AM, T Ames tamesw...@gmail.com wrote:
As an alternative, I place all my properties in an LDAP server. In the
Application, I
Hi, I am new in Wicket.
I did Spring web applications before and I usually put an app's configuration
parameters in the application context file.
I would like to know the best practice in Wichet for setting parameters such as
SMTP server, LDAP server, etc. Where should I put them? I dont
Why not use Spring *with* Wicket?
On Sun, Mar 7, 2010 at 3:15 PM, David Chang david_q_zh...@yahoo.com wrote:
Hi, I am new in Wicket.
I did Spring web applications before and I usually put an app's configuration
parameters in the application context file.
I would like to know the best
David,
Given your requirements, I'd recomment putting them in a properties file
along side your custom WebApplication class for your particular application
and then inside of the WebApp's init method, reading in the properties file
and storing the information in the WebApplication.get/setMetaData
I use Spring IoC and do all of my app configuration with Spring still. I
just use Wicket for the webapp portion. There's no reason Wicket should
know about these SMTP / LDAP config values - all of that should be service
layer or below.
--
Jeremy Thomerson
http://www.wickettraining.com
On
Jeremy, thanks for chiming. I read your transition from Spring to Wicket long
time ago.
Best, David
--- On Sun, 3/7/10, Jeremy Thomerson jer...@wickettraining.com wrote:
From: Jeremy Thomerson jer...@wickettraining.com
Subject: Re: Where to put an application's configuration parameters
James and Riyad,
Thanks for your input. I really appreciate it. Wicket is great, but I still
feel a little elusive.
Regards.
--- On Sun, 3/7/10, James Carman jcar...@carmanconsulting.com wrote:
From: James Carman jcar...@carmanconsulting.com
Subject: Re: Where to put an application's
it. Wicket is great, but I still
feel a little elusive.
Regards.
--- On Sun, 3/7/10, James Carman jcar...@carmanconsulting.com wrote:
From: James Carman jcar...@carmanconsulting.com
Subject: Re: Where to put an application's configuration parameters?
To: us...@wicket.apache.org...
Date: Sunday
...@carmanconsulting.com
Subject: Re: Where to put an application's configuration parameters?
To: us...@wicket.apache.org...
Date: Sunday, March 7, 2010, 3:26 PM
Why not use Spring *with* Wicket?
On Sun, Mar 7, 2010 at 3:15 PM, David Chang david_q_zh...@...
And if you want live redeployment, you could use jrebel and their spring
plugin. I think it will reload beans based on property file changes
On Mar 7, 2010 7:17 PM, Riyad Kalla rka...@gmail.com wrote:
James,
Thanks for the link.
-R
On Sun, Mar 7, 2010 at 4:50 PM, James Carman
11 matches
Mail list logo
