September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4697) Support general XML Entities in AS boot configuration

by Michael Epley (JIRA)

Michael Epley created AS7-4697: ---------------------------------- Summary: Support general XML Entities in AS boot configuration Key: AS7-4697 URL: https://issues.jboss.org/browse/AS7-4697 Project: Application Server 7 Issue Type: Feature Request Components: ConfigAdmin Affects Versions: 7.1.1.Final Environment: Fedora 16, plenty of memory, disk, etc; feature is not related to environment Reporter: Michael Epley Assignee: Thomas Diesler The parser for the AS7 boot configuration (tested with standalone.xml) does not permit the use of general XML entities, as it fails [1] on the parsing of the entity declaration [2]. This appears due to the use of a low level parser enforcing certain expectations in the XML file layout. Use of XML external entities is a method that allows the single boot configuration file to be broken into multiple, independent pieces so that they can be independently contributed (by different developers/teams), controlled (by different developers/teams), configuration managed, or use substituted (for different dev/test/stage/prod) configurations. This is a common business requirement, with larger applications, different developers or sub teams usually contribute or have ownership over different subsystems, or that each contribute some portion of a subsystem. For example, two developers may each use a different JDBC datasource, and a third deployment engineer may be responsible for controlling the main boot configuration to ensure application integrity. Use of XML entities would allow the deployment engineer to write portions of the boot configuration (eg. standalone.xml) such as: ... <subsystem xmlns="urn:jboss:domain:datasources:1.0"> <datasources> &developer1datasource; &developer2datasource; </datasources> </subsystem> ... where &developer1datasource &developer2datasource might be declared as <!ENTITY developer1datasource SYSTEM "alicesDatasource.xml" > <!ENTITY developer2datasource SYSTEM "bobsDatasource.xml" > and the file alicesDatasource.xml is owned/maintained by developer Alice, and the the file bobsDatasource.xml is owned/maintained by developer Bob. ____________________________________________________________________ [1] For example, on boot, the following is reported: 08:52:51,181 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.jboss.as.server.ServerService.boot(ServerService.java:268) [jboss-as-server-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[6,4] Message: found: DTD, expected START_ELEMENT or END_ELEMENT at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1246) [rt.jar:1.6.0_24] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:67) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] ... 3 more 08:52:51,185 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. [2] Tested with the following entity declaration in standalone.xml (and various other combinations): <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE server [ <!ENTITY datasources SYSTEM "datasources.xml" > <!ENTITY cacheDefinitions SYSTEM "caches.xml" > ] > <server xmlns="urn:jboss:domain:1.3"> <extensions> ... <subsystem xmlns="urn:jboss:domain:datasources:1.0"> &datasources; </subsystem> ... <subsystem xmlns="urn:jboss:domain:infinispan:1.3" default-cache-container="local"> &cacheDefinitions; </subsystem> ... </socket-binding-group> </server> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

6
7
0 / 0

[JBoss JIRA] (AS7-4626) Standard method of documenting whether expressions are supported in the jboss-as-config_x_x.xsd and in the subsystem xsds

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4626: ------------------------------------- Summary: Standard method of documenting whether expressions are supported in the jboss-as-config_x_x.xsd and in the subsystem xsds Key: AS7-4626 URL: https://issues.jboss.org/browse/AS7-4626 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Fix For: 7.2.0.Alpha1 Users should be able to read the xsd to tell if expressions are supported for a given attribute/element. Reading the management API metadata is too cumbersome and indirect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] (AS7-4627) Remove ServerEnvironment.getModulesDir()

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4627: ------------------------------------- Summary: Remove ServerEnvironment.getModulesDir() Key: AS7-4627 URL: https://issues.jboss.org/browse/AS7-4627 Project: Application Server 7 Issue Type: Task Components: Server Reporter: Brian Stansberry Fix For: 7.2.0.Alpha1 This method was deprecated in 7.1.0 and the OSGi subsystem is removing the only known use of it in 7.1.2. Remove the method in 7.2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] (AS7-4383) Mode to disable writing deployment outcome files to deployment scanner dir

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4383: ------------------------------------- Summary: Mode to disable writing deployment outcome files to deployment scanner dir Key: AS7-4383 URL: https://issues.jboss.org/browse/AS7-4383 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Investigate adding a config option that disables writing the .isdeploying, .deployed, .isundeploying, .undeployed files to the deployment scanner dir. Idea is to make it possible to have multiple scanners on different nodes sharing the deployment directory, without having the markers from one interfere with another. This may not be practical at all in reality; needs investigation. Marker files created by the user to control deployment should still be supported. The .failed and .pending files are a bit of a gray area that need investigation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
5
0 / 0

