Bug 5597 – LocalInvocationHelper: wrong way of getting container configuration values

Bug 5597 - LocalInvocationHelper: wrong way of getting container configuration values

Summary:

LocalInvocationHelper: wrong way of getting container configuration values

Status:	CLOSED FIXED

Product:	GRAM
Component:	general
Version:	4.0.5
Platform:	Macintosh All

Importance:	P3 normal
Target Milestone:	4.0.6
Assigned To:	Martin Feller

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-05 15:17 by Martin Feller
Modified:	2007-10-26 21:39 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Martin Feller 2007-10-05 15:17:49

The two properties org.apache.axis.Constants.MC_HOME_DIR and
org.apache.axis.Constants.MC_CONFIGPATH are added to the
MessageContext in a local invocation from GRAM4 to RFT.
Otherwise service initialization fails because wsdl files
are not found.
So far however we used a wrong method to get these properties
that caused problems when GRAM4 runs in Tomcat and local invocations
from GRAM4 to RFT are enabled: a wsdl file cannot be found although
it's in place.
The right way to get the values for these properties from Core is
using ContainerConfig. See section 5.2.2.3 on
http://www.globus.org/toolkit/docs/4.0/common/javawscore/developer-index.html

With this local invocations from Gram4 to RFT also work in Tomcat.

------- Comment #1 From Martin Feller 2007-10-05 15:26:10 -------

fixed in 4.0 branch