I've updated the following libs: - VFS --> 2.0.0.Beta14 - windows locking issue - better modification options - Microcontainer --> 2.0.0.Beta15 - few minor fixes - @Bean(Factory) - Deployers --> 2.0.0.Beta16 - Adrian's CL fixes - @annotation scanning improvement - few new helper deployers - JBossXB --> 2.0.0.CR9 - PersistenceMD fix - EJB3 --> 0.1.2 - ... - Persistence URL handling Code changes: - adding jboss-structure.xml to shutdown.sar, instructing it to do temp copy. - adding sys property to minimal server config, running in synch reaper mode. - updating Ejb3 deployer to use new PersistenceMD - this includes hack, since I forgot to handle (vfs)zip - going away with new ejb3 version; will fix it there As mentioned to Dimitris, I see errors when running AS with existing apps in deploy (they are present there before we do run.sh) - deployment are not able to find TransactionManager. I suspect this is effect of moving TM into deploy, and not having explicit dependency on it (again JNDI lookup). After my above mention changes Adrian's smoke tests produce more than 2-3 errors. :-( I think few of them are due to TM issue. I've commited it anyway, in order to move fwd with new MC artifacts (which I think are not the cause of those smoke failures - perhaps only some VFS impl detail assumption). _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

This doesn't explain me much. Could it be this: - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136749&a... "And I see that all persistence.xml's need namespace to be set. Or is this part of schema validation? Will no-namespace persistence.xml map to new PersistenceMetaData?" Dimitris Andreadis wrote: > The first results do not look promising: > > http://hudson.qa.jboss.com/hudson/view/TCK5/job/tck5-assembly/lastBuild/a... _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Yes, I see the same issue in tck. Might be the jbossxb update? http://jira.jboss.com/jira/browse/JBCTS-805 Andrew Lee Rubinger wrote: > Doubtful that it's related to the EJB3 API change. > > This is the same JBossXB issue that Anil and I saw earlier in the > week. The stacktrace is: > > Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse > source: Premature end of file. @ *unknown*[-1,-1] > at > org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:193) > > at > org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153) > > at > org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:191) > > at > org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:165) > > at > org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) > > at > org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) > > at > org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128) > > at > org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329) > > ... 65 more > Caused by: org.xml.sax.SAXException: Premature end of file. @ > *unknown*[-1,-1] > at > org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:438) > > at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(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.XMLErrorReporter.reportError(Unknown > Source) > at > org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(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:189) > > ... 72 more > > S, > ALR > > Ales Justin wrote: >> This doesn't explain me much. >> >> Could it be this: >> - >> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136749&a... >> >> "And I see that all persistence.xml's need namespace to be set. >> Or is this part of schema validation? >> Will no-namespace persistence.xml map to new PersistenceMetaData?" >> >> Dimitris Andreadis wrote: >>> The first results do not look promising: >>> >>> http://hudson.qa.jboss.com/hudson/view/TCK5/job/tck5-assembly/lastBuild/a... >> >> >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

This comes from xerces. XB re-throws. Dimitris Andreadis wrote: > All that changed in jbossxb is: > http://jira.jboss.com/jira/browse/JBXB-139 > > Dimitris Andreadis wrote: >> Yes, I see the same issue in tck. Might be the jbossxb update? >> >> http://jira.jboss.com/jira/browse/JBCTS-805 >> >> Andrew Lee Rubinger wrote: >>> Doubtful that it's related to the EJB3 API change. >>> >>> This is the same JBossXB issue that Anil and I saw earlier in the >>> week. The stacktrace is: >>> >>> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse >>> source: Premature end of file. @ *unknown*[-1,-1] >>> at >>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:193) >>> >>> at >>> org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153) >>> >>> at >>> org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:191) >>> >>> at >>> org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:165) >>> >>> at >>> org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) >>> >>> at >>> org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) >>> >>> at >>> org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128) >>> >>> at >>> org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329) >>> >>> ... 65 more >>> Caused by: org.xml.sax.SAXException: Premature end of file. @ >>> *unknown*[-1,-1] >>> at >>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:438) >>> >>> at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(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.XMLErrorReporter.reportError(Unknown >>> Source) >>> at >>> org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(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:189) >>> >>> ... 72 more >>> >>> S, >>> ALR >>> >>> Ales Justin wrote: >>>> This doesn't explain me much. >>>> >>>> Could it be this: >>>> - >>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136749&a... >>>> >>>> >>>> "And I see that all persistence.xml's need namespace to be set. >>>> Or is this part of schema validation? >>>> Will no-namespace persistence.xml map to new PersistenceMetaData?" >>>>

