Re: [wsrp] Why are resource URLs not restricted in case of wsrp-resourceCacheabilityfull and portlet?

Just saw that there is some note of "These restrictions apply not only 
to the resource directly referenced, but also to any secondary resources 
the resource references, either directly or indirectly. "
So basically you could only create resource URLs of lower cacheability 
but not do much. Given that JSR 286 anyway rejects creating such URLs 
the Java Portlet API users are protected against this issue.

May seem like another thing to explain in our famous primer ;-)

Stefan

Stefan Hepper wrote:
> Hi,
> I was wondering why we only prohibited action and render urls for 
> wsrp-resourceCacheability full and portlet but do not mention that 
> resource urls also are restricted and should be of the same caching 
> level like the parent resource or stricter?
> 
> Stefan
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
>