Hii Craig,

Thanks for your response and clarification. 

I agree that the Struts-Faces library uses JSF URLs
and for make them into use in my application, i need
to change the handling.

But, I have a very dull feeling about using
Struts+Faces together. Moreover things are not going
fine together with different implementations. Just for
curiosity, How Shale is going to make use of JSF in
View?? Isn't it be the same way?

Regards
fargo



--- Craig McClanahan <[EMAIL PROTECTED]> wrote:

> One issue you'll have is that the Struts-Faces
> library uses JSF URLs
> (*.faces in your case) for all form submits, so your
> filter on *.do
> patterns will never execute.  You'll likely need an
> alternative
> approach to do that kind of processing.
> 
> In addition, as of MyFaces 1.0.7 (when it was at
> SourceForge) there
> were still some fatal bugs in MyFaces that prevented
> it from working
> with the Struts-Faces library.  I don't believe all
> of them have been
> fixed yet, but will be doing some review of that as
> the Struts-Faces
> library approaches being released.
> 
> Craig McClanahan
> 
> 
> On Tue, 30 Nov 2004 05:39:58 -0800 (PST), No Galz
> <[EMAIL PROTECTED]> wrote:
> > Hii All,
> > 
> > I have setup the MyFaces+Struts+StrutsFaces in the
> > following way
> > 
> > --> myfaces jars, struts-faces.jar, jstl.jar,
> > standard.jar added to lib
> > 
> > --> add facesrequest processor to the
> > struts-config.xml (without tiles impl.)
> > 
> >    <controller nocache="true" >
> >           <set-property property="inputForward"
> value="true"
> > />
> >           <set-property property="processorClass"
> >
>
value="org.apache.struts.faces.application.FacesRequestProcessor"
> > />
> >   </controller>
> > 
> > --> add MyFaces' ContextListener to web.xml with
> reqd.
> > context
> > --> parameters
> > 
> >         <context-param>
> > 
> >
>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> > 
> >                 <param-value>client</param-value>
> >         </context-param>
> > 
> > <!-- Myfaces implementation listener
> initialisation
> > -->
> >  <listener>
> > 
> >
>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
> > 
> >  </listener>
> > 
> > --> added JSF Servlet configuration and change the
> > load-on-startup attribute to load JSF at the start
> > -->then struts and -->then the application servlet
> > 
> >   <!--  JavaServer Faces Servlet Configuration -->
> >   <servlet>
> >   <servlet-name>faces</servlet-name>
> > 
> >
>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
> > 
> >   <load-on-startup>1</load-on-startup>
> >   </servlet>
> > 
> > --> adding the servlet mapping too
> > 
> >  <!--  JavaServer Faces Servlet Mapping -->
> >  <servlet-mapping>
> >   <servlet-name>faces</servlet-name>
> >   <url-pattern>*.faces</url-pattern>
> > </servlet-mapping>
> > 
> > I have a SevletFilter which is configured with a
> > pattern of *.do (same as my Struts Action Servlet
> > mappings)
> > ServletFilter is used as a mode of authentication,
> for
> > each page request.
> > 
> > I expect my Struts based application to work as it
> is,
> > b'coz i m not using any struts-faces tags or faces
> tag
> > at the moment.
> > 
> > But with the first click...i got the following
> error
> > from myfaces
> > 
> > could not find pathMapping for servletPath =
> > /loginCheck.do requestPathInfo = null
> > 
> > at
> >
>
org.apache.myfaces.application.jsp.JspViewHandlerImpl
> > 
> > Moreover, i m used the latest of
> everything..myfaces,
> > struts-faces.
> > 
> > I m trying it hard, b'coz i want to leverage the
> > benefits of JSF with my existing (quite BIG)
> struts
> > based application.
> > 
> > Any feedback will be a big help for me.
> > 
> > Thanks,
> > fargo
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > All your favorites on one personal page – Try My
> Yahoo!
> > http://my.yahoo.com
> >
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to