![]() We're looking for an application that can be customized to look like the rest of the JavaEdge site. This approach is a little different from the search interface that most commercial web search engines use, such as Google. HouseSpider uses a Java applet to search the items and display the results. Some Java open source web search engines are Lucene, Egothor, and HouseSpider. But if this isn't the case, we will need to create an integration code between our application and the search engine.Īnother requirement is that the search engine should be open source, so we can modify its behavior. We would prefer the solution to be ready to go with our Struts framework. ![]() It's certainly possible to use a search engine that is written only in Perl, C, or Python with our JavaEdge application, but it would be much harder to integrate with Struts. If we used a product that isn't J2EE- compatible, we would have a tougher integration problem. We need a solution that fits in with our existing architecture. While displaying the results, a summary or description of each link should be given, so the users can figure out what they're likely to get when they select a particular result. A link to the search engine should be available from every page. Hence, we have to find a search engine that can reliably rank and score results.Īnother consideration for the user interface is that it needs to be consistent with the rest of the JavaEdge site. Most users select results only from the first page or at the most first few pages into the site. It is very frustrating to click on a search link to find out that the content doesn't have anything to do with the search results. Furthermore, we have to minimize the amount of time any stale content appears in the search results. This means that when content is added or updated, our search engine should reflect those changes as soon as possible. Our search engine must remain relevant and provide high quality results. The user interface should be similar to these popular sites and, therefore, intuitive for the end user. Users should be able to use our search engine like any other web search engine they may be familiar with (for example, Google, Lycos, MSN Search, etc.). We want to incorporate the logical design of our content into the new search facility. To make full use of the JavaEdge application, it's crucial that users can simply search for the content in which they are interested and view previously published stories and comments. Search Requirements for the JavaEdge Application We'll use Lucene, which is the open source search engine from the Jakarta Apache Group, as our solution and show how to configure Lucene to work with the JavaEdge application. In this chapter, we will discuss some of the issues with search engines and present the design needed for an effective search tool. Also, we need something that can be easily customized to match the look and feel of our site. To avoid maintaining two different technology stacks on our servers, any search engine that we decide to use should be deployable into Tomcat, WebLogic, WebSphere, or another J2EE application server or servlet container. The JavaEdge application needs a search engine that can be plugged into our existing web infrastructure. Configuring Struts for our Pages and ActionsĮvery web site that has more than a few pages requires some attention to be given to information architecture, including navigation, a site map, and a search engine.Search Requirements for the JavaEdge Application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |