What I meant to lead off with was that I got the Maven 2 jbi plugin working, but it doesn't seem to be generating deployable artifacts.

On 8-Mar-06, at 9:31 PM, Marc Tremblay wrote:

Caused by: org.xml.sax.SAXParseException: Document root element "jbi", must
match DOCTYPE root "null".
        at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException (Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
        at
org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified (Unknown
Source)
        at
org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement (Unknown
Source)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement (Unkno
wn Source)
        at
org.apache.xerces.impl.XMLDocumentScannerImpl $ContentDispatcher.scanRootElem
entHook(Unknown Source)

        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl $FragmentContentDispatc
her.dispatch(Unknown So
urce)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument (Unknown
Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
        at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
        at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBean Defini
tions(XmlBeanDefinition
Reader.java:161)
        ... 51 more


Generated jbi.xml (maven2-jbi-plugin)

<?xml version="1.0" encoding="UTF-8"?>
<jbi xmlns="HYPERLINK
"http://java.sun.com/xml/ns/jbi"http://java.sun.com/xml/ns/jbi";
version="1.0">
  <component type="service-engine">
    <identification>
      <name>logger</name>
      <description>Service :: Logger</description>
    </identification>

<component-class-name>org.servicemix.client.SpringComponent</ component-class
-name>
    <component-class-path>
      <path-element>logger-1.0-SNAPSHOT.jar</path-element>
      <path-element>lib/servicemix-2.0.2.jar</path-element>
      <path-element>lib/commons-logging-1.0.3.jar</path-element>
      <path-element>lib/mx4j-jmx-2.1.1.jar</path-element>
      <path-element>lib/servicemix-client-1.0.jar</path-element>
      <path-element>lib/jaxp-1.3.jar</path-element>
      <path-element>lib/spring-1.2.2-dev-2.jar</path-element>
    </component-class-path>

<bootstrap-class-name>org.servicemix.client.SpringBootstrap</ bootstrap-class
-name>
    <bootstrap-class-path>
      <path-element>logger-1.0-SNAPSHOT.jar</path-element>
      <path-element>lib/servicemix-2.0.2.jar</path-element>
      <path-element>lib/commons-logging-1.0.3.jar</path-element>
      <path-element>lib/mx4j-jmx-2.1.1.jar</path-element>
      <path-element>lib/servicemix-client-1.0.jar</path-element>
      <path-element>lib/jaxp-1.3.jar</path-element>
      <path-element>lib/spring-1.2.2-dev-2.jar</path-element>
    </bootstrap-class-path>
  </component>
</jbi>

I wrote a simple wrapper for Xerces and verified that the generated jbi.xml was in fact validated. I then downloaded Sun's JBI SDK to retrieve the schema definition (jbi.xsd) to use with a Xerces validator I wrote. From that I was able to determine that the jbi.xml would validate with this as
the root element tag.

<jbi xmlns="HYPERLINK
"http://java.sun.com/xml/ns/jbi"http://java.sun.com/xml/ns/jbi";
xmlns:xsi="HYPERLINK
"http://www.w3.org/2001/XMLSchema-instance"http://www.w3.org/2001/ XMLSchema-
instance" xsi:schemaLocation="HYPERLINK
"http://java.sun.com/xml/ns/jbi"http://java.sun.com/xml/ns/jbi ./ jbi.xsd"
version="1.0">

However, both JBoss and the standalone ServiceMix still give me the same
exception above when deployed with valid jbi.xml files.

Any ideas?

M.

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.2.0/275 - Release Date: 06/03/2006


Reply via email to