compile

The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application:

test

The following is a list of test dependencies for this project. These dependencies are only required to compile and run unit tests for the application:

compile

The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application:

Dependency Tree

• org.vpda:vpda-server-appCore:jar
  • org.vpda:vpda-server-viewProvider:jar
    • org.vpda:vpda-server-core:jar
    • org.vpda:vpda-server-dataModel:jar
    • org.vpda:vpda-server-persistence:jar
    • org.vpda:vpda-common-abstractClientViewProviderUI:jar
      • org.vpda:vpda-common-clientServerViewProvider:jar

  • org.vpda:vpda-common-util:test-jar:tests
  • org.vpda:vpda-common-core:test-jar:tests
    • org.picocontainer:picocontainer:jar
    • commons-vfs:commons-vfs:jar
    • commons-httpclient:commons-httpclient:jar
    • commons-io:commons-io:jar

  • org.vpda:vpda-common-clientServerCore:test-jar:tests
    • org.apache.httpcomponents:httpclient:jar

  • org.vpda:vpda-common-abstractClientCore:jar
  • org.vpda:vpda-common-abstractClientCore:test-jar:tests
    • org.vpda:vpda-common-util:jar
    • org.vpda:vpda-common-core:jar
    • org.vpda:vpda-common-clientServerCore:jar

  • com.h2database:h2:jar
  • toplink.essentials:toplink-essentials:jar
    • javax.persistence:persistence-api:jar

  • com.thoughtworks.xstream:xstream:jar
    • xpp3:xpp3_min:jar

  • xom:xom:jar
  • junit:junit:jar
  • jdepend:jdepend:jar
  • org.easymock:easymock:jar

Dependency Listings

vpda-server-appCore

Application core abstract classes. These are mainly domain not specific abstract classes regarding to DB and persistence.

http://vpda.org/vpda-server/vpda-server-appCore

vpda-server-viewProvider

Implementation for server view providers. Here we provider view providers for runtime data and also DB view providers.

http://vpda.org/vpda-server/vpda-server-viewProvider

vpda-server-core

Server core module provided common user management functionality and common interface to server

http://vpda.org/vpda-server/vpda-server-core

vpda-server-dataModel

Serval data modeling provides generation of DDL scripts using reflection from java classes or programatically. This way we have consistent DB mapping for JPA and also for JDBC view providers implementations.

http://vpda.org/vpda-server/vpda-server-dataModel

vpda-server-persistence

Server persistence provides common api for application persistence. This some configuration entry point to all server persistence. here we define interfaces using which we can lookup jdbc data sources,jpa entity manager factories and also bussiness services. Bussiness services are POJO with user managemant and transaction support. Also very simple implementation for testing is provided here.

http://vpda.org/vpda-server/vpda-server-persistence

vpda-common-abstractClientViewProviderUI

Abstract client view provider module provide abstraction for both client and server view of view provider UI. This means abstract client view provider UI for concreete platforms and also basic commands using which server controls client flow.

http://vpda.org/vpda-common/vpda-common-abstractClient/vpda-common-abstractClientViewProviderUI

vpda-common-clientServerViewProvider

Client server provides interfaces for main idea of this framework - view providers and view providers related components.

http://vpda.org/vpda-common/vpda-common-clientServer/vpda-common-clientServerViewProvider

vpda-common-util

Utility module with only static utility classes. Also some helper tools are located here.

http://vpda.org/vpda-common/vpda-common-util

vpda-common-common-core

Common core module provides module managament,common basic services like localization,resources. Also basic user session interfaces and basic communication interfaces are provided here. PicoContainer is used as IOC container, but there is dependency to picocontainer only in module entry of each module. Constructor dependency is used preferable throgh project, which means once you construct object using its constructor, u can use it. This does not depends whether you use component in context of container or programatically (e.g in tests)

http://vpda.org/vpda-common/vpda-common-core

PicoContainer Core

Please refer to the <a href="http://picocontainer.org/">main website</a> for documentation.

http://www.picocontainer.org/picocontainer

Commons VFS

VFS is a Virtual File System library.

http://jakarta.apache.org/commons/vfs/

HttpClient

The HttpClient component supports the client-side of RFC 1945 (HTTP/1.0) and RFC 2616 (HTTP/1.1) , several related specifications (RFC 2109 (Cookies) , RFC 2617 (HTTP Authentication) , etc.), and provides a framework by which new request types (methods) or HTTP extensions can be created easily.

http://jakarta.apache.org/commons/httpclient/

Commons IO

Commons-IO contains utility classes, stream implementations, file filters, and endian classes.

http://jakarta.apache.org/commons/io/

vpda-common-clientServerCore

Client server core is communication module between client and server. Here are provided basic interfaces for basic client server communication. Also menu interface and basic components interfaces are located here.

http://vpda.org/vpda-common/vpda-common-clientServer/vpda-common-clientServerCore

HttpClient (base module)

HttpComponents Client (base module)

http://hc.apache.org/httpcomponents-client

vpda-common-abstractClientCore

Abstract client core module provide client abstraction for both client and server view. This means basic client UI and also view provider UI. This way we have some abstraction for client platforms and also server can create new commands which can control client ui flow.

http://vpda.org/vpda-common/vpda-common-abstractClient/vpda-common-abstractClientCore

vpda-common-abstractClientCore

Abstract client core module provide client abstraction for both client and server view. This means basic client UI and also view provider UI. This way we have some abstraction for client platforms and also server can create new commands which can control client ui flow.

http://vpda.org/vpda-common/vpda-common-abstractClient/vpda-common-abstractClientCore

vpda-common-util

Utility module with only static utility classes. Also some helper tools are located here.

http://vpda.org/vpda-common/vpda-common-util

vpda-common-common-core

Common core module provides module managament,common basic services like localization,resources. Also basic user session interfaces and basic communication interfaces are provided here. PicoContainer is used as IOC container, but there is dependency to picocontainer only in module entry of each module. Constructor dependency is used preferable throgh project, which means once you construct object using its constructor, u can use it. This does not depends whether you use component in context of container or programatically (e.g in tests)

http://vpda.org/vpda-common/vpda-common-core

vpda-common-clientServerCore

Client server core is communication module between client and server. Here are provided basic interfaces for basic client server communication. Also menu interface and basic components interfaces are located here.

http://vpda.org/vpda-common/vpda-common-clientServer/vpda-common-clientServerCore

H2 Database Engine

H2 Database Engine

http://www.h2database.com

Unnamed - toplink.essentials:toplink-essentials:jar:2.1-20

Unnamed - javax.persistence:persistence-api:jar:1.0.2

XStream Core

Unnamed - xpp3:xpp3_min:jar:1.1.3.4.O

MXP1 is a stable XmlPull parsing engine that is based on ideas from XPP and in particular XPP2 but completely revised and rewritten to take the best advantage of latest JIT JVMs such as Hotspot in JDK 1.4+.

http://www.extreme.indiana.edu/xgws/xsoap/xpp/mxp1/

xom

http://www.xom.nu

JUnit

JUnit is a regression testing framework written by Erich Gamma and Kent Beck. It is used by the developer who implements unit tests in Java.

http://junit.org

Unnamed - jdepend:jdepend:jar:2.9.1

EasyMock

EasyMock provides Mock Objects for interfaces in JUnit tests by generating them on the fly using Java's proxy mechanism

http://www.easymock.org