Looks like it is probably a problem in the UrlSyntaxProviderImpl I'm not going to have a chance to take a look until after the 14th so if you're interested the easiest way to figure out the problem is to add another unit test to UrlSyntaxProviderImplTest (look at the diff against the previous version for an example, I just added a new test right before the release) then you can just work in the unit test to figure out why the parser isn't happy with the detached UrlState for a resource UrlType.

-Eric

On 9/2/11 11:51 AM, Jen Bourey wrote:
We've run across an issue in the uPortal 4 codebase that affects AJAX portlets 
in detached mode.  Essentially it appears that resource URL calls against the 
detached URL are issued a 302 redirect to the normal URL, like so:

http://localhost:8080/f/u12l1s5/p/news.u12l1n7/detached/resource.uP?pCc=cacheLevelPage
 ->  
http://localhost:8080/f/u12l1s5/p/news.u12l1n7/normal/resource.uP?pCc=cacheLevelPage.

This redirect only seems to occur in detached mode (not maximized), and only on 
the desktop (not mobile) theme.  I'm guessing that this might have to do with a 
difference in the syntax node helpers, but I've yet to find anything that looks 
to be causing it.

While this shouldn't actually break functionality, there also seems to be some 
sort of other issue with the redirected URL that's breaking the content.  I'll 
do further debugging, but I don't think we want to be using 302 redirects 
anyway since it will affect the browser-side performance of the page.

- Jen



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to