You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Dinesh Premalal (JIRA)" <ji...@apache.org> on 2007/05/06 13:28:15 UTC
[jira] Commented: (AXIS2C-601) Rampart Sample is Unable to pickup
outgoing policy file
[ https://issues.apache.org/jira/browse/AXIS2C-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493920 ]
Dinesh Premalal commented on AXIS2C-601:
----------------------------------------
I think these values came from client_repo/axis2.xml , because rampart_engine.c seems get that value from a parameter. Moreover sec_echo/service.xml sec_echo/outgoing_secpolicy.xml and sec_echo/incoming_secpolicy.xml , client_repo/outgoing_secpolicy.xml and client_repo/incoming_secpolicy.xml files seems to hold some hard coded paths. I think we need to figure out better way of giving those files.
I think its better if we can calculate those paths with respect to $AXIS2C_HOME environmental variable. Or else we can ask from user to fill out those value before he run samples. You might have a better solution. Please correct me if I'm mistaken.
> 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 ???
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org