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
