RE: performblockinginteraction

[Schelling Bernhard <Be...@lemon42.com>]

performblockinginteraction solved:

...portletInstanceKey: An opaque string, unique within the
RegistrationContext

my fault - forgot to change this in the performblockinginteraction
request -
an error message would have been nice.
still interested in the mysterious appearing registrationHandle :)

regards 
bernhard


> -----Original Message-----
> From: Schelling Bernhard 
> Sent: Tuesday, March 07, 2006 5:45 PM
> To: wsrp4j-user@portals.apache.org; wsrp4j-dev@portals.apache.org
> Subject: RE: performblockinginteraction ...
> 
> 
> hi,
> 
> > i'm trying to implement a simple consumer for our cms, using
> > tomcat & wsrp4j as a producer. everything worked ok so far 
> > but now i'm stuck: the performblockinginteraction url quits with an
> errormessage. 
> > Since I'm struggling for a while now - maybe someone can point me in
> the 
> > right direction....
> 
> one step further: i think my problem is related to 
> portletHandle or Registrationcontext
> 
> At the Moment my consumer starts as follows (pseudocode) 
> ============================================================
> GetServiceDescription 
> 	if registrationrequired
> 		register
> 		 new ServiceDescriptionrequest
> 	endif
> 
> getportlehandle_from_servicedescription
> getregistrationcontext_from_servicedescription
> 
> if initcookirequired
> 	initcookie
> endif
> 
> getmarkup
> -- klick on urlType=blockingAction
> performblockinginteraction
> 
> 
> the funny thing is:
> if i listen to the communication of  wsrp4j producer/ 
> proxyportlet consumer, the very first request starts with 
> getServiceDescription AND
> 
> <registrationHandle>80.81.129.128_1141738525596_0</registrationHandle>
> 
> where did the consumer get this handle from? no prior 
> requests, no registerRequest, the next request is initCookie :(
> 
> thanks for hints!
> bernhard 
> 
> 
> 
>