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 "Elliot Metsger (JIRA)" <ji...@apache.org> on 2008/03/02 02:06:51 UTC

[jira] Created: (PLUTO-469) Pluto Driver not using injected Portal URL Parser

Pluto Driver not using injected Portal URL Parser
-------------------------------------------------

                 Key: PLUTO-469
                 URL: https://issues.apache.org/jira/browse/PLUTO-469
             Project: Pluto
          Issue Type: Bug
          Components: portal driver
    Affects Versions: 1.1.2, 1.1.4
            Reporter: Elliot Metsger
            Assignee: Elliot Metsger
            Priority: Critical
             Fix For: 2.0.0, 1.1.5


Hi all,

We are in the process of upgrading to pluto 1.1.2 and have run into a small problem.  We have taken advantage of the new IoC to inject the required and optional services into our container services (ContainerServicesImpl).  It appears that the PortalURLImpl and RelativePortalURLImpl classes in the driver are not using the injected override service for URL creation (PortalURLParser).  The code below is showing the singleton access which always comes from org.apache.pluto.driver.url.impl rather than the container services.

// The toString() method for both classes listed below

org.apache.pluto.driver.url.impl.PortalURLImpl
  and
org.apache.pluto.driver.url.impl.RelativePortalURLImpl

public String toString() {
    return PortalURLParserImpl.getParser().toString(this);
}


Am I just confused as to how this should work, or was this singleton just missed?

Best,
Nate
-- 
Nathaniel A. Johnson                           Voice: 812.855.9905
Principal Systems Analyst                        Fax: 812.856.9046
Systems Integration Team, Indiana University 

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


[jira] Updated: (PLUTO-469) Pluto Driver not using injected Portal URL Parser

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

Elliot Metsger updated PLUTO-469:
---------------------------------

    Fix Version/s:     (was: 1.1.5)

> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
>                 Key: PLUTO-469
>                 URL: https://issues.apache.org/jira/browse/PLUTO-469
>             Project: Pluto
>          Issue Type: Bug
>          Components: portal driver
>    Affects Versions: 1.1.2, 1.1.4
>            Reporter: Elliot Metsger
>            Assignee: Elliot Metsger
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> Hi all,
> We are in the process of upgrading to pluto 1.1.2 and have run into a small problem.  We have taken advantage of the new IoC to inject the required and optional services into our container services (ContainerServicesImpl).  It appears that the PortalURLImpl and RelativePortalURLImpl classes in the driver are not using the injected override service for URL creation (PortalURLParser).  The code below is showing the singleton access which always comes from org.apache.pluto.driver.url.impl rather than the container services.
> // The toString() method for both classes listed below
> org.apache.pluto.driver.url.impl.PortalURLImpl
>   and
> org.apache.pluto.driver.url.impl.RelativePortalURLImpl
> public String toString() {
>     return PortalURLParserImpl.getParser().toString(this);
> }
> Am I just confused as to how this should work, or was this singleton just missed?
> Best,
> Nate
> -- 
> Nathaniel A. Johnson                           Voice: 812.855.9905
> Principal Systems Analyst                        Fax: 812.856.9046
> Systems Integration Team, Indiana University 

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


[jira] Closed: (PLUTO-469) Pluto Driver not using injected Portal URL Parser

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

Eric Dalquist closed PLUTO-469.
-------------------------------

    Resolution: Duplicate

PLUTO-356

> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
>                 Key: PLUTO-469
>                 URL: https://issues.apache.org/jira/browse/PLUTO-469
>             Project: Pluto
>          Issue Type: Bug
>          Components: portal driver
>    Affects Versions: 1.1.2, 1.1.4
>            Reporter: Elliot Metsger
>            Assignee: Elliot Metsger
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> Hi all,
> We are in the process of upgrading to pluto 1.1.2 and have run into a small problem.  We have taken advantage of the new IoC to inject the required and optional services into our container services (ContainerServicesImpl).  It appears that the PortalURLImpl and RelativePortalURLImpl classes in the driver are not using the injected override service for URL creation (PortalURLParser).  The code below is showing the singleton access which always comes from org.apache.pluto.driver.url.impl rather than the container services.
> // The toString() method for both classes listed below
> org.apache.pluto.driver.url.impl.PortalURLImpl
>   and
> org.apache.pluto.driver.url.impl.RelativePortalURLImpl
> public String toString() {
>     return PortalURLParserImpl.getParser().toString(this);
> }
> Am I just confused as to how this should work, or was this singleton just missed?
> Best,
> Nate
> -- 
> Nathaniel A. Johnson                           Voice: 812.855.9905
> Principal Systems Analyst                        Fax: 812.856.9046
> Systems Integration Team, Indiana University 

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