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 "Nate Johnson (JIRA)" <ji...@apache.org> on 2007/04/13 19:15:15 UTC
[jira] Created: (PLUTO-356) Pluto Driver not using injected Portal
URL Parser
Pluto Driver not using injected Portal URL Parser
-------------------------------------------------
Key: PLUTO-356
URL: https://issues.apache.org/jira/browse/PLUTO-356
Project: Pluto
Issue Type: Bug
Components: portal driver
Affects Versions: 1.1.2
Reporter: Nate Johnson
Priority: Critical
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-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger updated PLUTO-356:
---------------------------------
Attachment: PLUTO-356.patch
Nate, can you try applying this patch and see if it works for you? Let me know if you have trouble applying it.
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2
> Reporter: Nate Johnson
> Assigned To: Elliot Metsger
> Priority: Critical
> Attachments: PLUTO-356.patch
>
>
> 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-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger updated PLUTO-356:
---------------------------------
Fix Version/s: (was: 1.1.4)
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2, 1.1.4
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 2.0.0, 1.1.5
>
> Attachments: PLUTO-356.patch
>
>
> 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] Resolved: (PLUTO-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger resolved PLUTO-356.
----------------------------------
Resolution: Fixed
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2, 1.1.4
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 1.1.5
>
> Attachments: PLUTO-356.patch
>
>
> 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-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger closed PLUTO-356.
--------------------------------
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 1.2.0, 1.1.4
>
> Attachments: PLUTO-356.patch
>
>
> 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-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger updated PLUTO-356:
---------------------------------
Fix Version/s: 1.2.0
Applied to trunk r554485.
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 1.2.0, 1.1.4
>
> Attachments: PLUTO-356.patch
>
>
> 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] Commented: (PLUTO-356) Pluto Driver not using injected
Portal URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574171#action_12574171 ]
Elliot Metsger commented on PLUTO-356:
--------------------------------------
PLUTO-469 is this issue opened against 2.0.0.
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2, 1.1.4
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 1.1.5
>
> Attachments: PLUTO-356.patch
>
>
> 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] Commented: (PLUTO-356) Pluto Driver not using injected
Portal URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556307#action_12556307 ]
Elliot Metsger commented on PLUTO-356:
--------------------------------------
Fix committed to 1.1.x branch 609238.
The 286 merge branch is out of date and this patch can't be easily merged/applied to it.
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2, 1.1.4
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 2.0.0, 1.1.5
>
> Attachments: PLUTO-356.patch
>
>
> 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] Assigned: (PLUTO-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger reassigned PLUTO-356:
------------------------------------
Assignee: Elliot Metsger
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2
> Reporter: Nate Johnson
> Assigned To: Elliot Metsger
> Priority: Critical
>
> 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-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger updated PLUTO-356:
---------------------------------
Fix Version/s: (was: 2.0.0)
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2, 1.1.4
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 1.1.5
>
> Attachments: PLUTO-356.patch
>
>
> 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] Resolved: (PLUTO-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger resolved PLUTO-356.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.1.4
PortalURLParser is now provided as an argument to the RelativePortalURLImpl constructor. Fix committed to the pluto-1.1.x branch. Nate if you could confirm that this fixes things for you, it would be appreciated. Thanks!
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2
> Reporter: Nate Johnson
> Assigned To: Elliot Metsger
> Priority: Critical
> Fix For: 1.1.4
>
> Attachments: PLUTO-356.patch
>
>
> 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] Commented: (PLUTO-356) Pluto Driver not using injected
Portal URL Parser
Posted by "Nate Johnson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508337 ]
Nate Johnson commented on PLUTO-356:
------------------------------------
I haven't been able to put this into our development code yet, but after talking to Dave at JA-SIG, and finding the correct branch in your version control, I believe this is going to work out just great. Thanks for getting this fix in!
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 1.1.4
>
> Attachments: PLUTO-356.patch
>
>
> 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] Reopened: (PLUTO-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger reopened PLUTO-356:
----------------------------------
PLUTO-361 reverted part of this patch. Need to add a unit test for PLUTO-356.
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 1.2.0, 1.1.4
>
> Attachments: PLUTO-356.patch
>
>
> 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] Commented: (PLUTO-356) Pluto Driver not using injected
Portal URL Parser
Posted by "Nate Johnson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491347 ]
Nate Johnson commented on PLUTO-356:
------------------------------------
I will try to test this as soon as I can. We are currently using the 1.1.2 binaries. Will this patch work or would I need to upgrade to head?
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2
> Reporter: Nate Johnson
> Assigned To: Elliot Metsger
> Priority: Critical
> Attachments: PLUTO-356.patch
>
>
> 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-356) Pluto Driver not using injected Portal
URL Parser
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger updated PLUTO-356:
---------------------------------
Fix Version/s: (was: 1.2.0)
1.1.5
2.0.0
Affects Version/s: 1.1.4
Updating fix ver to 1.1.5/2.0.0
> Pluto Driver not using injected Portal URL Parser
> -------------------------------------------------
>
> Key: PLUTO-356
> URL: https://issues.apache.org/jira/browse/PLUTO-356
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 1.1.2, 1.1.4
> Reporter: Nate Johnson
> Assignee: Elliot Metsger
> Priority: Critical
> Fix For: 2.0.0, 1.1.5
>
> Attachments: PLUTO-356.patch
>
>
> 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.