Leszek Gawron wrote:
Berin Loritsch wrote:
Leszek Gawron wrote:
If you are trying to apply MVC here you're failing. You should not be
calling pages/displayHome.xsp but some displayHome flowscript function.
The flowscript function prepares the bean and does cocoon.sendPage(
"pages/displayHome" ) which is matched to:
> <map:match pattern="pages/displayHome.xsp">
> <map:aggregate element="page">
> <map:part src="cocoon:/header.xsp"/>
> <map:part src="cocoon:/pages/showFoo"/>
> <map:part src="cocoon:/footer.xsp"/>
> </map:aggregate>
> </map:match>
> <map:match pattern="pages/showFoo">
> <map:generate src="bean.jx" type="jx"/>
> <map:serialize type="xml"/>
> </map:match>
It means:
1. you invoke the controller
2. the controller performs business logic and prepares data for view
3. with cocoon.sendPage you call your view
In your case it is all pretty mixed up.
So how would you fix it, assuming we wanted to aggregate different
pieces into one page? Those peaces are used elsewhere in the
program. Your comments weren't particularly helpful to either point
to the specifics of how to expect flowscript to work or how to correct
the code as it is.
Seon's on my team, so I have a vested interest in getting this issue
resolved.
let me see:
function login() {
setupMyFoo();
home();
}
function home() {
var foo = accessTheFoo();
cocoon.sendPage( "displayHome", { bean: foo } );
}
and now the sitemap:
<map:match pattern="displayHome">
<map:aggregate element="page">
<map:part src="cocoon:/header.xsp"/>
<map:part src="cocoon:/showBean"/>
<map:part src="cocoon:/footer.xsp"/>
</map:aggregate>
</map:match>
<map:match pattern="showBean">
<map:generate src="bean.jx" type="jx"/>
<map:serialize type="xml"/>
</map:match>
<map:match pattern="login">
<map:call function="login"/>
</map:match>
<map:match pattern="home">
<map:call function="home"/>
</map:match>
Sorry if I sounded rude at first.
If you need it you can make your flowscript call login only when needed:
function main() {
cocoon.response.setHeader( "Expires", "-1" );
cocoon.response.setHeader( "Cache-Control", "no-cache" );
cocoon.response.setHeader( "Pragma", "no-cache" );
var action = cocoon.parameters["action"];
if ( springContext == null )
setupSpringContext();
if ( cocoon.session.user == null ) {
loginInternal();
}
invoke( action );
}
function invoke( action ) {
var func = this[ action ];
if ( func != undefined )
func.apply( this );
else
cocoon.sendPage( action, {} );
}
the sitemap:
<map:match pattern="*.do">
<map:match type="request-parameter" pattern="continuation-id">
<map:call resource="resume-continuation">
<map:parameter name="continuation-id"
value="{1}"/>
</map:call>
</map:match>
<map:call function="main">
<map:parameter name="action" value="{1}"/>
</map:call>
</map:match>
this way you can just call
http://localhost:8888/home.do
and the "main" function will be called which will detect if user is
logged in. If not login screen is shown first and later the home()
function is being run (with func.apply() ).
It's a poor's man intercepted flow.
--
Leszek Gawron [EMAIL PROTECTED]
IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
