felix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nanda Kishore Makkapati <msnkish...@gmail.com>
Subject Re: Dependency on Bundle Installation Order
Date Fri, 18 Nov 2011 18:55:45 GMT
Richard,

Unfortunately, I am supporting a product that uses Felix 1.8.1. I
understand that there should not be any but I am trying to figure out what
might be the reason in case if there are any.

Do you mean to say that having dependencies on installation order of
bundles is not possible?

Thanks,
Kishore

On Sat, Nov 19, 2011 at 12:04 AM, Richard S. Hall <heavy@ungoverned.org>wrote:

> It's not clear if this error has anything to do with the Felix framework
> or not, but if you are new to Felix you should consider getting a newer
> version of the framework...current version is 4.0.1.
>
> Generally, there should be no dependencies on installation order, since it
> shouldn't make a difference.
>
> -> richard
>
>
> On 11/18/11 13:19 , Nanda Kishore Makkapati wrote:
>
>> Hi,
>>
>> I am a newbie to Apache Felix. We are using Apache Felix 1.8.1. We have
>> got
>> the below exception when we started our application.
>>
>> org.springframework.beans.**factory.BeanCreationException: Error creating
>> bean with name 'org.springframework.aop.**aspectj.**
>> AspectJPointcutAdvisor#0':
>> Instantiation of bean failed; nested exception is
>> org.springframework.beans.**BeanInstantiationException: Could not
>> instantiate
>> bean class [org.springframework.aop.**aspectj.**AspectJPointcutAdvisor]:
>> Constructor threw exception; nested exception is
>> java.lang.**IllegalArgumentException: error at ::0 formal unbound in
>> pointcut
>>  at
>> org.springframework.beans.**factory.support.**
>> AbstractAutowireCapableBeanFac**tory$1.run(**
>> AbstractAutowireCapableBeanFac**tory.java:405)
>> [na:na]
>> at java.security.**AccessController.doPrivileged(**Native Method)
>> [na:1.6.0_27]
>>  at
>> org.springframework.beans.**factory.support.**
>> AbstractAutowireCapableBeanFac**tory.createBean(**
>> AbstractAutowireCapableBeanFac**tory.java:380)
>> [na:na]
>> at
>> org.springframework.beans.**factory.support.**AbstractBeanFactory$1.**
>> getObject(AbstractBeanFactory.**java:264)
>> [na:na]
>>  at
>> org.springframework.beans.**factory.support.**
>> DefaultSingletonBeanRegistry.**getSingleton(**
>> DefaultSingletonBeanRegistry.**java:222)
>> [na:na]
>> at
>> org.springframework.beans.**factory.support.**
>> AbstractBeanFactory.doGetBean(**AbstractBeanFactory.java:261)
>> [na:na]
>>
>> This exception seems to depend on the order in which the bundles are
>> getting installed. When the application was restarted, the order of the
>> installation of bundles changed and we did not get the error this time.
>>
>> We noticed that the order of start of bundles is already controlled in the
>> code but how can I identify the dependency on installation order?
>>
>> Thanks
>> Kishore
>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<users-unsubscribe@felix.apache.org>
> For additional commands, e-mail: users-help@felix.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message