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

Sergey Beryozkin updated ARIES-1323:
------------------------------------
    Description: 
Option 1. Use a 'blueprintNamespaceHandlers' context parameter:
{code:xml}
<web-app>
    <context-param>
        <param-name>blueprintLocation</param-name>
        <param-value>WEB-INF/beans.xml</param-value>
    </context-param>
    <context-param>
        <param-name>blueprintNamespaceHandlers</param-name>
        <param-value>
              a.b.C,
              d.e.F
        </param-value>
    </context-param>
    <listener>
        <listener-class>
            org.apache.aries.blueprint.web.BlueprintContextListener
        </listener-class>
    </listener>
    <!-- the rest of web-app -->
</web-app>
{code}

Option 2. Check META-INF/blueprint.handlers class resources. The handler 
resource only lists one or more NamespaceHandler classes, example:
{noformat}
a.b.C
d.e.F
{noformat}

The web.xml will look much simpler:
{code:xml}
<web-app>
    <context-param>
        <param-name>blueprintLocation</param-name>
        <param-value>WEB-INF/beans.xml</param-value>
    </context-param>
    <listener>
        <listener-class>
            org.apache.aries.blueprint.web.BlueprintContextListener
        </listener-class>
    </listener>
    <!-- the rest of web-app -->
</web-app>
{code}

  was:
{code:xml}
<web-app>
    <context-param>
        <param-name>blueprintLocation</param-name>
        <param-value>WEB-INF/beans.xml</param-value>
    </context-param>
    <context-param>
        <param-name>blueprintNamespaceHandlers</param-name>
        <param-value>
              a.b.C,
              d.e.F
        </param-value>
    </context-param>
    <listener>
        <listener-class>
            org.apache.aries.blueprint.web.BlueprintContextListener
        </listener-class>
    </listener>
    <!-- the rest of web-app -->
</web-app>
{code}

        Summary: Update blueprint-web ServletContextListener to optionally 
register NamespaceHandlers  (was: Update blueprint-web ServletContextListener 
to register NamespaceHandlers if a blueprintNamespaceHandlers property is set)

> Update blueprint-web ServletContextListener to optionally register 
> NamespaceHandlers
> ------------------------------------------------------------------------------------
>
>                 Key: ARIES-1323
>                 URL: https://issues.apache.org/jira/browse/ARIES-1323
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint, Web
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>             Fix For: blueprint-web-1.1.1
>
>         Attachments: aries1323.txt
>
>
> Option 1. Use a 'blueprintNamespaceHandlers' context parameter:
> {code:xml}
> <web-app>
>     <context-param>
>         <param-name>blueprintLocation</param-name>
>         <param-value>WEB-INF/beans.xml</param-value>
>     </context-param>
>     <context-param>
>         <param-name>blueprintNamespaceHandlers</param-name>
>         <param-value>
>               a.b.C,
>               d.e.F
>         </param-value>
>     </context-param>
>     <listener>
>         <listener-class>
>             org.apache.aries.blueprint.web.BlueprintContextListener
>         </listener-class>
>     </listener>
>     <!-- the rest of web-app -->
> </web-app>
> {code}
> Option 2. Check META-INF/blueprint.handlers class resources. The handler 
> resource only lists one or more NamespaceHandler classes, example:
> {noformat}
> a.b.C
> d.e.F
> {noformat}
> The web.xml will look much simpler:
> {code:xml}
> <web-app>
>     <context-param>
>         <param-name>blueprintLocation</param-name>
>         <param-value>WEB-INF/beans.xml</param-value>
>     </context-param>
>     <listener>
>         <listener-class>
>             org.apache.aries.blueprint.web.BlueprintContextListener
>         </listener-class>
>     </listener>
>     <!-- the rest of web-app -->
> </web-app>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to