activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-1312) SpringIDE extension plugin for configuration namespace
Date Wed, 29 Jun 2011 13:42:28 GMT

     [ https://issues.apache.org/jira/browse/AMQ-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-1312.
-----------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 5.6.0)

OBE

> SpringIDE extension plugin for configuration namespace
> ------------------------------------------------------
>
>                 Key: AMQ-1312
>                 URL: https://issues.apache.org/jira/browse/AMQ-1312
>             Project: ActiveMQ
>          Issue Type: Wish
>    Affects Versions: 4.1.1
>            Reporter: Thomas Brosnan
>
> This description is based on a response to a post on the Spring forums by cdupuis (see
http://forum.springframework.org/showthread.php?t=40946)
> Out of the box Spring IDE only knows about NamespaceHandlers that are part of the Spring
Portfolio. Therefore Spring IDE is not able to validate the Bean Reference to a bean that
would be generated by a NamespaceHandler at runtime, but not known in Spring IDE's runtime
environment. This also means that amq namespace elements don't appear in the Spring or Project
Explorer.
> Because Spring IDE lives in the OSGi environment of your Eclipse instance it can't take
any of your project's jar files and look for NamespaceHandlers.
> Spring IDE can "learn" about any namespace by adding suppport for custom namespaces,
see http://springide.org/blog/2007/04/05/adding-support-for-custom-namespaces/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message