Thanks Gil, I'm asking why not what. It doesn't make any sense to me why you'd want to rename an existing component, it's difficult to do and I'm not sure of the reason to try.
Regards Scott On 17/06/2013, at 8:22 PM, gil portenseigne wrote: > Hi, > > I guess that Hans want to rename a duplicated component of order. Then with > this new way to write the component://, it won't necessary to make a global > replacement of component://content by component://neworder in the duplicated > component. > > Do the global replacement in the new component is dangerous ? > > My 0.02 > > Gil Portenseigne > > Le 17/06/2013 10:10, Scott Gray a écrit : >> Thanks Hans. >> >> I guess what I don't understand is why you would rename the OOTB >> component? It seems like you're creating a headache for yourself >> unnecessarily. >> >> Regards >> Scott >> >> On 17/06/2013, at 8:03 PM, Hans Bakker wrote: >> >>> Thanks Scott for you reply, >>> >>> perhaps not explained good, another try: >>> >>> Presently we can write: >>> component://order/widget/order/...... >>> >>> Would be nice if we could also write: >>> component:/widget/order/...... >>> >>> which should be translated into: >>> component://order/widget/order/...... >>> when the url was physically located within the order component. >>> >>> When we have this ability and then rename the order component to something >>> else in ofbiz-component.xml >>> Then this renamed component would still work and can operate in the same >>> system as the original order component. >>> >>> The reason we want this is, that we create sometimes modified components >>> for different customers which should work in the same SAAS multi tenant >>> environment. >>> >>> bit more clear now? >>> >>> Regards, Hans >>> >>> >>> On 06/17/2013 01:52 PM, Scott Gray wrote: >>>> What would the current component be once the screen/form (I assume you're >>>> talking about screens/forms) was included from a different component? >>>> Would it be local to the component it is defined in or local to the >>>> component it was referenced from? >>>> >>>> I can't really offer any alternative solutions because I don't really >>>> understand the problem at all. >>>> >>>> Regards >>>> Scott >>>> >>>> On 17/06/2013, at 6:15 PM, Hans Bakker wrote: >>>> >>>>> The problem: >>>>> Sometimes we would like to demo similar components to different customers >>>>> on the same multi tenant installation. >>>>> The same problem will come up if we want to install it in a SAAS >>>>> environment. >>>>> >>>>> Presently we can write: >>>>> component://order/widget/order/...... >>>>> >>>>> Would be nice if we could also write: >>>>> component:/widget/order/...... >>>>> and use the current component name as component name in this url ? >>>>> >>>>> Anybody want to comment on this? >>>>> >>>>> Regards, >>>>> Hans Bakker >>>>> AntWebsystems.com >>>>> >>>>> >>> > >
