Actually, I was using Hivemind 1.1-beta-1, so I'm sure this is true.
Although, I could have missed the exception in the stack of exceptions.
Richard
________________________________
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 03, 2005 3:07 PM
To: [email protected]
Subject: Re: Autowiring Lesson Learned
In 1.1 I believe you'll see the exception (nested). 1.0 would log
and swallow the exception and return null. 1.1 will not swallow the
exception (for the dependent service) and this will result in an exception
on the main service.
On 5/3/05, Hensley, Richard <[EMAIL PROTECTED]> wrote:
I don't get the same error message, but it seems like a very
similar
problem. Core to the problem is that the service I want
depends on another
service that has an error in configuration. I get an error
on the service
I'm asking for, not on the service with an error in
configuration. I
wouldn't even care if one of the chained exceptions
indicated the error, but
something should.
Richard
________________________________
From: Liebig, Stefan
[mailto:[EMAIL PROTECTED]
Sent: Monday, May 02, 2005 9:43 PM
To: [email protected]
Subject: AW: Autowiring Lesson Learned
Is this HIVEMIND-65
( http://issues.apache.org/jira/browse/HIVEMIND-65
<http://issues.apache.org/jira/browse/HIVEMIND-65> )?
Stefan
________________________________
Von: Hensley, Richard
[mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ]
Gesendet: Di 03.05.2005 00:28
An: [email protected]
Betreff: Autowiring Lesson Learned
I just had a problem that took a while to chase
down. I kept getting
an
error that said can't find an appropriate
constructor to autowire,
use
explicit.
It turned out that the problem was another service.
I had misspelled
the
interface name and the service could never have been
bound and been
created,
however, I never saw that error because it was being
hidden by the
autowire
thing.
I'm not sure if this is a bug, or simply a lesson
learned to put
your
dependencies is approximately construction
requirement order so that
you can
see errors.
Does anybody have any suggestions as to how this is
best avoided?
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
