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