You can only have one standard page flow per directory. Each
directory maps to a corresponding directory under your web content
directory that contains that flow's related pages. As far as the
efficiency of this goes, I can't speak to that, but I would think each
page flow's efficiency would be roughly the same as a Struts module
(since that's what they map to underneath it all).
If you have 50 page flows then it seems it would get fairly "tall",
but that may just be the case because you have a large app, or maybe
I'm not real clear what you're trying to avoid. You might be able to
have some of your page flows become larger flows if that feels like
the right compromise.
On 5/21/06, Li <[EMAIL PROTECTED]> wrote:
Yeah,
I 'd tried group all controllers into a folder. But when i created many
flows (in my mind), the controller "tree" became very "tall". It looks like
as following:
/Controller
|__________ /Login (Controller)
|__________/ Process1 (Controller)
|__________/ Process2 ....
........
|__________/ Process 50
It involves a lot of file I/O work during runtime. Would be any more
efficient way or is it possible to just put all controllers into one folder
"e.g. /Controller" and rename Login controller as LoginController. (I tried
to do that, it doesnt work, i guess maybe i didnt find a correct way to do
that)
BTW, thanks for your suggestion on the Login module, Exception cost is
expensive in Java, if the login page is redirected cuz of the exception
handling, I 'd rather just use redirect or forward.
Regards
Li
On 5/20/06, Thomas Cook <[EMAIL PROTECTED]> wrote:
>
> Your observation that each folder typically has a controller is
> correct. In page flow thinking, a "section" is a folder.
>
> On 5/19/06, Li <[EMAIL PROTECTED]> wrote:
> > Hi, thanks for replying,
> >
> > I added any a filter into web.xml:
> > <filter-mapping>
> > <filter-name>PageFlowForbiddenFilter</filter-name>
> > <url-pattern>*.jsp</url-pattern>
> > <dispatcher>FORWARD</dispatcher>
> > <dispatcher>REQUEST</dispatcher>
> > <dispatcher>INCLUDE</dispatcher>
> > </filter-mapping>
> >
> > It works fine.
> >
> > Is it a must that every single functional folder should have its own
> > controller?
> > such like: /login --> Controller for login process
> > /profile --> Controller for profile
> create->confirm->submit
> > process ...
> >
> > Is it possible to just have one controller which controls all processes
> > section by section?
> >
> > On 5/19/06, AndreasWuest <[EMAIL PROTECTED]> wrote:
> > >
> > > In order to achieve that, you have to put your jsp pages under the
> > > WEB-INF directory. This works at
> > > least for "normal" web application using struts. don't know if this
> > > works with beehive as well, but i think so.
> > >
> > > regards,
> > > Andreas
> > >
> > > > Hi all,
> > > >
> > > > Any idea on preventing direct access to page, say, only allow "
> abc.do"
> > > > but
> > > > not "a/b/c/abc.jsp"?
> > > >
> > > > Regards
> > > >
> > >
> > >
> > >
> >
> >
> > --
> > =====================================
> > The world will be ended if love is everywhere.
> > ---- Shawzi
> >
> >
>
--
=====================================
The world will be ended if love is everywhere.
---- Shawzi
