I had a similar issue. The jfwid wasn't used in my project. I had to manually
set the client window render mode with a
@Specializes
public class MyJsfModuleConfig extends JsfModuleConfig {
@Override
public ClientWindowConfig.ClientWindowRenderMode getDefaultWindowMode() {
return ClientWindowRenderMode.DELEGATED;
}
}
After adding that file everything worked fine.
Regards
Ortwin Escher
________________________________________
Von: Gerhard Petracek [[email protected]]
Gesendet: Mittwoch, 9. Juli 2014 20:29
An: [email protected]
Betreff: Re: JSFModule - windowId
short addition:
i've tested it and it works as described before.
@juliano:
it would be great if you can provide a link to a demo which illustrates the
issue.
regards,
gerhard
2014-07-09 18:12 GMT+02:00 Gerhard Petracek <[email protected]>:
> @thomas
> yes - once the jsf 2.2+ client-window feature is enabled, deltaspike
> should just use the information provided by jsf itself.
> (-> ds:windowId can't be used.)
>
> regards,
> gerhard
>
>
>
> 2014-07-09 16:40 GMT+02:00 Thomas Andraschko <[email protected]>
> :
>
> @Gerhard
>> We only append the dswid if
>> DefaultClientWindow#isClientWindowRenderModeEnabled and this is only the
>> case when the mode is LAZY.
>> AFAIR, we set the mode to DELEGATED when JSF 2.2 is available.
>> So this should actually not occur.
>>
>>
>> 2014-07-09 16:19 GMT+02:00 Juliano Marques <[email protected]
>> >:
>>
>> > Hi,
>> >
>> > Why is jfwid appended to the url when ds window handling is active
>> > (dswid)?
>> > jfwid and dswid have the same purpose, don't have?
>> >
>> > I searched in internet, mailing list... Maybe I'm missing something...
>> >
>> > I use DS 1.0.0 with JSFModule, no module config changed.
>> >
>> > Regards,
>> > Juliano
>> >
>> >
>> >
>>
>
>
