Scott -
This _seems_ to be the case when you use the 1.0 version of the Spring
Client and 2.0.2 release and is actually related to parsing the
jbi-spring.xml.  If you grab the source and build the Spring Client in
the tooling directory, you can at least get by this error.  Make sure
to change the depends in the project.xml to the correct version.

While this will fix the parsing error, there seems to be a problem
mixing the 2.1-SNAPSHOT and the 2.0.2 release - so this is not a
complete fix, atleast for me.  If it works for you, please let me
know.

On 12/6/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Thanks Guillaume. jbi:jbi worked in creating the jbi package...
>
> Even with that, I sttill have trouble... running SM 2.0.2, standalone.
>
> The autodeploy works, meaning I see the exploded contents in the 
> wdir/defaultJBI/components directory.
>
> But its throwing an exception on parsing the jbi.xml.  Acting like it cannot 
> find
> the xsd, which is in place, and referenced in the schemaLocation (../jbi.xsd)
>
> "....../META-INF/jbi.xml] is invalid; nested exception is 
> org.xml.sax.SAXParseException: Document root element "jbi", must match 
> DOCTYPE root "null"........."
>
> Again this is from the Spring client example that I am trying to work 
> through...
> any help getting this up and running appreciated.
>
> Here's a stack dump.........
>
> 11:28:37,314 ERROR [InstallationService] Could not build Component: 
> jbi-test-sen
> der
> errorCode: 0
>        at 
> org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.ja
> va:323)
>        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown 
> So
> urce)
>        at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.RuntimeException: Unable to parse the jbi.xml
>        at 
> org.servicemix.client.DescriptorFactory.getDescriptor(DescriptorFacto
> ry.java:61)
>        at 
> org.servicemix.client.ClientEndPointRegistry.loadServiceUnitServices(
> ClientEndPointRegistry.java:314)
>        at 
> org.servicemix.client.ClientEndPointRegistry.loadComponentServices(Cl
> ientEndPointRegistry.java:298)
>        at 
> org.servicemix.client.SpringComponentLifeCycle.init(SpringComponentLi
> feCycle.java:130)
>        at 
> org.servicemix.jbi.container.JBIContainer.activateComponent(JBIContai
> ner.java:887)
>        at 
> org.servicemix.jbi.container.JBIContainer.activateComponent(JBIContai
> ner.java:838)
>        at 
> org.servicemix.jbi.framework.InstallerMBeanImpl.install(InstallerMBea
> nImpl.java:131)
>        at 
> org.servicemix.jbi.framework.InstallationService.buildComponent(Insta
> llationService.java:529)
>        at 
> org.servicemix.jbi.framework.InstallationService$1.run(InstallationSe
> rvice.java:495)
>        at 
> org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.ja
> va:291)
>        ... 2 more
>
> Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: 
> Line
> 3 in XML document from URL 
> [file:/C:/servicemix/servicemix-2.0.2/bin/../wdir/def
> aultJBI/components/jbi-test-sender/installation/META-INF/jbi.xml] is invalid; 
> ne
> sted exception is org.xml.sax.SAXParseException: Document root element "jbi", 
> must match DOCTYPE root "null".
>        at 
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
> nDefinitions(XmlBeanDefinitionReader.java:169)
> ...
>
>
> my jbi.xml .................
> <?xml version="1.0" encoding="UTF-8"?>
>
> <jbi xmlns="http://java.sun.com/xml/ns/jbi"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
> xsi:schemaLocation="http://java.sun.com/xml/ns/jbi ../jbi.xsd" version="1.0">
>  <component type="binding-engine">
>    <identification>
>      <name>jbi-test-sender</name>
>      <description>A new JBI component</description>
>    </identification>
>    <component-class-name description="Component 
> Implementation">org.servicemix.client.SpringComponent</component-class-name>
>    <component-class-path>
>      <path-element>lib/test-test-1.0.jar</path-element>
>      <path-element>lib/servicemix-client-1.0.jar</path-element>
>    </component-class-path>
>  </component>
>
> <services binding-component="false" xmlns:logger="http://tempuri.org/logger";>
>        <consumes interface-name="logger:log" service-name="logger:myLogger" />
> </services>
>
> </jbi>
>
>
> ----- Original Message -----
> >
> From: "Guillaume Nodet" <[EMAIL PROTECTED]>
> >
> To: <[email protected]>
> >
> Sent: Monday, December 05, 2005 3:40 PM
> >
> Subject: Re: [servicemix-user] Maven JBI Plugin 1.0 - bad?
> >
>
> >
>
> >
> > Could you try to run "jbi:jbi" instead of "jbi:generateInstaller" with the
> >
> > latest from the trunk ?
> >
> > It should work better.
> >
> >
> >
> > Cheers,
> >
> > Guillaume Nodet
> >
> >
> >
> > [EMAIL PROTECTED] wrote:
> >
> >
> >
> >>Trying to eval. servicemix and following the instructions in the docs with
> >
> >>the Spring Client Toolkit, the Maven JBI plugin is generating a bad
> >
> >>jbi.xml.  I looked through the source and see where it was fixed (7 days
> >
> >>ago), but a new build has not been created.  So I tried to download the
> >
> >>trunk and build the plugin myself (maybe dangerous! but I want this eval
> >
> >>to work!) the plugin built, but does not build out the zip file correctly
> >
> >>when running jbi:generateInstaller goal.
> >
> >>
> >
> >>Anyone got any constructive tips for me? Can a nightly build be done of
> >
> >>the tooling:maven-jbi-plugin? Or is it and I don't know where to look?
> >
> >>
> >
> >>Thanks
> >
> >>
> >
> >>
> >
> >>
> >
> >>
> >
> >>
> >
> >
> >
>
> >
>
>
>

Reply via email to