You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "David DeWolf (JIRA)" <ji...@apache.org> on 2007/03/10 14:21:09 UTC

[jira] Created: (PLUTO-336) Provide alternate ways for deriving applicationId

Provide alternate ways for deriving applicationId
-------------------------------------------------

                 Key: PLUTO-336
                 URL: https://issues.apache.org/jira/browse/PLUTO-336
             Project: Pluto
          Issue Type: Bug
          Components: portlet container
    Affects Versions: 1.1.1
            Reporter: David DeWolf
         Assigned To: David DeWolf
             Fix For: 1.1.2


Current approach does not work in weblogic and (i suspect) other containers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (PLUTO-336) Provide alternate ways for deriving applicationId

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David DeWolf resolved PLUTO-336.
--------------------------------

    Resolution: Fixed

applied.

> Provide alternate ways for deriving applicationId
> -------------------------------------------------
>
>                 Key: PLUTO-336
>                 URL: https://issues.apache.org/jira/browse/PLUTO-336
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>    Affects Versions: 1.1.1
>            Reporter: David DeWolf
>         Assigned To: David DeWolf
>             Fix For: 1.1.2
>
>
> Current approach does not work in weblogic and (i suspect) other containers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (PLUTO-336) Provide alternate ways for deriving applicationId

Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliot Metsger closed PLUTO-336.
--------------------------------


> Provide alternate ways for deriving applicationId
> -------------------------------------------------
>
>                 Key: PLUTO-336
>                 URL: https://issues.apache.org/jira/browse/PLUTO-336
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>    Affects Versions: 1.1.1
>            Reporter: David DeWolf
>         Assigned To: David DeWolf
>             Fix For: 1.1.2
>
>
> Current approach does not work in weblogic and (i suspect) other containers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (PLUTO-336) Provide alternate ways for deriving applicationId

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479962 ] 

David DeWolf commented on PLUTO-336:
------------------------------------

I have created and provided default implementations of the ApplicationIdResolver interface.  New impls can be registered with pluto by providing a pluto.properties file in /META-INF.  This impl will be added to the list of valid impls and be given an opportunity to participate in resolution. Unfortunately, it CAN NOT be provided as container configuration since it is required even before the container is started up.

> Provide alternate ways for deriving applicationId
> -------------------------------------------------
>
>                 Key: PLUTO-336
>                 URL: https://issues.apache.org/jira/browse/PLUTO-336
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>    Affects Versions: 1.1.1
>            Reporter: David DeWolf
>         Assigned To: David DeWolf
>             Fix For: 1.1.2
>
>
> Current approach does not work in weblogic and (i suspect) other containers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.