That resolver failure seems to suggest that
org.apache.aries.proxy-0.3-incubating-SNAPSHOT (although it is not clear which
bundle 17.0 refers to) has a dependency on org.osgi.service.framework, which it
does not seem to happen in my current workspace build. Does that rime with what
you can see
Hi Matt,
if I understand correctly this is not an intermittent problem. Is there a test
log (in target/surefire-reports) or a thread dump you could get from your
system and attach to say a JIRA?
This would really help since I have not seen a problem like this on my system
before :(
Regards,
Hi,
as I understand the spec (121.3.4) Blueprint should search in
OSGI-INF/blueprint for blueprint xml files (in both the host and fragments). If
you want it to locate things in META-INF/blueprint you should be able to the
Bundle-Blueprint manifest header like:
Bundle-Blueprint: META-INF/blu
Hi Thiago,
There is no way that I am aware of to do that. In the spec (121.3) a Blueprint
will only enter the grace period during the initialization phase to wait for
mandatory references. Once it is created it won't go back.
However, if a reference becomes untracked, services depend on it shoul
Hi Matt,
a bit is mentioned in http://aries.apache.org/modules/jpaproject.html, which is
under the general Documentation -> Programming Model link.
It's not particular verbose about injection in particular though :) Basically
it comes in two flavours, for both the namespace to use would be
htt
Hi Matt,
the stack trace looks like in the ITest there is no Aries JNDI provider (either
because it is not installed or has failed to start).
In the blog tests there is:
mavenBundle("org.apache.aries.jndi", "org.apache.aries.jndi" )
Plus at least the following dependencies I believe
tt
>
> On Mon, Apr 18, 2011 at 2:31 PM, Valentin Mahrwald
> wrote:
> Hi Matt,
>
> the stack trace looks like in the ITest there is no Aries JNDI provider
> (either because it is not installed or has failed to start).
>
> In the blog tests there is:
> m
ect, next time
>
> Thanks
> Matt
>
> On Tue, Apr 19, 2011 at 12:44 PM, Valentin Mahrwald
> wrote:
> Hi Matt,
>
> it is hard to say what is going wrong, from the stack trace though I can say
> that the OSGiInitialContextFactoryBuilder the root to all OSGi integration
Hi Matt,
the blueprint-ext namespace (unfortunately the URL as usual points into the
void) contains property placeholders (for the old config admin work), i.e.
properties containing placeholders like ${user.name}, and field injection (what
the RedBook referred to). The namespace itself is inclu
Hi Sandro,
this failure looks like it is actually caused by
org.apache.xbean.finder.BundleAnnotationFinder, which returns classes twice
when scanning a bundle with fragments. I'll raise a bug against Geronimo. In
the mean time
it should be easy to work around this in the Blueprint annotation co
Hi Matt,
as I read section 121.3.4 of the 4.2 enterprise spec the bean definition in the
fragment definitely should work. Other than a bug the only thing I can think of
is that the fragment is not attached at the time the Blueprint bundle is
scanned ...
Regards,
Valentin
On 25 May 2011, at 1
Hi Matt,
the waiting for namespace handlers message comes up when a bundle uses
additional namespaces in the Blueprint XML but at the time the bundle is
started the namespace handler service is not available. In the case of the
persistence bundle
I would imagine it is probably waiting for the J
Hi Christiano,
if I understand correctly you are using Blueprint annotation (or xml) for your
test bundle !?
I haven't seen any one do that and I doubt that would work since the test class
would be instantiated by the test runtime and not the Blueprint runtime, so
they would live in the wrong
nt runtime before to be able to automatically get a reference to
> another bundle service ?
> if so, it makes sense not being working :)
>
> cheers
>
> Cristiano
>
> On 14/06/11 08:05, Valentin Mahrwald wrote:
>> Hi Christiano,
>>
>> if I understand
Hi,
one approach that seems to cover some of the bases would be to consume the
BlueprintContainer object for your bundle from the service registry. After the
Blueprint xml is parsed and components are instantiated, a BlueprintContainer
service is published for the bundle (see
http://www.osgi.o
Hi Christoph,
as the system shows you don't need testsupport to get Blueprint running in
PaxConstruct or elsewhere. The test support bundle is meant for inclusion in
Pax Exam itests and as such depends on a junit bundle available in the runtime.
PaxExam has very convenient support for installin
16 matches
Mail list logo