The problem here is in security policy files we have assumed Axis2/C is installed in , /home/AXIS2_USER/axis2/c/deploy.
So when you are building the samples a script will replace the AXIS2_USER with the username(eg:- AXIS2_USER => dinesh). If we don't do it then user have to manually edit four policy files. By the way this discussion should be moved to rampart-dev list. Thanks -Manjula. On Sun, 2007-05-06 at 02:58 -0700, Dinesh Premalal (JIRA) wrote: > Rampart Sample is Unable to pickup outgoing policy file > ------------------------------------------------------- > > Key: AXIS2C-601 > URL: https://issues.apache.org/jira/browse/AXIS2C-601 > Project: Axis2-C > Issue Type: Bug > Components: rampart > Affects Versions: 0.96, Current (Nightly) > Reporter: Dinesh Premalal > > > After building rampart , I tried to run samples but they failed. Although my > environmental variables of > > AXIS2C_HOME=/home/dinesh/axis2c/deploy > CLIENT_REPO=$AXIS2C_HOME/client_repo > > log complains saying > > [rampart][rampart_Engine] Trying to build rampart context from file > /home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml > [Sun May 6 15:28:53 2007] [info] [rampart][rampart_Engine] Cannot get policy > [Sun May 6 15:28:53 2007] [info] [rampart][mod_rampart] mod_rampart shutdown > > I have no idea where this path > "home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml" came from ??? > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
