On 2/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi Rahul, thank you very much for your reply. After reading your statement
that the dialog jars should not really effect my application, I removed
them from my WEB-INF/lib directory again. Actually i had tried this before
with no success, but it turned out that it was a problem with my eclispe
caching stuff (even after a refresh/clean/rebuild)! So I deleted my server,
created a new one, and was thrilled to see that i could go beyond what i
had before..:)

My happiness was short lived though.. and instead of going into the gory
details, let me ask you two things:

1. Is it necessary to add this in my web.xml:<listener>
      <listener>
            <listener-class>

org.springframework.web.context.ContextLoaderListener
            </listener-class>
      </listener>

*even though* I don't use spring in my application? I removed it but ran
into trouble and googling led me to this solution:
http://www.mail-archive.com/issues@shale.apache.org/msg00050.html
which made me think I ought to add in web.xml it anyways.. In any case my
app would not start up without it.. Am I right..?

2. The tiles uri I used to have before (in my jsps) was
http://jakarta.apache.org/tiles. However that doesn't work now and I now
use http://struts.apache.org/tags-tiles. Is this correct? (I got this uri
from the tld in tiles.core-2.0-r68346-SNAPSSHOT.jar).

I did 1 above in order to get rid of a java.lang.IllegalStateException: No
WebApplicationContext error. And I changed my uri as outlined in 2 above in
order to resolve a "I don't know what you mean by this uri" kind of
problem.

<snip/>

About (1), if you're not using Spring, better off taking out all
Spring jars and the shale-spring jar from the application. (2) sounds
correct, and it might change further now that Tiles is a top level
project at Apache. Again, seems unrelated to the 403 bit.

-Rahul


I am now back to the 403 (Access forbidden) page. Would I need to add
anything more/different in chain-config.xml? Or am I again barking up the
wrong tree?

btw, I don't access my logon.jsp directly either. My 'welcome-file list"
has index0.jsp. And index0.jsp forwards to index1.jsp using <jsp:forward
page="index1.faces"/>.. This has always worked before (before I did the
upgrade to the new shale/faces/tiles..)

Thank you very much again for your time; I really appreciate it!
Geeta

<snap/>

Reply via email to