Hi Laci,

just do a bundle:refresh (without arg), it should work.

Regards
JB

On 09/15/2014 08:24 AM, Laci Gaspar wrote:
Hi Achim
That's an interesting point. Does that mean, if every time I install a
new version of a bundle containing a camel route, I have to refresh
camel-core?

thanks!
Laci



On 11.09.2014 08:40, Achim Nierbeck wrote:
If your bundle contains a camel route you have to refresh the camel
core bundle, cause that bundle holds references to the bundles
containing camel routes. Unless you refresh the camel-core bundle it
will still hold a reference to the old "route" as it didn't realize
it's been replaced.

regards, Achim


2014-09-11 8:36 GMT+02:00 Laci Gaspar <[email protected]
<mailto:[email protected]>>:

    Hi JB
    you put your finger right into it... I had a dynamic import of
    org.apache.cxf.bundle there...

    The strange thing is that when I removed it, uninstalled the
    bundle reinstalled it, it still didn't work.
    I had to restart karaf for it to take effect.

    Thanks anyway!
    Regards,
    Laci


    On 10.09.2014 19:28, Jean-Baptiste Onofré wrote:

        Hi Laci,

        do you use dynamic import for the bundle providing the Camel
        route ?

        Regards
        JB

        On 09/10/2014 05:02 PM, Laci Gaspar wrote:

            Hi

            I have a problem in one of my camer routes which is
            calling a WS from a
            bean class.

            I get the following error:
            java.lang.IllegalStateException: BeanFactory not
            initialized or already
            closed - call 'refresh' before accessing beans via the
            ApplicationContext
                 at
            
org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:171)


                 at
            
org.springframework.context.support.AbstractApplicationContext.containsBean(AbstractApplicationContext.java:1133)


                 at
            
org.apache.cxf.configuration.spring.ConfigurerImpl.configureBean(ConfigurerImpl.java:158)


                 at
            
org.apache.cxf.configuration.spring.ConfigurerImpl.configureBean(ConfigurerImpl.java:128)


                 at
            
org.apache.cxf.frontend.ClientProxyFactoryBean.configureObject(ClientProxyFactoryBean.java:105)


                 at
            
org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFactoryBean.java:133)


                 at
            
org.apache.cxf.jaxws.JaxWsProxyFactoryBean.create(JaxWsProxyFactoryBean.java:142)


                 at
            org.apache.cxf.jaxws.ServiceImpl.createPort(ServiceImpl.java:476)
                 at
            org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:343)
                 at
            org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:334)
                 at javax.xml.ws.Service.getPort(Service.java:46)[:2.2.0]
                 at
            
ch.curabill.msp.etg.messageResponseReceiver.MessageResponseSender.receiveMessageResponses(MessageResponseSender.java:89)[923:MessageResponseReceiver:1.2.0.SNAPSHOT]



            The WS is called using stubs created by cxf.
            I suspect that it is a problem of "wrong wiring" but I
            don't know how to
            solve it.

            Any ideas would be most welcome.

            Thanks
            Laci






--

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer & Project Lead
blog <http://notizblog.nierbeck.de/>

Software Architect / Project Manager / Scrum Master



--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to