The best matching functionality would be a ProductFeature with the
different types as you described. These should be associated to
products as standard features.
Not showing up in ecommerce just means it's not in the productdetail
(or other product display) template, and you can make changes there as
desired.
Using product features this way will allow for searching by feature
using the advanced search page in the ecommerce templates.
Note that there is a good deal of more advanced functionality related
to this, like associating features with a category so that when you
search within the category you only see the features to search by that
are relevant for that category.
As far as the data structures go, the ProductFeature and
ProductFeatureAppl entities (and ProductFeatureAndAppl view-entity if
I remember right) are the ones you want to look at, and you can find
lots of stuff by searching for those around OFBiz.
-David
On May 18, 2008, at 1:54 AM, Bruno Busco wrote:
Hi,
I am considering to use ofbiz to implement an ecommerce site that
sells
exclusively tyres.
Every tyre product has a specific code and some parameters as
diameter,
width, height, load code and speed code.
In the site there should be the possibility to filter and list all
product
specifing one or more of the above parameters.
I would like to know what is the preferred way to implement this.
Every tyre type must have a specific productId toghether with its
parameters
so I do not think this is going to be a configurable product, am I
right?
At the moment I have extended the Product entity with those additional
fields, but I am not sure to have done the best think.
Any help will be greatly appreciated.
-Bruno
