[JBoss JIRA] Created: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
3:38 a.m.
Should we add a relax flag for people using out of order content inside elements of their
XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://jira.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Deployers
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Ales Justin
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:52 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://jira.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin.sy...
]
Ales Justin reassigned JBAS-8268:
---------------------------------
Assignee: Alexey Loubyansky (was: Ales Justin)
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://jira.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:52 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://jira.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin.sy...
]
Ales Justin updated JBAS-8268:
------------------------------
Component/s: XML services
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://jira.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:51 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://jira.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin.sy...
]
Alexey Loubyansky commented on JBAS-8268:
-----------------------------------------
But there is such a flag as you wrote on the original issue, i.e. it's the validation
on/off one. What's different between these AS versions is the default for XML
validation.
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://jira.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:55 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://jira.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin.sy...
]
jaikiran pai commented on JBAS-8268:
------------------------------------
I guess the current flag just allows to switch off the validations, which isn't really
recommended. What might be useful is a flag which just WARNs a user about the validation
failure, so that he can then fix that issue or report it to the third party library
developers. That way, the deployment won't fail and the user will still be able to see
the issue in his xml config.
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://jira.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:57 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://jira.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin.sy...
]
Alexey Loubyansky commented on JBAS-8268:
-----------------------------------------
Note, that it's not exactly an XB error, it's a xerces validation error.
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://jira.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:34 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://jira.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin.sy...
]
Alexey Loubyansky commented on JBAS-8268:
-----------------------------------------
Ok, I've added JBXB-252. If that works for you I'll make a release and then
we'll need to turn it into a feature request for deployers to expose that option.
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://jira.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:10 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://jira.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin.sy...
]
Jason Porter commented on JBAS-8268:
------------------------------------
I had another one that I believe fits this issue (while it may not be the exact issue, the
proposed fix should make this work as well):
12:43:04,132 WARN [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] SchemaLocation:
schemaLocation value = 'http://java.sun.com/xml/ns/j2ee web jsptaglibrary_2_0.xsd'
must have even number of URI's. @
vfs:///Users/jporter/servers/jboss-6.0.0.20101110-CR1/server/default/deploy/tigrisfaces.war/WEB-INF/lib/standard.jar/META-INF/scriptfree.tld[7,19]
12:43:04,133 WARN [org.jboss.util.xml.JBossEntityResolver] Trying to resolve systemId as
a non-file URL:
vfs:///Users/jporter/servers/jboss-6.0.0.20101110-CR1/server/default/deploy/tigrisfaces.war/WEB-INF/lib/standard.jar/META-INF/web
12:43:04,134 WARN [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] schema_reference.4:
Failed to read schema document 'web', because 1) could not find the document; 2)
the document could not be read; 3) the root element of the document is not
<xsd:schema>. @
vfs:///Users/jporter/servers/jboss-6.0.0.20101110-CR1/server/default/deploy/tigrisfaces.war/WEB-INF/lib/standard.jar/META-INF/scriptfree.tld[7,19]
12:43:04,137 WARN [org.jboss.util.xml.JBossEntityResolver] Trying to resolve systemId as
a non-file URL: http://java.sun.com/xml/ns/j2ee
12:43:20,768 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse:
name=vfs:///Users/jporter/servers/jboss-6.0.0.20101110-CR1/server/default/deploy/tigrisfaces.war
state=PreParse mode=Manual requiredState=Parse:
org.jboss.deployers.spi.DeploymentException: Error creating managed object for
vfs:///Users/jporter/servers/jboss-6.0.0.20101110-CR1/server/default/deploy/tigrisfaces.war
at
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
[:2.2.0.Alpha8]
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:383)
[:2.2.0.Alpha8]
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343)
[:2.2.0.Alpha8]
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:315)
[:2.2.0.Alpha8]
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:255)
[:2.2.0.Alpha8]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
[:2.2.0.Alpha8]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832)
[:2.2.0.Alpha8]
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550)
[:2.2.0.Alpha8]
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491)
[:2.2.0.Alpha8]
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379)
[jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044)
[jboss-dependency.jar:2.2.0.Alpha10]
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083)
[jboss-dependency.jar:2.2.0.Alpha10]
at
org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322)
[jboss-dependency.jar:2.2.0.Alpha10]
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246)
[jboss-dependency.jar:2.2.0.Alpha10]
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139)
[jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939)
[jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654)
[jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983)
[:2.2.0.Alpha8]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076)
[:2.2.0.Alpha8]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679)
[:2.2.0.Alpha8]
at
org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106)
[:6.0.0.20101110-CR1]
at
org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:59)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:94)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150)
[:0.1.0.Alpha1]
at
org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135)
[:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146)
[:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90)
[:0.1.0.Alpha1]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_22]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
[:1.6.0_22]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_22]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
[:1.6.0_22]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
[:1.6.0_22]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_22]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_22]
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source:
vfs:///Users/jporter/servers/jboss-6.0.0.20101110-CR1/server/default/deploy/tigrisfaces.war/WEB-INF/lib/standard.jar/META-INF/scriptfree.tld@7,19
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:224)
[jbossxb.jar:2.0.2.Beta9]
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:178)
[jbossxb.jar:2.0.2.Beta9]
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:231)
[jbossxb.jar:2.0.2.Beta9]
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:206)
[jbossxb.jar:2.0.2.Beta9]
at
org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
[:2.2.0.Alpha8]
at org.jboss.deployment.TldParsingDeployer.parse(TldParsingDeployer.java:64)
[:6.0.0.20101110-CR1]
at org.jboss.deployment.TldParsingDeployer.parse(TldParsingDeployer.java:38)
[:6.0.0.20101110-CR1]
at
org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
[:2.2.0.Alpha8]
at
org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.handleMultipleFiles(AbstractVFSParsingDeployer.java:446)
[:2.2.0.Alpha8]
at
org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:319)
[:2.2.0.Alpha8]
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:376)
[:2.2.0.Alpha8]
... 41 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to parse schema for
nsURI=http://java.sun.com/xml/ns/j2ee, localName=taglib, schemaLocation=web
at
org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(AbstractMutableSchemaResolver.java:350)
[jbossxb.jar:2.0.2.Beta9]
at
org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:176)
[jbossxb.jar:2.0.2.Beta9]
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.startElement(SaxJBossXBParser.java:401)
[jbossxb.jar:2.0.2.Beta9]
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown
Source) [xercesImpl.jar:6.0.0.20101110-CR1]
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source) [xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)
[jbossxb.jar:2.0.2.Beta9]
... 51 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 31:3 The declaration for
the entity "HTML.Version" must end with '>'.
at
org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHandler.handleError(XsdBinderTerminatingErrorHandler.java:40)
[jbossxb.jar:2.0.2.Beta9]
at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.apache.xerces.impl.xs.XSLoaderImpl.load(Unknown Source)
[xercesImpl.jar:6.0.0.20101110-CR1]
at org.jboss.xb.binding.Util.loadSchema(Util.java:394) [jbossxb.jar:2.0.2.Beta9]
at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:178)
[jbossxb.jar:2.0.2.Beta9]
at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:149)
[jbossxb.jar:2.0.2.Beta9]
at
org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(AbstractMutableSchemaResolver.java:342)
[jbossxb.jar:2.0.2.Beta9]
... 66 more
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://jira.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:08 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://jira.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin.sy...
]
Alexey Loubyansky commented on JBAS-8268:
-----------------------------------------
No, it's not related to this issue. Looks like a schema resolution one.
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://jira.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:59 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://issues.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin....
]
Shelly McGowan commented on JBAS-8268:
--------------------------------------
I believe this will be resolved once the Deployers update for AS 6 Final is integrated.
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://issues.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:33 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://issues.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin....
]
Alexey Loubyansky commented on JBAS-8268:
-----------------------------------------
Yes and the new property will probably have to be added in the XML config after that.
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://issues.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.0.Final
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:35 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://issues.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin....
]
Shelly McGowan updated JBAS-8268:
---------------------------------
Fix Version/s: 6.0.1.M1
(was: 6.0.0.Final)
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://issues.jboss.org/browse/JBAS-8268
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML services
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.0.1.M1
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:26 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://issues.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8268:
------------------------------------
I think, this made to 6.0.0.Final, didn't it?
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://issues.jboss.org/browse/JBAS-8268
Project: Legacy JBoss Application Server 6
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML Services/Frameworks
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Alexey Loubyansky
Fix For: 6.1.0
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:32 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://issues.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin....
]
Ales Justin reassigned JBAS-8268:
---------------------------------
Assignee: Ales Justin (was: Alexey Loubyansky)
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://issues.jboss.org/browse/JBAS-8268
Project: Legacy JBoss Application Server 6
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML Services/Frameworks
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Ales Justin
Fix For: 6.1.0
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:32 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://issues.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin....
]
Ales Justin resolved JBAS-8268.
-------------------------------
Resolution: Done
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://issues.jboss.org/browse/JBAS-8268
Project: Legacy JBoss Application Server 6
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML Services/Frameworks
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Ales Justin
Fix For: 6.1.0
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:32 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files
[
https://issues.jboss.org/browse/JBAS-8268?page=com.atlassian.jira.plugin....
]
Ales Justin commented on JBAS-8268:
-----------------------------------
This property can be set on any deployer that extends JBossXBDeployer.
Should we add a relax flag for people using out of order content
inside elements of their XML files
---------------------------------------------------------------------------------------------------
Key: JBAS-8268
URL: https://issues.jboss.org/browse/JBAS-8268
Project: Legacy JBoss Application Server 6
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers, XML Services/Frameworks
Affects Versions: 6.0.0.M4
Reporter: Emmanuel Bernard
Assignee: Ales Justin
Fix For: 6.1.0
It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the
content in elements
https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_...
Would it make sense to have a flag to relax this rule? I am thinking of people with
existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of
use and less pain in support down the road).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4813
days inactive
5182
days old
15 comments
6 participants
participants (6)
-
Ales Justin (JIRA) -
Alexey Loubyansky (JIRA)
-
Emmanuel Bernard (JIRA)
-
jaikiran pai (JIRA)
-
Jason Porter (JIRA)
-
Shelly McGowan (JIRA)