After going back through the WSRP v1 spec and seeing http://www.jboss.com/index.html?module=bb&op=viewtopic&t=102961 I'm thinking this is a problem in ICEfaces, where they're not using response.createRenderURL(). The portal that I'm trying to remote is actually a seam and ICEfaces portlet, so I'm quite sure how urls that are put into the facelets templates are handled, but I'll take it one step at a time.

I assume Chris would know if this is an ICEfaces problem or something within JBoss Portal. Thanks for any help anyone has to offer.

The title of your post got truncated so I'm not sure what your issue is, though I suspect it has to do with resources not being properly handled... Could you please detail the issue?Note also that resource support in our implementation of WSRP is not as complete as it should be since JSR-168 on which we aligned didn't not support this. We should improve resource support in 2.7 as we will now work on top of JBoss Portlet Container 2.0 which fully implements JSR-286.

Ah okay. Yeah I noticed that it was truncated after I posted. I have an ICEfaces + Seam portlet that I'm remoting. There are style sheets and javascript files that ICEfaces is putting into the resultant HTML so that it can do all the AJAX stuff (and make it look pretty). There are also some images in the application that we have used.

On the consumer end none of the images, css, or javascript are coming across. When I look at the HTML that is rendered all of those are relative paths back to the context of the war that was deployed in JBoss portal (JBoss is the Producer). The images we could probably make absolute in the source ourselves, but the main things are the javascript and css from ICEfaces.

I imagine these should be urlType=resource in WSRP terms, but I'm not sure if that's the case (the spec really doesn't make that clear in my mind). I'm wondering if this is a bug in JBoss Portal or if ICEfaces should be using absolute paths. Thanks for the help, hope that made more sense.