[ https://issues.apache.org/jira/browse/ARIES-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved ARIES-1293. -------------------------------- Resolution: Fixed Fix Version/s: blueprint-core-1.4.2 Assignee: Daniel Kulp > Help custom namespace handlers that would like bean references.. > ---------------------------------------------------------------- > > Key: ARIES-1293 > URL: https://issues.apache.org/jira/browse/ARIES-1293 > Project: Aries > Issue Type: Bug > Components: Blueprint > Reporter: Daniel Kulp > Assignee: Daniel Kulp > Fix For: blueprint-core-1.4.2 > > > In some cases, custom namespace handlers may have a schema element like: > {code:xml} > <xsd:element name="plugin"> > <xsd:complexType> > <xsd:sequence> > <xsd:any namespace="##other"/> > </xsd:complexType> > </xsd:element> > {code} > where they intend to allow the user to define some sort of bean or other > object to be defined by the user. This works well in Spring/Spring-DM as > you can define an object there via the normal Spring "bean" element. > However, blueprint.xsd does NOT have a top level bean element that can be > referenced. Thus, with the above schema, you can only use objects that can > be created via custom namespaces. > The proposal would be to add two elements to the blueprint-ext namespace: > {code:xml} > <xsd:element name="bean" type="bp:Tbean"/> > <xsd:element name="reference" type="bp:Treference"/> > {code} > to fill the gap that Spring-DM provides that we cannot do with Blueprint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)