Download JAR files tagged by provide with all dependencies

The idea and motivation of the lindbergframework is to provide resources and simple solutions to problems based on the concept 'Plug and Use'. In the current version, the framework provides easy and simple solutions to the population of beans from SQL queries, abstraction of the complexities to access to stored procedures and stored functions , population of database cursors, transaction management, dependency injection, integration with Spring, JSF and Adobe Flex. The lindberg-persistence (LINP) solution, implements a important concept: separated repository of SQL commands. Among other resources.

The Jentity framework attempts to provide the Java platform with more powerful building blocks for integrating objects and components. The framework focuses on the challenge of maintaining consistent data or state in a dynamic environment. This is achieved by provide reusable, extensible objects, that can use to construct higher order structures like components, applications and systems. Examples of concrete problems that can be effectively solved by using the Jentity framework, are shared models, distributed models, MVC constructs.

This service implements the Indexer and Searcher interface of WebLab and connect to a remote SOLR engine in order to realize the functions. The connection is mandatory and thus the remote SOLR server should be started beforehand. Configuration of the SOLR server URL is found in src/main/webapp/WEB-INF/cxf-servlet.xml . See in particular "indexerServiceBean" and "searcherServiceBean". Moreover, the service implements several "Analyser" services that could be included in a complete search chain in order to: - enrich a ResultSet with metadata about Hits (see resultSetMetaEnricherServiceBean) - highlight snippet in ResultSet (see highlighterServiceBean) - provide facets related to the current results (see facetSuggestionServiceBean) - suggest spell correction of the original query (see spellSuggestionServiceBean)

This library aims to provide a central access point to the services exposed on the ESB without forcing each part of the system to know the actual location of the ESB and the names of the exposed endpoints. For this sake it allows to map service URI (ie referring to service in webLab taxonomy) to the actual exposed URL on the ESB within the context of a specific project. The library and the configuration should be added in portal lib in order to be central and available to any portlets. The mapping is done in a simple spring config file "webLabClient.xml" which must be accessible in JAVA classpath.

JDOM is a Java-oriented object model which models XML documents. It provides a Java-centric means of generating and manipulating XML documents. While JDOM interoperates well with existing standards such as the Simple API for XML (SAX) and the Document Object Model (DOM), it is not an abstraction layer or enhancement to those APIs. Rather, it seeks to provide a robust, light-weight means of reading and writing XML data without the complex and memory-consumptive options that current API offerings provide. built July 23 2009

The project provides an implementation of REPOSITORY PATTERN using HIBERNATE for data access. The a goal of this project is to provide an EASY TO USE API that allows to write most of CRUD operations you will need in development of end user applications in ONE LINE OF CODE even for developers who are unfamiliar with Hibernate. We provide a well tested set of CRUD operations which were assembled in more than 4 years of refactoring of projects of our clients. Instead of writing same code over and over again we encourage you to try this API on your own project and see how many lines of code YOU can replace with JUST ONE LINE.

"Tests with Parameters" allows you to simply add parameters to your JUnit test methods. TwiP calls such methods with all possible combinations of their parameters... or at least some reasonable subset of commonly failing values in the case of Integers, etc. You can further reduce these values with an assume expression in an annotation, e.g. ">= 0". Alternatively you can specify a static method or field to provide the values for your test method(s), if you want to test with other than the default values. By using TwiP you change the semantics of your tests from existence to for-all quantifiers, i.e. you specify "all ravens are black" instead of "Abraxas is black", "Toni is black", etc. This moves your tests closer to an executable specification, so TwiP is a very nice addition to BDD.