You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Jacopo Cappellato <ja...@hotwaxsystems.com> on 2016/09/16 03:55:01 UTC
Removing the ecomclone webapp from the ecommerce component
In the "ecommerce" component there are two web applications:
- ecommerce: the actual web application
- ecomclone: a clone of the above, that leverages the controller's
"include" feature to extend the main web application
For what I know the ecomclone webapp has been initially created to to test
and provide an example of the "include" feature; since then the feature has
been widely used and now essentially all the OFBiz applications make use of
it (by including the common-controller.xml) or extending/overriding other
applications.
My proposal is to remove ecomclone since it is no more needed.
Any objection or concerns?
Thanks,
Jacopo
Re: Removing the ecomclone webapp from the ecommerce component
Posted by Michael Brohl <mi...@ecomify.de>.
+1
Michael
> Am 16.09.2016 um 05:55 schrieb Jacopo Cappellato <ja...@hotwaxsystems.com>:
>
> In the "ecommerce" component there are two web applications:
> - ecommerce: the actual web application
> - ecomclone: a clone of the above, that leverages the controller's
> "include" feature to extend the main web application
> For what I know the ecomclone webapp has been initially created to to test
> and provide an example of the "include" feature; since then the feature has
> been widely used and now essentially all the OFBiz applications make use of
> it (by including the common-controller.xml) or extending/overriding other
> applications.
>
> My proposal is to remove ecomclone since it is no more needed.
>
> Any objection or concerns?
>
> Thanks,
>
> Jacopo
Re: Removing the ecomclone webapp from the ecommerce component
Posted by Pierre Smits <pi...@gmail.com>.
+1
Op vrijdag 16 september 2016 heeft Taher Alkhateeb <
slidingfilaments@gmail.com> het volgende geschreven:
> +1
>
> On Sep 16, 2016 7:52 AM, "Jacques Le Roux" <jacques.le.roux@les7arts.com
> <javascript:;>>
> wrote:
>
> > Le 16/09/2016 à 05:55, Jacopo Cappellato a écrit :
> >
> >> In the "ecommerce" component there are two web applications:
> >> - ecommerce: the actual web application
> >> - ecomclone: a clone of the above, that leverages the controller's
> >> "include" feature to extend the main web application
> >> For what I know the ecomclone webapp has been initially created to to
> test
> >> and provide an example of the "include" feature; since then the feature
> >> has
> >> been widely used and now essentially all the OFBiz applications make use
> >> of
> >> it (by including the common-controller.xml) or extending/overriding
> other
> >> applications.
> >>
> >> My proposal is to remove ecomclone since it is no more needed.
> >>
> >> Any objection or concerns?
> >>
> >> Thanks,
> >>
> >> Jacopo
> >>
> >> Actually there are 3 web applications with also ecomseo which uses the
> > include feature to leverage the ecommerce webapp by adding SEO friendly
> > URLs and other SEO aspects.
> > So I see no reasons to keep ecomclone since ecomseo demonstrates how to
> > use include, without any other request maps, like does ecomclone.
> > +1
> >
> > Jacques
> >
> >
>
--
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
Re: Removing the ecomclone webapp from the ecommerce component
Posted by Taher Alkhateeb <sl...@gmail.com>.
+1
On Sep 16, 2016 7:52 AM, "Jacques Le Roux" <ja...@les7arts.com>
wrote:
> Le 16/09/2016 à 05:55, Jacopo Cappellato a écrit :
>
>> In the "ecommerce" component there are two web applications:
>> - ecommerce: the actual web application
>> - ecomclone: a clone of the above, that leverages the controller's
>> "include" feature to extend the main web application
>> For what I know the ecomclone webapp has been initially created to to test
>> and provide an example of the "include" feature; since then the feature
>> has
>> been widely used and now essentially all the OFBiz applications make use
>> of
>> it (by including the common-controller.xml) or extending/overriding other
>> applications.
>>
>> My proposal is to remove ecomclone since it is no more needed.
>>
>> Any objection or concerns?
>>
>> Thanks,
>>
>> Jacopo
>>
>> Actually there are 3 web applications with also ecomseo which uses the
> include feature to leverage the ecommerce webapp by adding SEO friendly
> URLs and other SEO aspects.
> So I see no reasons to keep ecomclone since ecomseo demonstrates how to
> use include, without any other request maps, like does ecomclone.
> +1
>
> Jacques
>
>
Re: Removing the ecomclone webapp from the ecommerce component
Posted by Jacques Le Roux <ja...@les7arts.com>.
Le 16/09/2016 � 05:55, Jacopo Cappellato a �crit :
> In the "ecommerce" component there are two web applications:
> - ecommerce: the actual web application
> - ecomclone: a clone of the above, that leverages the controller's
> "include" feature to extend the main web application
> For what I know the ecomclone webapp has been initially created to to test
> and provide an example of the "include" feature; since then the feature has
> been widely used and now essentially all the OFBiz applications make use of
> it (by including the common-controller.xml) or extending/overriding other
> applications.
>
> My proposal is to remove ecomclone since it is no more needed.
>
> Any objection or concerns?
>
> Thanks,
>
> Jacopo
>
Actually there are 3 web applications with also ecomseo which uses the include feature to leverage the ecommerce webapp by adding SEO friendly URLs
and other SEO aspects.
So I see no reasons to keep ecomclone since ecomseo demonstrates how to use include, without any other request maps, like does ecomclone.
+1
Jacques