cancel
Showing results for 
Search instead for 
Did you mean: 

bsp:call with page.htm, instead of controller.do ?

daniel_humberg
Contributor
0 Kudos

I usually call my subcontrollers with


<bsp:call url="mycontroller.do" comp_id = "mc1">
</bsp:call>

Now I tried to call an "ordinary" page with flow logic like this


<bsp:call url="mypage.htm" comp_id = "mp1">
</bsp:call>

but I get the bsp error "Call of BSP page terminated due to error." (which does not help much).

Is it not possible to call pages with flow logic like this?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

You can call a Page with flow logic using:

navigation->next_page( '<i><navigation_request></i>' ).

Now click on the name of your BSP Application in the left pane.

Click on "Navigation" Tab in the right pane.

Enter the name of the navigation request you made in the call to page.

Give start page and target page for the navigation request created by you.

Hope this solves your problem.

daniel_humberg
Contributor
0 Kudos

but with

navigation->next_page or

navigation->goto, i will not embed the new page into the other page (that's want I want), but go to the new page completely.

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

See with MVC you aren't really imbedding pages within each other. Your are just processing chunks of views (logical representation - not a physical page) together to create one single page.

You can acomplish the same with pages and flow logic in two different ways. First you could change your inner page to be a page fragment - then it could be processed in line like you desire. However I despise page fragements for several reasons (no debugging, expanded in place, etc).

You might want to consider instead just using normal HTML constructs like the iFrame to imbed the other page into your current one. However this other page has a life of its own and can't share data in the processing flow.

daniel_humberg
Contributor
0 Kudos

Ok, then I will just transform my page with flow logic into a view+controller.

That's the most elegant way in this situation, I think.

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

>That's the most elegant way in this situation, I think.

Without a doubt!

Answers (0)