Allow NamespaceHandlers to use ParserContext to figure out what is being parsed
-------------------------------------------------------------------------------
Key: ARIES-111
URL: https://issues.apache.org/jira/browse/ARIES-111
Project: Aries
Issue Type: Bug
Components: Blueprint
Affects Versions: 1.0
Reporter: David Jencks
Fix For: 1.0
Attachments: ARIES-111.diff
ParserContext.parseElement currently expects you to know what kind of metadata
you expect to get out of an element and, depending on the type, may or may not
require the element to be in the blueprint namespace. Sometimes he requiest is
mapped to a namespace handler, and sometimes it's assumed that you are giving
it a blueprint element (but it isn't checked).
It would be much more convenient for writing sophisticated NamespaceHandlers if
parseElement would work with Metadata.class as the type: this allows the parser
to check namespaces, map to the correct namespace handler if necessary, and
figure out what kind of metadata is needed for blueprint elements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
