Hi,
As a user and a consumer of Tuscany that has had to debug problems, I
have a couple of comments.
Raymond Feng wrote:
It seems to me that we could use the EventManagement in the core to
handle these in the event/listener pattern.
If possible, I would like to see Tuscany focus on the high
Hi,
Please see my comments inline.
Thanks,
Raymond
- Original Message -
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To:
Sent: Monday, April 23, 2007 10:48 AM
Subject: Re: Monitoring, logging, and exceptions (was: Re: Notifcation of
missing extensions)
[sn
[snip]
Raymond Feng wrote:
Hi, Simon.
[snip]
On the positive side this seems like an approach we could use that
separates logging/tracing from the application code. However you
still need
the aspectj runtime to weave the annotation based aspects into the
application classfiles right. I am att
rt a new discussion thread to discuss monitoring in general,
and try to come up with something that will be more usable and easier to
adopt through our whole runtime.
>
> Thanks,
> Raymond
>
> - Original Message - From: "Simon Laws"
> <[EMAIL PROTECTED]>
&g
Hi, Simon.
[snip]
On the positive side this seems like an approach we could use that
separates logging/tracing from the application code. However you still
need
the aspectj runtime to weave the annotation based aspects into the
application classfiles right. I am attracted by doing tracing with
quot;Raymond Feng" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, April 18, 2007 10:49 AM
Subject: Re: Monitoring, logging, and exceptions (was: Re: Notifcation of
missing extensions)
> Hi,
>
> Please see my comments below.
>
> Thanks,
> Raymond
>
> - Origin
I was referring to this mail [1] when I mentioned commons logging and SLF4J.
I don't know if its worth converting if you've already used LOG4J. SLF4J
does have some nice features though, particularly parameterized log
messages. You can read all about it at: http://www.slf4j.org.
...ant
On 4/18
thread to discuss monitoring in general,
and try to come up with something that will be more usable and easier to
adopt through our whole runtime.
>
> Thanks,
> Raymond
>
> - Original Message - From: "Simon Laws"
> <[EMAIL PROTECTED]>
> To: "tuscany
To:
Sent: Wednesday, April 18, 2007 10:49 AM
Subject: Re: Monitoring, logging, and exceptions (was: Re: Notifcation of
missing extensions)
Hi,
Please see my comments below.
Thanks,
Raymond
- Original Message -
From: "ant elder" <[EMAIL PROTECTED]>
To:
Sent: Wednes
Is SLF4J a better route than Log4j? If so, I wonder if we should convert
over the RDB DAS.
On 4/18/07, ant elder <[EMAIL PROTECTED]> wrote:
On 4/17/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
I found our current Monitor stuff difficult to follow as well. I suggest
> that we start
Hi,
Please see my comments below.
Thanks,
Raymond
- Original Message -
From: "ant elder" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, April 18, 2007 3:51 AM
Subject: Monitoring, logging, and exceptions (was: Re: Notifcation of
missing extensions)
On 4/17/07, Jean-S
Ant
Replies in line
On 4/18/07, ant elder <[EMAIL PROTECTED]> wrote:
On 4/17/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
I found our current Monitor stuff difficult to follow as well. I suggest
> that we start a new discussion thread to discuss monitoring in general,
> and try to
On 4/17/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
I found our current Monitor stuff difficult to follow as well. I suggest
that we start a new discussion thread to discuss monitoring in general,
and try to come up with something that will be more usable and easier to
adopt through
e runtime.
Thanks,
Raymond
- Original Message - From: "Simon Laws"
<[EMAIL PROTECTED]>
To: "tuscany-dev"
Sent: Tuesday, April 17, 2007 9:04 AM
Subject: Notifcation of missing extensions
I've been caught out a couple of times now by the runtime silently
f
gt;
To: "tuscany-dev"
Sent: Tuesday, April 17, 2007 9:04 AM
Subject: Notifcation of missing extensions
I've been caught out a couple of times now by the runtime silently failing
to work properly because I haven't put the correct set of extensions on my
classpath. Locally
I've been caught out a couple of times now by the runtime silently failing
to work properly because I haven't put the correct set of extensions on my
classpath. Locally I have just put a printout in to warn me.
DefaultStAXArtifactProcessorExtensionPoint
public Object read(XMLStreamReader sour
16 matches
Mail list logo
