| Key: |
WW-1236
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Nils-Helge Garli
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
WebWork
Created: 12/Mar/06 11:41 AM
Updated: 14/Dec/06 02:31 PM
|
|
| Component/s: |
Views
|
| Affects Version/s: |
2.2.1
|
| Fix Version/s: |
2.2.2
|
|
|
Issue Links:
|
Related
|
|
This issue relates to:
|
|
WW-1266
URL tag - includeParams default is "n...
|
|
|
|
|
This issue is related to:
|
|
WW-1224
Portlet URL support doesn't follow JS...
|
|
|
|
|
|
|
in the URL component, there's a check if the 'includeParameters' and 'value' properties are null, and if this is the case, it's treated as if 'includeParameters' is set to 'GET'. This causes incorrect behaviour when deploying the sample portlets in uPortal, since the 'action' property is used instead of the 'value' property. The test looks like this:
if ((includeParams == null && value == null) || GET.equalsIgnoreCase(includeParams)) {
Is a test for 'action' == null deliberately left out of this, or is it a bug?
|
|
Description
|
in the URL component, there's a check if the 'includeParameters' and 'value' properties are null, and if this is the case, it's treated as if 'includeParameters' is set to 'GET'. This causes incorrect behaviour when deploying the sample portlets in uPortal, since the 'action' property is used instead of the 'value' property. The test looks like this:
if ((includeParams == null && value == null) || GET.equalsIgnoreCase(includeParams)) {
Is a test for 'action' == null deliberately left out of this, or is it a bug? |
Show » |
|
