Ok, I found out, how to submit the page before the popup is shown.
Deleting the line
<tc:attribute name="renderedPartially" value="popup1"/>
does it (always guessing and trying...).
But there's another problem. When a validation error occurs during
submit, there's no chance to prevent the popup from opening or to
show an other or modified popup. How do I react on validation errors
in this case?
Regards
Helmut
>Hello Volker,
>
>can you give me an example? I tried this:
>
> <tc:button label="#{bundle.button_label_freigeben}" id="popupButton1"
> action="#{mainController.popupAction1}">
> <tc:attribute name="renderedPartially" value="popup1"/>
> <f:facet name="popup">
> <tc:popup width="400" height="250" id="popup1">
> <tc:box label="#{bundle.box_label_freigeben}">
>...
> <tc:button label="#{bundle.button_label_save}" id="saveButton"
> action="#{mainController.saveAction1}">
> <tc:attribute name="popupClose" value="afterSubmit"/>
> </tc:button>
> <tc:button label="#{bundle.button_label_cancel}" id="cancelButton">
> <tc:attribute name="popupClose" value="immediate"/>
> <tc:attribute name="renderedPartially"
>value="genaPage:workflowPanel"/>
> </tc:button>
> </tc:box>
> </tc:popup>
> </f:facet>
> </tc:button>
>
>The page is definitely not submitted, before the popup shows up (by
>the popupButton1), but the popupAction1 is executed. When the popup is
>closed (by the saveButton), the page is submitted and saveAction1 is
>executed.
>
>Regards
>Helmut
>
>
>>Hello Helmut,
>>
>>no the old style of popup handling did not longer work, but should not
>>be a problem,
>>if you put a action to the opening command the action is executed
>>(including submitting all page content, but without rerendring).
>>
>>
>>Regards,
>> Volker
>>
>>
>>
>>2006/12/19, H. Swaczinna <[EMAIL PROTECTED]>:
>>> Hello Volker,
>>>
>>> aren't the old style popups supported anymore? I need both of them.
>>> The old ones, because I want the page to be submitted, before the
>>> popup is displayed, and the new ones for displaying some detail data
>>> or for short user prompts. I mixed both styles in one page and I got
>>> strange results. The old style popups work as expected, only when
>>> there's somewere in the page a new style popup with the same id!
>>> If there's no new style popup with the same id, the old style popup
>>> can not be closed. And under some cirumstances, a new style popup
>>> is displayed, when the old style popup should be closed. So both
>>> popups are displayed at the same time. These two popups have different
>>> ids.
>>>
>>> I'm using the current 1.0.10 snapshot.
>>>
>>> Regards
>>> Helmut
>>>
>>>
>>> >Hi Florian,
>>> >
>>> >the popup handling has changed in the last weeks.
>>> >
>>> >the rendered attribute of the popup-tag did not longer cause tho popup
>>> >to open (it just can suppress the popup).
>>> >You need a command with a tc:attribute inside to open or close a popup.
>>> >see the sourcecode of the sheetControll.jsp in the tobago-example-demo
>>> >there is a popup for the sheet config.
>>> >
>>> >Regards,
>>> > Volker
>>> >
>>> >2006/12/18, Florian Pfann <[EMAIL PROTECTED]>:
>>> >> Hello
>>> >> i'am using myfaces-tobago-1.0.9-SNAPSHOT. I have some problems with
>>> >> popus.
>>> >>
>>> >> The following side works with 1.0.8:
>>> >>
>>> >> <%@ taglib uri="http://myfaces.apache.org/tobago/component";
>>prefix="tc"%>
>>> >> <%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f"%>
>>> >> <%@ taglib uri="http://myfaces.apache.org/tobago/extension";
>>prefix="tx"%>
>>> >>
>>> >> <f:view>
>>> >> <tc:page width="750px" height="600px">
>>> >> <f:facet name="dpopup">
>>> >> <tc:popup width="300" height="100"
>>> >> rendered="true" id="dpopup">
>>> >> <f:facet name="layout">
>>> >> <tc:gridLayout rows="*" columns="*" margin="10px"
>/>
>>> >> </f:facet>
>>> >> <tc:cell>
>>> >> <tc:out value="Hello - i am a popup"
>>> >> id="idDPopupText" />
>>> >> </tc:cell>
>>> >> </tc:popup>
>>> >> </f:facet>
>>> >> </tc:page>
>>> >> </f:view>
>>> >>
>>> >> When i try it with 1.0.9, i get an empty page without the popup.
>>> >> I couldn't determine the error.
>>> >>
>>> >> Are there any sulutions for this problem or will it be resolved in the
>>> >> final version?
>>> >>
>>> >> (mayby the problem is sitting in front of the monitor ;-))
>>> >>
>>> >> Regards,
>>> >> Florian
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>>
