I checkout the blueprint-core from trunk, which is currently at
1.1.0-SNAPSHOT, it it right? ) and build with apache-karaf
2.3.1-snapshot
upon startup with karaf.bat i got the following stderr
ERROR: Bundle org.apache.aries.blueprint.cm [13] Error starting
mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.0.0
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.aries.blueprint.cm [13]: Unable to resolve 13.0: missing
requirement [13.0] osgi.wiring.package;
(&(osgi.wiring.package=org.apache.aries.blueprint)(version>=1.0.0)(!(version>=1.1.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.aries.blueprint.cm [13]: Unable to resolve 13.0: missing
requirement [13.0] osgi.wiring.package; (&(osgi.wiring.package=o
rg.apache.aries.blueprint)(version>=1.0.0)(!(version>=1.1.0)))
at
org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3826)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)
at java.lang.Thread.run(Thread.java:662)
On Fri, Jan 18, 2013 at 10:37 AM, Dan Tran <[email protected]> wrote:
> would it be possible to have aries blueprint 1.0.2-snashot deployed?
>
> apache snapshot at
> https://repository.apache.org/content/repositories/snapshots/org/apache/aries/blueprint/org.apache.aries.blueprint.core/1.0.2-SNAPSHOT/
> is quite old
>
> Thanks
>
> -D
>
> On Fri, Jan 18, 2013 at 9:09 AM, Dan Tran <[email protected]> wrote:
>> cool, I will try to build my own version of karaf 2.3.1 snapshot to aries
>> 1.0.2
>>
>> Thanks
>>
>> -Dan
>>
>> On Fri, Jan 18, 2013 at 12:35 AM, Guillaume Nodet <[email protected]> wrote:
>>> Actually, I've raised and fixed
>>> https://issues.apache.org/jira/browse/ARIES-1004
>>> Can you see if the latest snapshots works better for you ?
>>>
>>>
>>> On Fri, Jan 18, 2013 at 8:26 AM, Guillaume Nodet <[email protected]> wrote:
>>>>
>>>> I fix a bunch of problems with blueprint shutting down recently, so could
>>>> you try with a recent blueprint snapshot and see if that helps ?
>>>> For now, blueprint bundles are shut down roughly according to their start
>>>> level. THere's something in blueprint which is supposed to better use the
>>>> bundle service usage and shutdown bundles so that the problem you see would
>>>> not happen, however, this only happen when the blueprint extender itself is
>>>> stopped, which in fact, does not really help because the extender has a
>>>> very
>>>> low start level and is thus stopped very late in the process.
>>>> Something that could be improved in blueprint is reacting to the fact that
>>>> a framework shutdown is initiated and do that orderly shutdown earlier in
>>>> the process.
>>>> In all cases, your bundles should be able to deal with cases where one
>>>> dependency is missing and be able to shutdown cleanly anyway.
>>>> So I would suggest you try with the latest blueprint snapshots and see if
>>>> it helps. I can write a patch to see if the modification i suggested above
>>>> would help (I think it should) if you want to give it a try.
>>>>
>>>>
>>>>
>>>> On Wed, Jan 16, 2013 at 9:31 PM, Dan Tran <[email protected]> wrote:
>>>>>
>>>>> Hi JB,
>>>>>
>>>>> I only try 2.3, my new work does not work with 2.2
>>>>>
>>>>> what is osgi/karaf shutdown sequencing flow? like it would shutdown
>>>>> all bundles with the same start- level in the order from high to low ?
>>>>>
>>>>> Thanks
>>>>>
>>>>> -D
>>>>>
>>>>>
>>>>> On Wed, Jan 16, 2013 at 12:18 PM, Jean-Baptiste Onofré <[email protected]>
>>>>> wrote:
>>>>> > Hi Dan,
>>>>> >
>>>>> > did you try both with Karaf 2.2.x and 2.3.x ?
>>>>> > did you see differences in the behavior ?
>>>>> >
>>>>> > Regards
>>>>> > JB
>>>>> >
>>>>> >
>>>>> > On 01/16/2013 09:17 PM, Dan Tran wrote:
>>>>> >>
>>>>> >> Hi I have a service's PreDestroy method which requires a service from
>>>>> >> other bundle during shutdown. However at shutdown time, blueprint make
>>>>> >> the required service 'unavailable'. Using start level ordering does
>>>>> >> not seem to help.
>>>>> >>
>>>>> >> What are your experiences dealing with this issue?
>>>>> >>
>>>>> >> Big thanks ahead.
>>>>> >>
>>>>> >> -Dan
>>>>> >>
>>>>> >
>>>>> > --
>>>>> > Jean-Baptiste Onofré
>>>>> > [email protected]
>>>>> > http://blog.nanthrax.net
>>>>> > Talend - http://www.talend.com
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> ------------------------
>>>> Guillaume Nodet
>>>> ------------------------
>>>> Blog: http://gnodet.blogspot.com/
>>>> ------------------------
>>>> FuseSource, Integration everywhere
>>>> http://fusesource.com
>>>
>>>
>>>
>>>
>>> --
>>> ------------------------
>>> Guillaume Nodet
>>> ------------------------
>>> Blog: http://gnodet.blogspot.com/
>>> ------------------------
>>> FuseSource, Integration everywhere
>>> http://fusesource.com
