AW: [JBoss-dev] METHOD-INVOCATION (introducing profiling support)

[Jung , D. C. <chr...@in...>]

-----Urspr=FCngliche Nachricht-----
>Von: marc fleury [mailto:mar...@jb...]
>Gesendet: Donnerstag, 28. Juni 2001 18:03
>An: jbo...@li...
>Betreff: RE: [JBoss-dev] METHOD-INVOCATION (introducing profiling
>support)

>I believe we should in fact move EVERYTHING to the map, the user the =
method
>the tx everything
>so that the MI is just a big

>MI {
>Map
>}

>and in the map we have pairs
>user Object
>method Object
>params Object[]
>myInformationThatIOnlyUseInMyOwnLittleApplication
>Object[Maps[Array[OfMyStuff]]]]

>would that cut it?  yes we pay a price (map lookup) but it is on a =
small
>map.

that would perfectly cut it.

>The only tricky part is that it needs to be serializable, (or not =
actually
>but we would need to write the map item by item and catch the
>non-serializability).

as a first approach I would say that it is in the responsibility of the
invoker/interceptor
developers to either put only serializable instances in there or to =
remove
any non-serializable stuff
before returning to their predecessor in the chain

... now that I write it, there was once this idea of having
a "tree of responsibility" or at least of several invokers feeding the =
same
chain, maybe we could realise this also in RabbitHole? ...=20

hence we could rely on a serializable HashMap or whatever.

I=B4d be glad to assist you wherever possible in that respect ...
=20
CGJ