You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bruce Snyder (JIRA)" <ji...@apache.org> on 2009/11/20 20:21:52 UTC

[jira] Updated: (AMQ-1312) SpringIDE extension plugin for configuration namespace

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

Bruce Snyder updated AMQ-1312:
------------------------------

    Fix Version/s:     (was: AGING_TO_DIE)
       Issue Type: Wish  (was: New Feature)

> SpringIDE extension plugin for configuration namespace
> ------------------------------------------------------
>
>                 Key: AMQ-1312
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1312
>             Project: ActiveMQ
>          Issue Type: Wish
>    Affects Versions: 4.1.1
>            Reporter: TJ 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.
-
You can reply to this email to add a comment to the issue online.