[JBoss JIRA] Created: (JBXB-201) Cannot parse schema/jbxb_1_0.xsd
by Thomas Diesler (JIRA)
Cannot parse schema/jbxb_1_0.xsd
--------------------------------
Key: JBXB-201
URL: https://jira.jboss.org/jira/browse/JBXB-201
Project: JBoss XML Binding (JBossXB)
Issue Type: Bug
Reporter: Thomas Diesler
This code
String jbxbSchema = "schema/jbxb_1_0.xsd";
URL jbxbXSD = context.getBundle().getResource(jbxbSchema);
if (jbxbXSD == null)
throw new IllegalStateException("Cannot find: " + jbxbSchema);
XSModel xsModel = Util.loadSchema(jbxbXSD.toExternalForm(), (SchemaBindingResolver)null);
if (xsModel == null)
throw new IllegalStateException("Cannot load schema: " + jbxbSchema);
fails with
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 94:47 src-element.3: Element 'class' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element.
at org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHandler.handleError(XsdBinderTerminatingErrorHandler.java:40)
at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source)
at org.apache.xerces.impl.xs.XSLoaderImpl.loadURI(Unknown Source)
at org.jboss.xb.binding.Util.loadSchema(Util.java:367)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBXB-202) Incosistent initialization of XSImplementation
by Thomas Diesler (JIRA)
Incosistent initialization of XSImplementation
----------------------------------------------
Key: JBXB-202
URL: https://jira.jboss.org/jira/browse/JBXB-202
Project: JBoss XML Binding (JBossXB)
Issue Type: Bug
Reporter: Thomas Diesler
Fix For: JBossXB-2.0.1.GA
In Util there is
private static XSImplementation xsImpl;
which gets initialized lazily in
public static XSModel loadSchema(String xsdURL, SchemaBindingResolver schemaResolver)
{
if(xsImpl == null)
{
xsImpl = getXSImplementation();
}
All other loadSchema method do not reuse the static property
Also,
private static XSImplementation getXSImplementation()
relies on the thread context classloader, which is not available in an OSGi environment.
Could you please provide an JBossXB initialization entry point that is public and does not make an assumption on the availability of the TCCL
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBDEPLOY-225) Create ErrorHandler to DeploymentControllerContext
by Thomas Diesler (JIRA)
Create ErrorHandler to DeploymentControllerContext
---------------------------------------------------
Key: JBDEPLOY-225
URL: https://jira.jboss.org/jira/browse/JBDEPLOY-225
Project: JBoss Deployers
Issue Type: Feature Request
Reporter: Thomas Diesler
The MC Framework incorrectly uninstalls the bundle if there is a failure in bundle.start()
The controller context reached its required stage DESCRIBED after bundle install. A subsequent call to bundle.start() is supposed to transition to stages CLASSLOADER and then INSTALLED, which corresponds to the Bundle states RESOLVED and ACTIVE respectively.
If the transition to INSTALLED fails, the controller context gets undeployed, which causes the bundle to transition to UNINSTALLED.
The desired behaviour is:
* on fail to resolve: remain in state INSTALLED
* on fail to start: remain in state RESOLVED
The proposed solution is to add an ErrorHandler to the DeploymentControllerContext
if it is an OSGi deployment
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months