On Wed, Jan 28, 2009 at 10:39 AM, Ignacio de Córdoba wrote:
>
> Oh yes, I have no problem with EJB3 init parameters. The only thing I am
> really missing is where to put struts2 actions init paramers.
If your parameters are action-specific, you can easily put them into
the struts.xml which declar
Oh yes, I have no problem with EJB3 init parameters. The only thing I am
really missing is where to put struts2 actions init paramers.
--
View this message in context:
http://www.nabble.com/Best-global-parameter-aproach-for-struts2-tp21698744p21702585.html
Sent from the Struts - User mailing lis
That is too bad. Injecting a Resource in Spring is a snap and you can do
cool things like load from the classpath when testing but then load from the
file system during runtime. You can store your parameters in a properties
file and then load that file into a Properties object.
Bummer your int
Thanks for your reply,
I have lots of code developed for struts1+tiles+EJB3 (Jboss). I am migrating
struts-tiles to struts2 + tiles2. I have too much EJB3 code and I don't have
a clear picture of where I can fit Spring there. I have so much time to
invest just to move to struts2... and absolutely
On Tuesday 27 January 2009 21:20:17 Ignacio de Córdoba wrote:
> Hi there,
> after starting some serious migration from struts to struts2 I am wondering
> is there is any "best practices" for global application parameters.
> I used to store this parameters in web.xml, but as struts2 finds important
5 matches
Mail list logo
