[PLUTO-356] Pluto Driver not using injected Portal URL Parser

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.1.2, 1.1.4
• Fix Version/s: 1.1.5
• Component/s: portal driver
• Assignee: Elliot Metsger
• Reporter: Nate Johnson
• Created: 13/Apr/07 17:14
• Updated: 02/Mar/08 01:11
• Resolved: 02/Mar/08 01:11

Description

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: [phone]
Systems Integration Team, Indiana University

Issue Links

• is cloned by: PLUTO-469 Pluto Driver not using injected Portal URL Parser