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/[email protected]/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.
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
"Rahul Akolkar" <[EMAIL PROTECTED]> wrote on 02/24/2007 03:35:47 PM:
> On 2/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Hi all:
> >
> > I just downloaded the shale-framework-1.1.0-SNAPSHOT (dated today) and
> > after a bit of hastle got my server to at least start up (it was a
> > challenge since I use tiles too..(:(.
> >
> > My web.xml has this filter-mapping:
> > <filter-mapping>
> > <filter-name>shale</filter-name>
> > <url-pattern>/*</url-pattern>
> > <dispatcher>REQUEST</dispatcher>
> > <dispatcher>FORWARD</dispatcher>
> > </filter-mapping>
> >
> > However, when tomcat starts up I get the following warnings:
> >
> > [WARN] FacesConfigurator - More than one managed bean w/ the name of
> > 'org.apache.shale.dialog.MANAGER' - only keeping the last
> > [WARN] WebXmlParser - Ignored element 'dispatcher' as child of
> > 'filter-mapping'.
> > [WARN] WebXmlParser - Ignored element 'dispatcher' as child of
> > 'filter-mapping'.
> > [WARN] SCXMLLifecycleListener - No dialog configuration information
> > present. No default configuration found at:
/WEB-INF/dialog-config.xml.
> > No embedded configuration found at: META-INF/dialog-config.xml
> > [WARN] BasicLifecycleListener - No dialog configuration information
> > present. No default configuration found at:
/WEB-INF/dialog-config.xml.
> > No embedded configuration found at: META-INF/dialog-config.xml
> >
> <snip/>
>
> The three dialog related warnings are due to the fact that the app
> includes both shale-dialog-basic and shale-dialog-scxml jars. You get
> to pick one of the impls, see "API and Implementations" section:
>
> http://shale.apache.org/shale-dialog/index.html
>
> Removing one of those (of your choice) will reduce the number of
> warnings to one (assuming you still don't have a dialog-config).
> Alternatively, if you are not using dialogs, you might as well remove
> both (and the API jar, shale-dialog as well).
>
> The <dispatcher> warnings are probably related to this:
>
> https://issues.apache.org/jira/browse/MYFACES-1415
>
> and if so, they're inconsequential.
>
>
> > Since I am (as of now) not using dialogs I ignored the dialog warnings.
> > However, I think the WebXmlParser is in fact important because when I
try
> > to access my app, I get a 403 error ("Access to the specfied resource
()
> > has been forbidden"). My initial page does a forward and that is why i
> > think getting the WebXmlParser warning is important.
> >
> <snap/>
>
> Not sure what it is, a similar scenario is available in the
> shale-usecases war file (index.jsp has a <jsp:forward> to
> usecases.jsp), but accessing usecases.jsp does 403, IIRC.
>
> -Rahul
>
>
> > Btw, my chain-config.xml has this:
> >
> > <catalog name="shale">
> > <!-- Disallow direct access to JSP and JSFP resources -->
> > <chain name="preprocess">
> > <command
> > className="org.apache.shale.application.ContextRelativePathFilter"
> >
> > includes="\S*\.xml,\S*\.faces,\S*\.css,\S*\.html,\S*\.gif,\S*\.
> png,\S*\.js,\S*\.jpg,/index0\.jsp,/index1\.jsp,/index\.jsp,/test\.
> html,/assessmentDone,/createProcess,/dbPing\.do,\S*\.resources"
> > excludes="\S*\.jsp,\S*\.jspf"/>
> >
> > </chain>
> > </catalog>
> >
> > Can anybody give me a clue what's going on? .. Or at least why I get
the
> > WebXmlParser warning? Btw, my web.xml has this header:
> > <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> > http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";>
> >
> > Many thanks in advance for all help..:)
> > Geeta
> >
> >
> >
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
