JPJ wrote:
Should this be viewed as an issue of FORM tag implementation? I do not know
whether I am making a worthless statements but according my view we should
not prepend the web app context root to the action value in JSP while
rendering. Instead we should only prepend only the name space wit
oot+/WebAppContextRoot/Action).
The URI is now /webapp1/Login.action where I expect /Login.action. This
created problem for my apache rewrite rules. Is there anyway I can avoid
the
webapp context root to prepend to my action value in jsp while rendring
the
page? I think this is happening while re
The URI is now /webapp1/Login.action where I expect /Login.action. This
>> created problem for my apache rewrite rules. Is there anyway I can avoid
>> the
>> webapp context root to prepend to my action value in jsp while rendring
>> the
>> page? I think this is h
url is changed to
http://appserver:8080/webapp1/webapp1/Login.action(http://ServerName:port/WebAppContextRoot+/WebAppContextRoot/Action).
The URI is now /webapp1/Login.action where I expect /Login.action. This
created problem for my apache rewrite rules. Is there anyway I can avoid the
webapp
w /webapp1/Login.action where I expect /Login.action. This
created problem for my apache rewrite rules. Is there anyway I can avoid the
webapp context root to prepend to my action value in jsp while rendring the
page? I think this is happening while rendering the FORM tag.
I tried with namespa
Yea, I will do that.
But its still unsolved, so if anybody has got some solution, please
feel free to guide me.
Thank you..
On Thu, Feb 14, 2008 at 4:18 PM, Ian Roughley <[EMAIL PROTECTED]> wrote:
> This question will probably result in an answer / better solution if
> asked on the Spring forums.
This question will probably result in an answer / better solution if
asked on the Spring forums.
/Ian
--
Ian Roughley
From Down & Around, Inc.
Consulting * Training / Mentoring * Agile Process * Open Source
web: http://www.fdar.com - email: [EMAIL PROTECTED]
Rushikesh Thakkar wrote:
Thank
Thanks Ian and Laurie for looking into this.
Excuse me Laurie, for missing out an imp. info. that "web.xml also contains
spring ContextLoaderListener declaration".
I now feel that it is more a spring / tomcat issue and not a really a
struts2 issue.
I observed the tomcat's console logs while it was
> (3) web.xml doesn't contain anything but struts2 filter declaration.
If that's the case, how is Spring getting initialized? Usually you would
configure one of Spring's context listeners, which will take care of
loading the Spring context on startup and destroying it when the
application is s
Implement the ServletContextListener and configure it in web.xml - this
has the initialize and destroy methods you are looking for, and they are
called when the container loads and destroys your application.
/Ian
--
Ian Roughley
From Down & Around, Inc.
Consulting * Training / Mentoring * Ag
I want to release a database connection while reloading the context (using
Tomcat Manager web app) of a Struts2 Web Application. I am also using Spring
and hibernate. (Spring's HibernateTemplate, Spring SessionFactory and Apache
Commons-dbcp with HSql standalone-database)
As I am using HSql 'stand
11 matches
Mail list logo