I tried with the previous jbossxb version and it still shows the problem. Maybe it's a VFS issue? Ales Justin wrote: > How come this didn't show before my update if this is xerces's issue? > I updated JBossXB to 2.0.0.CR9, but that brought in just one simple > change - as Dimitris also pointed. > > Alexey Loubyansky wrote: >> This comes from xerces. XB re-throws. >> >> Dimitris Andreadis wrote: >>> All that changed in jbossxb is: >>> http://jira.jboss.com/jira/browse/JBXB-139 >>> >>> Dimitris Andreadis wrote: >>>> Yes, I see the same issue in tck. Might be the jbossxb update? >>>> >>>> http://jira.jboss.com/jira/browse/JBCTS-805 >>>> >>>> Andrew Lee Rubinger wrote: >>>>> Doubtful that it's related to the EJB3 API change. >>>>> >>>>> This is the same JBossXB issue that Anil and I saw earlier in the >>>>> week. The stacktrace is: >>>>> >>>>> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse >>>>> source: Premature end of file. @ *unknown*[-1,-1] >>>>> at >>>>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:193) >>>>> >>>>> at >>>>> org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153) >>>>> >>>>> at >>>>> org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:191) >>>>> >>>>> at >>>>> org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:165) >>>>> >>>>> at >>>>> org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) >>>>> >>>>> at >>>>> org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) >>>>> >>>>> at >>>>> org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128) >>>>> >>>>> at >>>>> org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329) >>>>> >>>>> ... 65 more >>>>> Caused by: org.xml.sax.SAXException: Premature end of file. @ >>>>> *unknown*[-1,-1] >>>>> at >>>>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:438) >>>>> >>>>> at >>>>> org.apache.xerces.util.ErrorHandlerWrapper.fatalError(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.XMLErrorReporter.reportError(Unknown >>>>> Source) >>>>> at >>>>> org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(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:189) >>>>> >>>>> ... 72 more >>>>> >>>>> S, >>>>> ALR >>>>> >>>>> Ales Justin wrote: >>>>>> This doesn't explain me much. >>>>>> >>>>>> Could it be this: >>>>>> - >>>>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136749&a... >>>>>> >>>>>> >>>>>> "And I see that all persistence.xml's need namespace to be set. >>>>>> Or is this part of schema validation? >>>>>> Will no-namespace persistence.xml map to new PersistenceMetaData?" >>>>>> > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Can you create a test for it? And I'll get Marko to look at it. Sent from my iPhone On Jun 7, 2008, at 16:56, Dimitris Andreadis <dandread(a)redhat.com&gt; wrote: > It is an issue of the new VFS impl. It seems to be working if you > fall back to the old impl with -Djboss.vfs.forceVfsJar > > Dimitris Andreadis wrote: >> I tried with the previous jbossxb version and it still shows the >> problem. Maybe it's a VFS issue? >> Ales Justin wrote: >>> How come this didn't show before my update if this is xerces's issue? >>> I updated JBossXB to 2.0.0.CR9, but that brought in just one simple >>> change - as Dimitris also pointed. >>> >>> Alexey Loubyansky wrote: >>>> This comes from xerces. XB re-throws. >>>> >>>> Dimitris Andreadis wrote: >>>>> All that changed in jbossxb is: >>>>> http://jira.jboss.com/jira/browse/JBXB-139 >>>>> >>>>> Dimitris Andreadis wrote: >>>>>> Yes, I see the same issue in tck. Might be the jbossxb update? >>>>>> >>>>>> http://jira.jboss.com/jira/browse/JBCTS-805 >>>>>> >>>>>> Andrew Lee Rubinger wrote: >>>>>>> Doubtful that it's related to the EJB3 API change. >>>>>>> >>>>>>> This is the same JBossXB issue that Anil and I saw earlier in >>>>>>> the week. The stacktrace is: >>>>>>> >>>>>>> Caused by: org.jboss.xb.binding.JBossXBException: Failed to >>>>>>> parse source: Premature end of file. @ *unknown*[-1,-1] >>>>>>> at >>>>>>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:193) >>>>>>> >>>>>>> at >>>>>>> org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153) >>>>>>> >>>>>>> at >>>>>>> org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:191) >>>>>>> >>>>>>> at >>>>>>> org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:165) >>>>>>> >>>>>>> at >>>>>>> org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) >>>>>>> >>>>>>> at >>>>>>> org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) >>>>>>> >>>>>>> at >>>>>>> org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128) >>>>>>> >>>>>>> at >>>>>>> org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329) >>>>>>> >>>>>>> ... 65 more >>>>>>> Caused by: org.xml.sax.SAXException: Premature end of file. @ >>>>>>> *unknown*[-1,-1] >>>>>>> at >>>>>>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:438) >>>>>>> >>>>>>> at >>>>>>> org.apache.xerces.util.ErrorHandlerWrapper.fatalError(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.XMLErrorReporter.reportError(Unknown >>>>>>> Source) >>>>>>> at >>>>>>> org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(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:189) >>>>>>> >>>>>>> ... 72 more >>>>>>> >>>>>>> S, >>>>>>> ALR >>>>>>> >>>>>>> Ales Justin wrote: >>>>>>>> This doesn't explain me much. >>>>>>>> >>>>>>>> Could it be this: >>>>>>>> - >>>>>>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136749&a... >>>>>>>> >>>>>>>> >>>>>>>> "And I see that all persistence.xml's need namespace to be set. >>>>>>>> Or is this part of schema validation? >>>>>>>> Will no-namespace persistence.xml map to new >>>>>>>> PersistenceMetaData?"

The tck5-ejb30-persistence tests are mostly broken: http://hudson.qa.jboss.com/hudson/view/TCK5/job/tck5-ejb30-persistence/ They went from 46 failures to 1722 failures. Is the source of the parse exception your showing? Ales Justin wrote: > Can you create a test for it? > And I'll get Marko to look at it. > > Sent from my iPhone > > On Jun 7, 2008, at 16:56, Dimitris Andreadis <dandread(a)redhat.com&gt; wrote: > >> It is an issue of the new VFS impl. It seems to be working if you >> fall back to the old impl with -Djboss.vfs.forceVfsJar >> >> Dimitris Andreadis wrote: >>> I tried with the previous jbossxb version and it still shows the >>> problem. Maybe it's a VFS issue? >>> Ales Justin wrote: >>>> How come this didn't show before my update if this is xerces's issue? >>>> I updated JBossXB to 2.0.0.CR9, but that brought in just one simple >>>> change - as Dimitris also pointed. >>>> >>>> Alexey Loubyansky wrote: >>>>> This comes from xerces. XB re-throws. >>>>> >>>>> Dimitris Andreadis wrote: >>>>>> All that changed in jbossxb is: >>>>>> http://jira.jboss.com/jira/browse/JBXB-139 >>>>>> >>>>>> Dimitris Andreadis wrote: >>>>>>> Yes, I see the same issue in tck. Might be the jbossxb update? >>>>>>> >>>>>>> http://jira.jboss.com/jira/browse/JBCTS-805 >>>>>>> >>>>>>> Andrew Lee Rubinger wrote: >>>>>>>> Doubtful that it's related to the EJB3 API change. >>>>>>>> >>>>>>>> This is the same JBossXB issue that Anil and I saw earlier in >>>>>>>> the week. The stacktrace is: >>>>>>>> >>>>>>>> Caused by: org.jboss.xb.binding.JBossXBException: Failed to >>>>>>>> parse source: Premature end of file. @ *unknown*[-1,-1] >>>>>>>> at >>>>>>>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:193) >>>>>>>> >>>>>>>> at >>>>>>>> org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153) >>>>>>>> >>>>>>>> at >>>>>>>> org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:191) >>>>>>>> >>>>>>>> at >>>>>>>> org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:165) >>>>>>>> >>>>>>>> at >>>>>>>> org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) >>>>>>>> >>>>>>>> at >>>>>>>> org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) >>>>>>>> >>>>>>>> at >>>>>>>> org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128) >>>>>>>> >>>>>>>> at >>>>>>>> org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329) >>>>>>>> >>>>>>>> ... 65 more >>>>>>>> Caused by: org.xml.sax.SAXException: Premature end of file. @ >>>>>>>> *unknown*[-1,-1] >>>>>>>> at >>>>>>>> org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:438) >>>>>>>> >>>>>>>> at >>>>>>>> org.apache.xerces.util.ErrorHandlerWrapper.fatalError(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.XMLErrorReporter.reportError(Unknown >>>>>>>> Source) >>>>>>>> at >>>>>>>> org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(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:189) >>>>>>>> >>>>>>>> ... 72 more >>>>>>>> >>>>>>>> S, >>>>>>>> ALR >>>>>>>> >>>>>>>> Ales Justin wrote: >>>>>>>>> This doesn't explain me much. >>>>>>>>> >>>>>>>>> Could it be this: >>>>>>>>> - >>>>>>>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136749&a... >>>>>>>>> >>>>>>>>> >>>>>>>>> "And I see that all persistence.xml's need namespace to be set. >>>>>>>>> Or is this part of schema validation? >>>>>>>>> Will no-namespace persistence.xml map to new >>>>>>>>> PersistenceMetaData?" _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

This is what I've been asking here: - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156344#... "And I see that all persistence.xml's need namespace to be set. Or is this part of schema validation? (How) Will no-namespace persistence.xml map to new PersistenceMetaData?"