Ralph Goers wrote:
Well, I see that. But I just don't see how the urls ever get encoded
with the name. See my comments below.
Ok, short answer :) the name is used, you can see it in the sample
portal, but you're right that this mechanism does not prevent for
possible name clashes of the
In looking this over and it occured to me that if you are going to make
all events be convertable that:
a) we won't need the marshall events flag anymore,
b) It should end up that only the events needed to process the current
request will end up in the decode list of the DefaultEventConverter.
Ralph Goers wrote:
I've looked over the latest check-in and it occured to me that if you
are going to make all events be convertable that:
a) we won't need the marshall events flag anymore,
Yeah, I removed them :)
b) It should end up that only the events needed to process the current
Carsten Ziegeler wrote:
Ralph Goers wrote:
I have a concern over the hascode that is used in the
DefaultEventConverter. Although it may not be likely, hash algorithms
can return duplicate values so this is not guaranteed to always work.
Yes, you can configure a mapping on the event
