This is related to my comment given in the ticket #662 review:
"2. If I am configuring saAmfCtRelPathInstantiateCmd with relative patch
(/opt/amf_demo) and also configure saAmfCtSwBundle, then it is only taking
saAmfCtRelPathInstantiateCmd. This need to be documented."
---
** [tickets:#773] AMF: #662 backwards compatibility issues**
**Status:** fixed
**Created:** Fri Feb 07, 2014 03:05 PM UTC by Hans Feldt
**Last Updated:** Fri Feb 07, 2014 04:06 PM UTC
**Owner:** nobody
Some install campaign had a _relative_ path starting with "/" (yes weird) and
also a absolute prefix from the SaAmfNodeSwBundle. This triggered the logic
introduced in #662 to skip the path prefix thus producing an invalid CLC CLI
path.
This needs to work the same way as before, that is if a path prefix exist it
should be added to whatever the relative path is.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
