Ajax SOAP Client vs. WSE Web services

Background Our project is a rather large one which we estimate is already about 30-40% finished. This bid request is about the next 15-20% of the project. The rest of the project may be given to the same coder at the completion of this bid. A detailed requirements specification already exists, together with a working site and project source code. All these will be made available in full to the selected coder. Introduction Our company publishes a range of web services (Contract first/SOAP/WSDL/WSE3). The services feature an industry-specific search engine and directory administration features for users and companies. This project is about creating an AJAX web application that serves as a client to our web services, both enabling our customers to directly use them, but also to serve as a sample for those deciding to integrate with their own systems. The web application exists and the most important functionality is already there (ASP.NET 2, C#, XML, SOAP, Web Services, AJAX). Bid details This bid request aims to do two things: 1) Finish the administration part of the web application, which we estimate is about 50-60% finished. 2) Do bug fixes and add some features to the main search engine user interface. Coder(s) profile The chosen coder is expected to reuse existing code and graphical design where possible. The ideal coder(s) possesses great skills in both mapping XML nodes to forms and AJAX and GUI design skills to make a usable interface. Because of the time constraint we expect at least one full time developer to take part. ## Deliverables Coding guildelines We will provide a contract (wsdl and xml schemas) for each web service together with generated documentation. The web services makes extensive use of various Oasis SOAP standards, such as WS-Security and WS-SecureConversation for authentication. To make use of these standards the web application uses Microsoft Web Services Enhancements 3.0 (WSE). These are already implemented, meaning that no special concern should need to be taken here. Ajax integration The XMLHTTP and XMLHttpRequest are used to achieve the callbacks for the Ajax functionality. Data storage The web application does not rely on any internal permanent storage such as databases. All user and business oriented data are stored and retrieved using the web services provided. Any UI specific storage, such as that of column orders etc should be stored using the Set/Get name value pair operations on the User Web service. Application settings The web config file should be used for all technical application settings such as web service references etc Packaging deliverables The source code should be delivered as one Visual Studio solution, possibly containing several projects. Documentation The web application should be able to be used as a sample on how to integrate with our Web Services. Therefore it must be well documented. The code should be well documented enough to generate useful developer references. Technical enhancements/bugs - Performance issue with large search results in Internet Explorer. - Should be able to put application in debug mode which displays detailed error message instead of "XML Error". - The web references should not be compiled but reside in web.config. New features according to specification - Multiple currency support in search result detail module (4.1.3.1). - Legend module (4.1.5). - Restrictions in details module (4.1.4). - Family search (3.3.2). - Finish filter according to specification - Administration parts for Viewing/Creating/Updating/Deleting settings for: Company, Users, Currencies, Exchange rates, Calculation models and Locations(Cities, countries etc.) - Administration part for "My" User settings. GUI enhancements/bug fixes - Correct entry field validation according to the specification (4.1.1.2). - Latest search result tabs, information belonging to each tab should follow with each tab. - Details with repeating codes should not be displayed. - Sorting result by clicking on column header (4.1.2.4). - Drag, drop, expand a column (4.1.2.3). - Column headings should stay on top even when scrolling down. - Mouse-over effects to disappear when removing focus. - Display of information in latest search tabs should be changed to another order. - Should always have capital letters in Latest Search Tabs (IE). - Should be able to close particular tabs or all of them by Clear button. - Do not create Latest Search Tab if no result is found, display ‘No Result’ message in Result module. - Mouse-over box not to come over header. - Rules to open where you click so that you dont have to scroll again. - Heading for specific category in filter should be marked with different color if check box under that category has been unchecked. - We should validate for dates that do not exist, for example 29 feb 07, 31 apr etc. - Text font in destination part of filter is incorrect. - Cursor disappears in over/in some fields. An additional 8 minor GUI enhancements/bugs 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Development environment Microsoft Visual Studio 2005 .Net Framework 2.0 Microsoft WSE 3.0 No additional thirs party components may be used. Production environment Windows Server 2003 IIS 6 .Net Framework 2 WSE 3.0 Browser compatibility Microsoft Internet Explorer 7 Microsoft Internet Explorer 6 Gecko based (Firefox etc.) KHTML based (Safari etc.)