Obi Kenobi

Greenhorn
+ Follow
since Nov 02, 2005
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Obi Kenobi

In my deployment set-up, I want to keep the application level
property files outside of the EAR file, so that if we ever need to
modify the contents of these files, we won't have to re-deploy the EAR
file.

There are two ways (that I know) to do this. One is hardcode the
location of the property file on the server, but that bring up the
issue of having J2EE components accessing resources on the server , not
to mention a bunch of other issues if we have a clustered setup. The
2nd option is using a URL provider. I'm trying to set it up as per the

WAS documentation but get a wierd error.

http://www-128.ibm.com/developerworks/websphere/library/techarticles/...

The error I get is ..

Context: mhubDevCell2/nodes/sun522mhub-devn2_1/servers/server1, name:
url/PhoenixProperties: First component in name PhoenixProperties not
found.

where "url/PhoenixProperties" is the JNDI name and "PhoenixProperties"
is the URL (resource) on the WAS instance.

Was wondering if anyone here has received this error and fixed it OR if
anyone here has a more graceful way to configure & deploy application
level property files
18 years ago
In my deployment set-up, I want to keep the application level

property files outside of the EAR file, so that if we ever need to

modify the contents of these files, we won't have to re-deploy the EAR

file.

There are two ways (that I know) to do this. One is hardcode the

location of the property file on the server, but that bring up the

issue of having J2EE components accessing resources on the server , not
to mention a bunch of other issues if we have a clustered setup. The

2nd option is using a URL provider. I'm trying to set it up as per the

WAS documentation but get a wierd error.

http://www-128.ibm.com/developerworks/websphere/library/techarticles/...

The error I get is ..

Context: mhubDevCell2/nodes/sun522mhub-devn2_1/servers/server1, name:
url/PhoenixProperties: First component in name PhoenixProperties not
found.

where "url/PhoenixProperties" is the JNDI name and "PhoenixProperties"

is the URL (resource) on the WAS instance.

Was wondering if anyone here has received this error and fixed it OR if
anyone here has a more graceful way to configure & deploy application
level property files
18 years ago