1 2 Previous Next 22 Replies Latest reply on Dec 19, 2006 6:40 PM by alesj Go to original post
      • 15. Re: Other IoC containers support
        alesj

         

        "alex.loubyansky@jboss.com" wrote:
        I tried to load this XSD w/o xml.xsd in the classpath and there was no problem. There was also no resource resolution. Commit or send me a testcase if it's still a problem.


        Funny, at first I again had problems - my test case failing, so I again added xml.xsd, but I tried it now - without xml.xsl - and it works like you said.

        But now I get different exception, which is bugging me for a while now: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=97354

        I'm going through the XB code - which source code branch is used with current XB binaries used in MC? So that debuging code matches.

        • 16. Re: Other IoC containers support
          alesj

           

          "alex.loubyansky@jboss.com" wrote:
          Commit or send me a testcase if it's still a problem.


          I get the same

          Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 5:28 s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'The "xml:" Namespace'.

          exception.

          If you could have a look at the Spring-int testcase (tests)?

          • 17. Re: Other IoC containers support
            aloubyansky

            It's the trunk that should be used with the MC. There were changes and the binary snapshot has not been updated yet.
            Ok, I'll check out the Spring-int tests. It's in the MC, right?

            • 18. Re: Other IoC containers support
              alesj

              I've added some more tests - mixing MC beans with Spring beans.

              Injecting Spring beans into MC's works, but the other way around I get this exception:

              org.jboss.xb.binding.JBossXBException: Failed to parse source: jar:file:/C:/ales/projects/microcontainer/spring-int/output/lib/jboss-spring-int-test.jar!/org/jboss/test/spring/test/InstantiateMixed2TestCase.xml@13,9
               at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:173)
               at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:133)
               at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:135)
               at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.deploy(MicrocontainerTestDelegate.java:196)
               at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.deploy(MicrocontainerTestDelegate.java:267)
               at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.setUp(MicrocontainerTestDelegate.java:77)
               at org.jboss.test.spring.test.TempSpringMicrocontainerTestDelegate.setUp(TempSpringMicrocontainerTestDelegate.java:47)
               at org.jboss.test.AbstractTestSetup.setUp(AbstractTestSetup.java:63)
               at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
               at junit.extensions.TestSetup.run(TestSetup.java:23)
              Caused by: java.lang.ClassCastException: org.jboss.xb.binding.sunday.unmarshalling.WildcardBinding
               at org.jboss.xb.binding.sunday.unmarshalling.DefaultElementHandler.setParent(DefaultElementHandler.java:109)
               at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endRepeatableParticle(SundayContentHandler.java:730)
               at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:138)
               at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:353)
               at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
               at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source)
               at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
               at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
               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.AbstractSAXParser.parse(Unknown Source)
               at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
               at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:169)
               ... 13 more
              
              


              This is the XML that is the cause of this

              <beans xmlns="urn:jboss:spring-beans:2.0">
              
               <bean id="testBean" class="org.jboss.test.spring.support.SimpleBean">
               <property name="refBean"><ref bean="oldBean"/></property>
               </bean>
              
               <bean xmlns="urn:jboss:bean-deployer:2.0" name="oldBean" class="org.jboss.test.spring.support.OldBean">
               <property name="javaBeanString">JavaBean</property>
               </bean>
              
              </beans>


              • 19. Re: Other IoC containers support
                aloubyansky

                The schema parsing failed because of

                <xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>


                You don't need to do that.

                • 20. Re: Other IoC containers support
                  alesj

                   

                  "alex.loubyansky@jboss.com" wrote:
                  The schema parsing failed because of
                  <xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>

                  You don't need to do that.


                  This solves the xml.xsd issue.

                  What about other interceptor mixup CCEs?

                  • 21. Re: Other IoC containers support
                    aloubyansky

                    Unless you are saying it's a bug in the xb, I'd like to spend the remaining days before the holidays on the cts.
                    Make sure that the SchemaBinding is initialized properly. I don't know the schema and how it should be bound to the Java model at the moment to give you any specifics.

                    • 22. Re: Other IoC containers support
                      alesj

                       

                      "alex.loubyansky@jboss.com" wrote:
                      Unless you are saying it's a bug in the xb, I'd like to spend the remaining days before the holidays on the cts.
                      Make sure that the SchemaBinding is initialized properly. I don't know the schema and how it should be bound to the Java model at the moment to give you any specifics.


                      Uf, it's hard for me to say it's a XB bug, but I did get different exceptions after snapshot update - so things did't behave the same, which introduces some skepticism.

                      SchemaBinding is simple, not a lot different from MC's - since we want to get the same effect.
                      I don't know the schema as well (pre-existing (slightly modified) Spring schema), but I did expect XB to behave the same as on top of MC's schema.
                      Java model is the same - MC's MetaData.

                      I can look in some more, but I'm really no xsd expert. And my introduction to XB was with 'home written' MC schema - and not binding Java model from existing schema, as it is used here.

                      1 2 Previous Next