This content has been marked as final. Show 1 reply
Is mandatory registration already possible and the documentation just doesn't reflect this yet or are there any patches or hotfixes/hacks that would enable us to require registration for the WSRP customers? The system we're planning on implementing would require a mandatory registration scheme.
As specified in the documentation, registration on the producer side is not currently supported. It will be, however, as part of Portal 2.6. An alpha release containing this feature will be released by the end of 2006. I'd be interested in learning about your use cases though and how you intend to implement WSRP for your customers.
This is more of a general portlet/WSRP question. We haven't had time to test WSRP in action yet, we've just focused on creating some proof-of-concept portlets running on JBoss. When a user logs in to the WSRP customer's portal, am I correct in assuming that any setAttribute/getAttribute, getRemoteUser and similar-methods invoked in the RenderRequest will be based on the WSRP customer's session data. The reason I'm asking is that the system would use some data from the WSRP customer's user database to focus back-end searches on the corrent datasets.
I am not sure I understand your question properly. When you are talking of the "WSRP customer's session data" what exactly are you refering to? In JBoss Portal, a WSRP portlet (i.e. a portlet that happens to be located on a remote portal and interacted with via WSRP) is considered as a regular portlet. What this implies is that if you log into the portal that consumes remote portlets (the consumer) with a given identity, this will be the identity that will be propagated to the portlet via WSRP as long as it is covered by the WSRP protocol. Does that answer your question?
Let us know if you need more information.