[ 
https://issues.apache.org/jira/browse/ARTEMIS-3139?focusedWorklogId=794912&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-794912
 ]

ASF GitHub Bot logged work on ARTEMIS-3139:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jul/22 14:11
            Start Date: 25/Jul/22 14:11
    Worklog Time Spent: 10m 
      Work Description: ryan-highley commented on PR #4122:
URL: 
https://github.com/apache/activemq-artemis/pull/4122#issuecomment-1194102239

   @michaelandrepearce   Finally able to circle back to this. (Stupid day 
job....)
   
   Could you attach your config files so I can attempt to recreate the issue?
   




Issue Time Tracking
-------------------

    Worklog Id:     (was: 794912)
    Time Spent: 7h 20m  (was: 7h 10m)

> Anonymous types in artemis-configuration.xsd
> --------------------------------------------
>
>                 Key: ARTEMIS-3139
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3139
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Tuve Nordius
>            Priority: Major
>          Time Spent: 7h 20m
>  Remaining Estimate: 0h
>
> The artemis-configuration.xsd has a lot of anonymous types which makes it 
> hard to create a modulirized configuration. If I want to have diverts in a 
> seperate file I can do that but I cant get any validation/ help for any 
> editor. 
> example:
> I can do in an included file diverts.xml something like 
> {code:java}
> <diverts xmlns="urn:activemq:core">{code}
> I would like to do like bellow, but I can't since divertsType does not exist 
> other as an inline anonymous type.
>  
> {code:java}
> <diverts xmlns="urn:activemq:core"
>          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>          xsi:schemaLocation="urn:activemq:core 
> /schema/artemis-configuration.xsd"
>          xsi:type="divertsType" >
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to