A hearty +1 from me as well.
The one thing that I think would be awesome is if I could use @Inject
for more than just the BundleContext...I want to use it for services.
For example, if I say:
@Inject
private FooService fooService;
Then it'd be great for Pax Exam to lookup a service that implements
FooService. Or...
@Inject
private FooService[] fooServices;
Then it would inject a collection of services when there are more than
one matching service.
This would save me from having to work directly with the OSGi API to
lookup services in my tests. And it would fill the gap between Pax Exam
and Spring-DM's testing support.
FWIW, I just added this as PAXEXAM-41.
David Leangen wrote:
I just started using Pax Exam for a new experiment. I expected it to
be a lot harder to use than it was.
+1
+1
I also just started using it last week. It's really nice!!
The basics are all there, so additional features are additional sugar
to make things even smoother.
BTW...
I was thinking: sometimes I need to run automated processes in a
periodic manner, without having a 24/7 container. The lifecycle is
essentially the same: provision, start, run, shutdown.
I wonder if it would be a good idea to use the current codebase for
something like a "pax process", and make pax-exam an implementation of
that more general project.
wdyt?
Cheers,
=David
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