[JBoss JIRA] (AS7-5576) Slave HostControllers should provide initial ignored-resource data to the master HC

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5576: ------------------------------------- Summary: Slave HostControllers should provide initial ignored-resource data to the master HC Key: AS7-5576 URL: https://issues.jboss.org/browse/AS7-5576 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 When the master HC is transforming the domain-level configuration model in order to provide it to a registering slave host, it should not bother transforming resources that are going to be ignored once they arrive at the slave. To facilitate this, the slave should include ignored-resource data as part of the "host-info" ModelNode it passes to the master when it initiates registration. One thing this (partly) allows is registration failure on the master if it detects the presence of unignored resources that the a slave running any earlier version cannot understand. The master cannot *always* fail in this situation, since the slave may be configured to ignore the offending resource. Providing the ignored-resource data allows the master to make a more informed decision. Note: I say "(partly) allows" above because the master cannot "eagerly fail" if the registering slave is running a version that precedes the completion of this task. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] (AS7-4807) Add LDAP authorization for security realms.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4807: ------------------------------------- Summary: Add LDAP authorization for security realms. Key: AS7-4807 URL: https://issues.jboss.org/browse/AS7-4807 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1, Open To Community Add support for loading roles from LDAP in security realms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
2
0 / 0

[JBoss JIRA] (AS7-4792) Convert jgroups subsystem to ResourceDefinition

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4792: -------------------------------- Summary: Convert jgroups subsystem to ResourceDefinition Key: AS7-4792 URL: https://issues.jboss.org/browse/AS7-4792 Project: Application Server 7 Issue Type: Sub-task Components: Clustering Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Tomaz Cerar Assignee: Paul Ferraro Fix For: 7.2.0.Alpha1 Convert to jgroups subsystem to ResourceDefinition -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3614) Pluggable Belief System for the Truth Maintenance System

by Mark Proctor (JIRA)

Mark Proctor created JBRULES-3614: ------------------------------------- Summary: Pluggable Belief System for the Truth Maintenance System Key: JBRULES-3614 URL: https://issues.jboss.org/browse/JBRULES-3614 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.5.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] (AS7-5230) jboss-as maven plugin won't parse variables in filename configuration attribute

by Pete Muir (JIRA)

Pete Muir created AS7-5230: ------------------------------ Summary: jboss-as maven plugin won't parse variables in filename configuration attribute Key: AS7-5230 URL: https://issues.jboss.org/browse/AS7-5230 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Pete Muir Assignee: James Perkins If you try to use a variable here (e.g. ${project.artifactId}) then it doesn't get expanded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] (AS7-5229) jboss-as maven plugin tries to deploy an artifact ending in .ejb for ejb packaging type

by Pete Muir (JIRA)

Pete Muir created AS7-5229: ------------------------------ Summary: jboss-as maven plugin tries to deploy an artifact ending in .ejb for ejb packaging type Key: AS7-5229 URL: https://issues.jboss.org/browse/AS7-5229 Project: Application Server 7 Issue Type: Feature Request Reporter: Pete Muir Assignee: James Perkins Fix For: 7.1.1.Final If you create an artifact with ejb type packaging, the produced artifact still has .jar as the filename extension of the resource to deploy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2012