Hi,
Anatoly Akkerman wrote:
> On Sat, 30 Jun 2001, Ole Husgaard wrote:
> > Are you talking about org.jboss.ejb.MethodInvocation?
> > Why should that class be Serializable?
> > It is only used locally on the server.
>
> It is indeed reconstructed from the transport layer representation of the
> i
Makes sense.
>
> Best Regards,
>
> Ole Husgaard.
>
> P.S: I'll better go nuke that TPC import in the MI
> now...
>
>
> "Jung , Dr. Christoph" wrote:
> >
> > -----Ursprüngliche Nachricht-----
> > >Von: marc fleury [mailto:[EMAIL PROTECTED]]
I
now...
"Jung , Dr. Christoph" wrote:
>
> -Ursprüngliche Nachricht-
> >Von: marc fleury [mailto:[EMAIL PROTECTED]]
> >Gesendet: Donnerstag, 28. Juni 2001 18:03
> >An: [EMAIL PROTECTED]
> >Betreff: RE: [JBoss-dev] METHOD-INVOCATION (introducing profi
I am not a very efficient programmer but will try to assist with this as
much as I can to get forward with my project.
I am available immediately :)
Anatoly.
On Thu, 28 Jun 2001, marc fleury wrote:
> |hence we could rely on a serializable HashMap or whatever.
> |
> |I´d be glad to assist you
|hence we could rely on a serializable HashMap or whatever.
|
|I´d be glad to assist you wherever possible in that respect ...
my schedule is
finish busy wait LW bug fixing (almost done)
commit URL based rabbit hole (almost done)
JMX'ify invocation chain in invoker->container, first beta rabbit h
-Ursprüngliche Nachricht-
>Von: marc fleury [mailto:[EMAIL PROTECTED]]
>Gesendet: Donnerstag, 28. Juni 2001 18:03
>An: [EMAIL PROTECTED]
>Betreff: RE: [JBoss-dev] METHOD-INVOCATION (introducing profiling
>support)
>I believe we should in fact move EVERYTHING to the
Jung
|, Dr. Christoph
|Sent: Thursday, June 28, 2001 4:05 AM
|To: '[EMAIL PROTECTED]'
|Subject: AW: [JBoss-dev] METHOD-INVOCATION (introducing profiling
|support)
|
|
|Hi all,
|
|let me generalize the argument of Anatoly a bit: It would be a tremendous
|help, if MI would be
|extendible, ei
atoly Akkerman [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 27. Juni 2001 23:23
An: [EMAIL PROTECTED]
Betreff: RE: [JBoss-dev] METHOD-INVOCATION (introducing profiling
support)
Hello, Marc and others.
This is a bit off-topic from the original thread but I've notices
something in Marc'
Hello, Marc and others.
This is a bit off-topic from the original thread but I've notices
something in Marc's answer that had strong resonance with my thoughts.
I am trying to come up with a comprehensive profiling support for J2EE
applications running on top of JBoss. This is necessary for a m
|When we get to support IIOP invocations, the CORBA
|invocation transport layer automagically imports
|incoming TPCs, and we never see a TPC that we can
|import.
Yes
|That means that we cannot do the TPC import in the
|transaction interceptors.
|I guess the same argument goes for optimized local
Hi,
Picking up an unresolved issue on an old thread.
marc fleury wrote:
> 1- TPC IMPORTER
> It doesn't really belong there.
>
> MI IS A REPOSITORY OF DATA FOR THE INVOCATION. IT IS NOT THE IMPORTER OF
> TRANSACTIONS.
>
> About the only thing I believe is elegant in this call is the "java:/"
>
>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 09, 2001 4:11 PM
Subject: RE: [JBoss-dev] METHOD-INVOCATION
> From SecurityInterceptor invoke()
>
> Object bean = mi.getEnterpriseContext().getInstance();
> EJBContext ctx = mi.getEnterpriseContext().get
> acquisition.. surprised you don't have NPEs everywhere
>
> Let's take it private, no need to bother the list with clean-ups
no keep it public, it is a good learning process.
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[EMAIL PROTECTED]
www.filip.net
_
AIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Wednesday, May 09, 2001 6:45 PM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] METHOD-INVOCATION
|
|
|Ok, right. I don't try to access the EnterpriseContext associated with the
|MethodInvocation and if I did, it would not
Ok, right. I don't try to access the EnterpriseContext associated with the
MethodInvocation and if I did, it would not have been set yet.
- Original Message -
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 09, 2001 3:13
|> 2- The security, do we associate the Principal to the ctx
|somewhere else? I
|> don't believe we should associate to the ctx (see warning in
|source, I also
|> need to update these). Scott do you take care of associating the
|ctx to the
|> principal somewhere else?
|>
|The prinicpal identity a
>
> 2- The security, do we associate the Principal to the ctx somewhere else? I
> don't believe we should associate to the ctx (see warning in source, I also
> need to update these). Scott do you take care of associating the ctx to the
> principal somewhere else?
>
The prinicpal identity and cre
1- TPC IMPORTER
It doesn't really belong there.
MI IS A REPOSITORY OF DATA FOR THE INVOCATION. IT IS NOT THE IMPORTER OF
TRANSACTIONS.
About the only thing I believe is elegant in this call is the "java:/"
context lookup to get the TPC importer. It is elegant but silly. The
container tx shou
18 matches
Mail list logo
