Re: [smartweb-devel] Introducing a Web Entity Search Component

[Gaetano P. <gpe...@sm...>]

Truly I haven't yet got the time to think about how to implement but only to
what to implement.
Otherwise I think 2 approches are possibile:
1. Standard component to customize (by configuration: xml / properties)
2. Standard component that supports standard features: we could introduce a
tag library for doing it receiving the entity (the mapped class or a
property we can resolve with the mapped class at configuration time) the
criteria to filter. Mapped classes that are "searchable" could implement a
Searchable interface.
The previous sentence are just ideas at this time, but suggestion are
appreciated.



Roberto Lo Giacco wrote:
> 
> I like the idea, but I've few questions for you:
> 
> - do you intend a component that doesn't need to be customized on a per
> entity basis?
> - in case the previous answer is yes, how do you intend to choose fields
> that should be considered searchable?
> 
> 
> Gaetano Perrone wrote:
>> 
>> I'm thinking about introducing a standard web entity search  component.
>> Think about a form mask with customer field to valorize with the customer
>> id. Actually we do this opening a popup and managing manually all the
>> interaction between the opener and the opened window.
>> In my opinion a standard generalized ajax complient component ( :-) )
>> could
>> resolve this common web developing problem.
>> Waiting for opinions...
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Introducing-a-Web-Entity-Search-Component-tp14209483s17546p14336619.html
Sent from the SmartWeb Developers mailing list archive at Nabble.com.