DefaultBootstrap

[Rob de Jong <ro...@urbidata.nl>]

Hello,

After upgrading from 3.1 to 3.1.1, the following exception's thrown
while installing a custom BC:

ERROR - InstallerMBeanImpl
      - Class not found: org.apache.servicemix.common.DefaultBootstrap

I've found references to this exception, that it's dependant on having
the servicemix-shared dependency set up properly, yet in the BC's
pom.xml, this is set. So I wonder if there's been a change in 3.1.1
that could explain this error?

Rob

Re: DefaultBootstrap

[Guillaume Nodet <gn...@gmail.com>]

The shared libraries are not available at bootstrap time. This class
is usually injected into the component at build time by the maven
plugin.

On 7/26/07, Rob de Jong <ro...@urbidata.nl> wrote:
> The problem's fixed. The error thrown was due to the fact that the
> Component class being referenced in the pom file could not be found.
> there'd been a slight change in the package name, and ever since the
> DefaultBootstrap was not able to find the Component anymore.
>
> > ERROR - InstallerMBeanImpl
> >        - Class not found:
> >          org.apache.servicemix.common.DefaultBootstrap
> > java.lang.ClassNotFoundException:
> >         nl.uds.broker.AKRReader.AKRComponent
> >         in classloader nl.uds.broker.AKRReader.AKRComponent
>
> The relevant snippet:
>       <plugin>
>         <groupId>org.apache.servicemix.tooling</groupId>
>         <artifactId>jbi-maven-plugin</artifactId>
>         <version>${servicemix-version}</version>
>         <extensions>true</extensions>
>         <configuration>
>           <type>binding-component</type>
>
> <component>nl.uds.broker.akrreader.jbi.AKRComponent</component>
>         </configuration>
>       </plugin>
>
> Cheers,
> Rob
>


-- 
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/

RE: DefaultBootstrap

[Rob de Jong <ro...@urbidata.nl>]

The problem's fixed. The error thrown was due to the fact that the
Component class being referenced in the pom file could not be found.
there'd been a slight change in the package name, and ever since the
DefaultBootstrap was not able to find the Component anymore.

> ERROR - InstallerMBeanImpl
>        - Class not found:
>          org.apache.servicemix.common.DefaultBootstrap
> java.lang.ClassNotFoundException:
>         nl.uds.broker.AKRReader.AKRComponent
>         in classloader nl.uds.broker.AKRReader.AKRComponent

The relevant snippet:
      <plugin>
        <groupId>org.apache.servicemix.tooling</groupId>
        <artifactId>jbi-maven-plugin</artifactId>
        <version>${servicemix-version}</version>
        <extensions>true</extensions>
        <configuration>
          <type>binding-component</type>
 
<component>nl.uds.broker.akrreader.jbi.AKRComponent</component>
        </configuration>
      </plugin>

Cheers,
Rob

RE: DefaultBootstrap

[Rob de Jong <ro...@urbidata.nl>]

Quick update to my own question:

> After upgrading from 3.1 to 3.1.1, the following exception's 
> thrown while installing a custom BC:
> 
> ERROR - InstallerMBeanImpl
>       - Class not found: org.apache.servicemix.common.DefaultBootstrap
> 
> I've found references to this exception, that it's dependant 
> on having the servicemix-shared dependency set up properly, 
> yet in the BC's pom.xml, this is set. So I wonder if there's 
> been a change in 3.1.1 that could explain this error?

It seems the assumption this was due to 3.1.1 was erroneous. I'm
having the same problem after having returned to 3.1.

The situation is as follows:
 A Component class (AKRComponent) extends DefaultComponent. The message
indicates the DefaultBootstrap's being called from within the
AKRComponent
or the DefaultComponent:
java.lang.ClassNotFoundException: nl.uds.broker.AKRReader.AKRComponent
in
classloader nl.uds.broker.AKRReader.AKRComponent

I'm continuing my search for it's cause. It seems there's a minor detail
I've forgotten that's causing this. Any pointers in the right direction
would be appreciated.

Rob