[jboss-osgi-issues] [JBoss JIRA] Resolved: (JBOSGI-355) Get Start Level Configuration with custom XML namespace to work with AS

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/browse/JBOSGI-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved JBOSGI-355.
-----------------------------------

    Fix Version/s:     (was:  JBossOSGi 1.0.x)
       Resolution: Won't Fix


Won't fix in AS6

> Get Start Level Configuration with custom XML namespace to work with AS
> -----------------------------------------------------------------------
>
>                 Key: JBOSGI-355
>                 URL: https://jira.jboss.org/browse/JBOSGI-355
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Productization
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>
> The following start level configuration doesn't work in AS:
>     <start-level xmlns="urn:jboss:startlevel:1.0" />
> This is because the schema is defined in another MC deployment file which must be processed before the one containing the XML that uses it can be processed.
> This relates to https://community.jboss.org/thread/153462
> There are a couple of ways in which this can be resolved:
> * The MC could possibly inform the parser in some way that doesn't depend on the parse ordering
> * For AS, the deployers/metadata-deployer-jboss-beans.xml could be updated to include the start level schema - this could happen in the JBOSGi installer...

-- 
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