The portlet issue shouldn't cause the mangled interaction state. As far as WSRP
support with Microsoft, I don't know where you could ask. The WSRP
implementation in Sharepoint seems to have several issues...
View the original post :
ok, i'll post them asap.
In my topicstart, there are a couple of mistakes, due to the rendering i think.
Read the 's in the templates as
so e.g.
wsrp_rewrite?wsrp-urlType={wsrp-urlType}wsrp-url={wsrp-url}ws...
Should i change those 's to 's? If so, how can i change those?
View the
another try as there seems to be no edit modus. (keeps unescaping my escaped
ampersands)
jan.hoeve wrote : ok, i'll post them asap.
|
| In my topicstart, there are a couple of mistakes, due to the rendering i
think.
| Read the 's in the templates as amp ;
|
| so e.g.
This is the soap going from the jboss portal towards sharepoint: (of course the
unusefull information stripped out here).
beware: i put spaces between the ampersand sign and 'amp' and 'quot' etc.
This soap looks exact like the one which i intercept (no fiddling by this bb
forum)
|
It seems indeed like SharePoint is mangling the interaction state by appending
the navigational state to it. This seems like something you might want to see
with Microsoft as no WSRP producer can deal with modified interaction state
(which is supposed to be treated opaquely by the consumer).
chris.lap...@jboss.com wrote : It seems indeed like SharePoint is mangling
the interaction state by appending the navigational state to it. This seems
like something you might want to see with Microsoft as no WSRP producer can
deal with modified interaction state (which is supposed to be
Can you attach the SOAP request-response sequence for the action that is
failing, please?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208702#4208702
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4208702
