[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: sematics of overlapping QNames for navParams?
I've some questions regarding the QNames for navParams. I assume it is too late to restrict this to one QName instead of a QName list? ;-) Here a few scenarios: portlet 1: nav param aaa:p1, bbb:blub nav param aaa:p2 portlet 2: nav param bbb:blub, ccc:bla portlet 3: nav param ccc:bla, aaa:p2 questions: 1. what if portlet 1 creates an url setting bbb:bulb to "123"? Will it get the param under the name aaa:p1 or under bbb:blub? I didn't find anything in the spec about this. I expected to find that the portlet must only use the first entry in the QName list. 2. What is the happens when portlet 1 sets aaa:p1 = "111" ? Can portlet 2 receive this as new value bbb:blub? (I assume yes based on the current spec) Can portlet 3 receive it as new value for ccc:bla? (unclear to me from the current spec, it states: "SHOULD supply the same value to Portlets which provide a navigationalParameterDescription referencing the same QName in the names array", and ccc:bla is not on the QName list of portlet 1) Can portlet 1 receive it as new value for aaa:p2? 3. What happens if portlet 2 sets bbb:blub = "222" ? Can portlet 1 receive this as new value for aaa:p1 and portlet 3 as new values for ccc:bla? I assume yes. Based on the outcome of 2. (if the new values only gets distributed to potlet 2) this may now be strange that if portlet 1 set the new value it only gets distributed to portlet 2, but if portlet 2 sets the new value it gets distributed to portlet 1 and 3. So are we viewing these alias names as some kind of wires that the programmer can define? (Why is it then needed in the spec?) Or should they reference to the same global value? Stefan
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]