What you are seeing is exactly the right behaviour (well, depending
on where the NPE is coming from, but generally the right behaviour).
We don't want application code accessing system components as that
leads to all sorts of nasty issues (like major security holes).
So my first question is what are you trying to test and is it better
done as a unit test? That way you would be able to exercise all of
the code paths through your implementation giving good coverage
especially around boundary conditions.
If it is about integrating, what are you integrating with? Client
code? Host code? Each is likely to have different paths into the
runtime (based on default permissions etc.)
--
Jeremy
On Feb 23, 2007, at 2:50 PM, Luciano Resende wrote:
I have a contributionService system component
https://svn.apache.org/repos/asf/incubator/tuscany/branches/sca-
java-integration/sca/kernel/core/src/main/java/org/apache/tuscany/
core/services/deployment/ContributionServiceImpl.java
or
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/kernel/
core/src/main/java/org/apache/tuscany/core/services/deployment/
ContributionServiceImpl.java
I'm building a iTest and would like to get a reference to this system
component.
I have tried @Reference, @Autowire, but I keep getting a NPE.
Any ideas ?
--
Luciano Resende
http://people.apache.org/~lresende
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
