Removing the ecomclone webapp from the ecommerce component

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Removing the ecomclone webapp from the ecommerce component

Jacopo Cappellato-5
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
Reply | Threaded
Open this post in threaded view
|

Re: Removing the ecomclone webapp from the ecommerce component

Jacques Le Roux
Administrator
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

Reply | Threaded
Open this post in threaded view
|

Re: Removing the ecomclone webapp from the ecommerce component

taher
+1

On Sep 16, 2016 7:52 AM, "Jacques Le Roux" <[hidden email]>
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
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Removing the ecomclone webapp from the ecommerce component

Pierre Smits
+1

Op vrijdag 16 september 2016 heeft Taher Alkhateeb <
[hidden email]> het volgende geschreven:

> +1
>
> On Sep 16, 2016 7:52 AM, "Jacques Le Roux" <[hidden email]
> <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/
Reply | Threaded
Open this post in threaded view
|

Re: Removing the ecomclone webapp from the ecommerce component

Michael Brohl-3
In reply to this post by Jacopo Cappellato-5
+1

Michael

> Am 16.09.2016 um 05:55 schrieb Jacopo Cappellato <[hidden email]>:
>
> 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

smime.p7s (3K) Download Attachment