ppkarwasz commented on issue #1955: URL: https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1825627975
Our plugins can be approximately modeled as [JavaBeans](https://en.wikipedia.org/wiki/JavaBeans), i.e. as Java classes with a set of documented properties, so a descriptor of a Log4j plugin must allow: - to describe a class and its hierarchy (both superclass and interfaces), - to describe its properties, which can be primitive Java values, classes or interfaces: our current configuration visitor binds primitive values and `String`s by name and other kinds of properties by type. The second requirement limits the list of available read-to-use component descriptors: Plexus component descriptors do not allow properties of any type. An XSD schema might also not be enough to precisely document our components: there is no standard way to convey inheritance in an XSD. We should probably leave XSD as a product of our documentation process. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
