on 01-25-2008 12:35 PM
In the portal a message apperars and then it quickly disappears again on the view.
If I run this application ouside portal then it doesn't disappear. With outside I mean
as standalone WebDypro-application .
Regards
sas
As someone in your previous posting suggested, it could be that your application reacts to an event, in this case a portal event. After such an event, the controller code is triggered (round trip), and the view refreshes, which causes your message to disappear.
Try to look where in your application a portal event is processed. (Listened to)
Good luck, Roelof
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Knibbe!
That was exactly the problem, I have got it.
These two methods were called within wdDoInit() and wdDoExit().
Can you explain to me what these methods are doing ?
private void subscribeToPortalEvents() {
WDPortalEventing.subscribe( Constants.TM_PORTAL_NAVIGATION_NAMESPACE,
Constants.TM_PORTAL_NAVIGATION_EVENT,
wdThis.wdGetPortalNavigationAction() );
WDPortalEventing.subscribe( Constants.PORTAL_COMMUNICATION_NAMESPACE,
Constants.PORTAL_EVENT_CLOSE_VIEW,
wdThis.wdGetCloseUpdateViewAction() );
}
private void unsubscribeFromPortalEvents() {
WDPortalEventing.unsubscribe( Constants.TM_PORTAL_NAVIGATION_NAMESPACE,
Constants.TM_PORTAL_NAVIGATION_EVENT,
wdThis.wdGetPortalNavigationAction() );
WDPortalEventing.unsubscribe( Constants.PORTAL_COMMUNICATION_NAMESPACE,
Constants.PORTAL_EVENT_CLOSE_VIEW,
wdThis.wdGetCloseUpdateViewAction() );
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
What exactly does it mean ?
How can I set the configuration to avoid this circumstance ?
Rgd
sas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Forget it. I don't think the iView configuration is the cause. As I said, I don´t know much about that.
Do you have any statements in you app like:
WDPortalEventing.subscribe(arg1, arg2, ...)
Do you have methods defined in your app where the event source column is not empty?
If so, these could be the cause.
Good luck, Roelof
Though I have little knowledge of portal, it may be that the configuration of the portal iView that embeds your WD app is the cause.
Good luck, Roelof
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.