-
LONI.tree.GraphObject.Module
-
anvil.script.Module
interface Module
@author : Jani Lehtim�ki
-
apigen.adt.api.types.Module
-
ast.Module
-
avrora.syntax.Module
The Module
class collects together the instructions and data into an AVR assembly program.
@author Ben L. Titzer
-
ca.grimoire.jnoise.modules.Module
Basic interface common to all noise modules. A noise module represents a deterministic function in a 3-dimensional space returning a scalar value -- the "noise value" -- for each point within that space.
Noise modules may base the generation of noise values on anything at all, including the output of other modules. However, the noise value of a module at a given location must be deterministic.
-
ceylon.language.meta.declaration.Module
-
ch.bfh.swos.gandalf.model.Module
Entity implementation class for Entity: Module
-
ch.entwine.weblounge.common.site.Module
The module interface defines the method that may be called on weblounge module objects.
-
ch.tatool.data.Module
Interface for a Module.
@author Michael Ruflin
-
com.alibaba.citrus.service.moduleloader.Module
代表一个模块。
@author Michael Zhou
-
com.atlassian.labs.speakeasy.commonjs.Module
-
com.caucho.inject.Module
-
com.claymus.site.Module
-
com.dgwave.car.common.Module
Module Representation.
@author Akber Choudhry (Adapted from Ceylon Module Resolver)
-
com.eastidea.qaforum.entity.Module
-
com.eastidea.qaforum.model.Module
-
com.espertech.esper.client.deploy.Module
Represent a deployment unit consisting of deployment declarative information (module name, uses and imports) as well as EPL statements represented by {@link ModuleItem}. May have an additional user object and archive name and uri pointing to the module source attached.
The module URI gets initialized with the filename, resource or URL being read, however may be overridden and has not further meaning to the deployment.
The archive name and user object are opportunities to attach additional deployment information.
-
com.fasterxml.jackson.databind.Module
Simple interface for extensions that can be registered with {@link ObjectMapper}to provide a well-defined set of extensions to default functionality; such as support for new data types.
-
com.github.overengineer.container.module.Module
@author rees.byars
-
com.google.inject.Module
A module contributes configuration information, typically interface bindings, which will be used to create an {@link Injector}. A guice-based application is ultimately composed of little more than a set of {@code Module}s and some bootstrapping code.
Your Module classes can use a more streamlined syntax by extending {@link AbstractModule} rather than implementing this interface directly.
-
com.googlecode.gwtrpccommlayer.client.Module
-
com.intellij.openapi.module.Module
Represents a module in an IDEA project.
@see ModuleManager#getModules()
@see ModuleComponent
-
com.ketayao.ketacustom.entity.main.Module
@author
ketayaoVersion 1.1.0
@since 2012-8-2 下午5:36:39
-
com.lgx8.right.entities.Module
Module entity.
@author MyEclipse Persistence Tools
-
com.puppetlabs.geppetto.forge.v2.model.Module
-
com.redhat.ceylon.compiler.java.metadata.Module
-
com.redhat.ceylon.compiler.java.runtime.Main.ClassPath.Module
-
com.redhat.ceylon.compiler.typechecker.model.Module
-
com.rometools.rome.feed.module.Module
Base class for modules describing Metadata of feeds. Examples of such modules are the Dublin Core and Syndication modules.
@author Alejandro Abdelnur
-
com.sun.enterprise.config.serverbeans.Module
Tag Interface for any module
@author Jerome Dochez
-
com.sun.enterprise.module.Module
@author Sanjeeb.Sahoo@Sun.COM
-
com.sun.syndication.feed.module.Module
Base class for modules describing Metadata of feeds. Examples of such modules are the Dublin Core and Syndication modules.
@author Alejandro Abdelnur
-
com.sun.xml.internal.ws.api.server.Module
Represents an object scoped to the current "module" (like a JavaEE web appliation).
This object can be obtained from {@link Container#getSPI(Class)}.
The scope of the module is driven by {@link W3CEndpointReferenceBuilder#build()}'s requirement that we need to identify a {@link WSEndpoint} that has a specificservice/port name.
For JavaEE containers this should be scoped to a JavaEE application. For other environment, this could be scoped to any similar notion. If no such notion is available, the implementation of {@link Container} can returna new {@link Module} object each time {@link Container#getSPI(Class)} is invoked.
There's a considerable overlap between this and {@link HttpAdapterList}. The SPI really needs to be reconsidered
@see Container
@author Kohsuke Kawaguchi
@since 2.1 EA3
-
com.sun.xml.ws.api.server.Module
Represents an object scoped to the current "module" (like a JavaEE web appliation).
This object can be obtained from {@link Container#getSPI(Class)}.
The scope of the module is driven by {@link W3CEndpointReferenceBuilder#build()}'s requirement that we need to identify a {@link WSEndpoint} that has a specificservice/port name.
For JavaEE containers this should be scoped to a JavaEE application. For other environment, this could be scoped to any similar notion. If no such notion is available, the implementation of {@link Container} can returna new {@link Module} object each time {@link Container#getSPI(Class)} is invoked.
There's a considerable overlap between this and {@link HttpAdapterList}. The SPI really needs to be reconsidered
@see Container
@author Kohsuke Kawaguchi
@since 2.1 EA3
-
com.uwyn.drone.core.Module
-
cu.ftpd.modules.Module
@author Markus Jevring
@since 2008-okt-01 - 17:50:12
@version $Id: Module.java 292 2009-03-04 19:44:36Z jevring $
-
dtool.ast.definitions.Module
D Module. The top-level AST class, has no parent, is the first and main node of every compilation unit.
-
easyJ.system.data.Module
-
edu.byu.ece.rapidSmith.design.Module
This class represents the modules as found in XDL. They are used to describe hard macros and RPMs and instances of each.
@author Chris LavinCreated on: Jun 22, 2010
-
edu.harvard.hul.ois.jhove.Module
-
edu.isi.stella.Module
-
edu.mit.csail.sdg.alloy4compiler.ast.Module
This interface represents an Alloy module.
-
etch.compiler.ast.Module
A module declaration from the etch idl.
-
fr.tm.elibel.smartqvt.qvt.qvtoperational.Module
-
gri.gridp.modules.Module
Encapsulating class for an AppXML module. This module allows us define one or more functions of a program. It has a header section describing the program and may also include global parameter definitions. A list of one or more functions will then be given, each of which indicates one way in which the program can run. Each function will have its own list of parameters needed to run that function.
@author dan.rogers
-
ir.xweb.module.Module
-
model.Module
-
models.Module
@author Steve Chaloner (steve@objectify.be)
-
net.hasor.core.Module
Hasor模块。
@version : 2013-3-20
@author 赵永春 (zyc@hasor.net)
-
net.paoding.rose.web.impl.module.Module
{@link Module}代表了在同一个web程序中的一个模块。不同的模块包含一些特定的控制器对象、控制器拦截器、控制器异常处理器。 不同的模块共享了ServletContext以及整个程序的中间层、资源层。
一个web程序的不同的模块有不同的名字和路径。作为 {@link Module}接口本身并没有要求模块的名字和路径有什么关系, 但在实现上模块的路径是由其名字决定的,即path=/name,比如名字为admin的模块,路径将是/admin。 作为一个特例,名字为root的模块路径则只是空串。
一个HTTP请求将根据它的URI,映射到相应的web程序中(由web容器处理),而后又映射给具体的module模块(由Rose处理)。 映射规则以模块的路径为依据(名字此时不参与这个决策)。
@author 王志亮 [qieqie.wang@gmail.com]
-
net.sourceforge.marathon.api.module.Module
-
org.activiti.workflow.simple.alfresco.model.config.Module
@author Joram Barrez
-
org.apache.accumulo.server.test.randomwalk.Module
A module is directed graph of tests
-
org.apache.accumulo.test.randomwalk.Module
A module is directed graph of tests
-
org.apache.axis2.modules.Module
Every module provides an implementation of this class. Modules are in one of three states: "available" and "initialized". All modules that the runtime detects (from the system modules/ directory or from other means) are said to be in the "available" state. If some service indicates a dependency on this module then the module is initialized (once for the life of the system) and the state changes to "initialized".
Any module which is in the "initialized" state can be engaged as needed by the engine to respond to a message. Currently module engagement is done via deployment (using module.xml). In the future we may engage modules programmatically by introducing an engage() method to this interface, thereby allowing more dynamic scenarios.
-
org.apache.cayenne.di.Module
Represents a unit of configuration of the Cayenne DI container.
@since 3.1
-
org.apache.etch.compiler.ast.Module
A module declaration from the etch idl.
-
org.apache.geronimo.j2ee.deployment.Module
@version $Rev: 391549 $ $Date: 2006-04-05 08:41:31 +0200 (Wed, 05 Apr 2006) $
-
org.apache.geronimo.jee.application.Module
3.org/2001/XMLSchema}anyType"> <sequence> <choice> <element name="connector" type="{http://geronimo.apache.org/xml/ns/j2ee/application-2.0}pathType"/> <element name="ejb" type="{http://geronimo.apache.org/xml/ns/j2ee/application-2.0}pathType"/> <element name="java" type="{http://geronimo.apache.org/xml/ns/j2ee/application-2.0}pathType"/> <element name="web" type="{http://geronimo.apache.org/xml/ns/j2ee/application-2.0}pathType"/> </choice> <choice> <element name="alt-dd" type="{http://geronimo.apache.org/xml/ns/j2ee/application-2.0}pathType"/> <any/> </choice> </sequence> </restriction> </complexContent> </complexType>
@version $Rev: 672450 $ $Date: 2008-06-28 09:21:07 +0800 (Sat, 28 Jun 2008) $
-
org.apache.hivemind.annotations.definition.Module
-
org.apache.hivemind.internal.Module
The definition of a HiveMind Module. A Module is a container of service extension points and configuration extension points. It also acts as a "gateway" so that services and configurations in other modules may be accessed.
Why do we expose the Module rather than the {@link org.apache.hivemind.internal.RegistryInfrastructure}? It's more than just qualifying ids before passing them up to the RI. At some future point, a concept of visibility will be added to HiveMind. This will make many services and configurations private to the module which defines them and the necessary visibility filtering logic will be here.
@author Howard Lewis Ship
-
org.apache.karaf.jaas.config.impl.Module
POJO for a login module. It contains the class name, flags and a map of options.
-
org.apache.tuscany.model.assembly.Module
A specialized {@link Implementation} that defines a modular unit of assembly.A Module denotes the extent of assembly in which pass-by-reference semantics are supported.
-
org.apache.vxquery.xmlquery.query.Module
-
org.apache.vysper.xmpp.modules.Module
a module plugs new functionality into the server, most probably an implementation for a XEP. this functionality spans:
- adding services (implementing ServerRuntimeContextService) to the server which can be accessed by other modules
- doing initializations, for example adding request listeners to the ServiceDiscoveryRequestListenerRegistry
- adding dictionaries with new stanza handlers getting registered with the server which then get called as matching stanzas arrive
TODO: think about returning the supported XEPs
@see org.apache.vysper.xmpp.modules.DefaultModule recommended for simple modules not involved with service disco
@see org.apache.vysper.xmpp.modules.DefaultDiscoAwareModule recommended for modules responding to service disco requests
@see org.apache.vysper.xmpp.modules.ServerRuntimeContextService
@see org.apache.vysper.xmpp.protocol.HandlerDictionary
@author The Apache MINA Project (dev@mina.apache.org)
-
org.apdplat.module.module.model.Module
模块对象
@author 杨尚川
-
org.codehaus.jackson.map.Module
Simple interface for extensions that can be registered with {@link ObjectMapper}to provide a well-defined set of extensions to default functionality; such as support for new data types.
@since 1.7
-
org.convey.user.registration.model.Module
-
org.cruxframework.crux.core.rebind.module.Module
@author Thiago da Rosa de Bustamante
-
org.directwebremoting.extend.Module
@author Mike Wilson [mikewse at g mail dot com]
-
org.dmd.mvw.tools.mvwgenerator.extended.Module
-
org.drools.guvnor.client.rpc.Module
This contains data for a module configuration.
-
org.dru.clay.respository.artifact.Module
-
org.eclipse.jetty.start.Module
Represents a Module metadata, as defined in Jetty.
-
org.elasticsearch.common.inject.Module
A module contributes configuration information, typically interface bindings, which will be used to create an {@link Injector}. A Guice-based application is ultimately composed of little more than a set of {@code Module}s and some bootstrapping code.
Your Module classes can use a more streamlined syntax by extending {@link AbstractModule} rather than implementing this interface directly.
In addition to the bindings configured via {@link #configure}, bindings will be created for all methods annotated with {@literal @}{@link Provides}. Use scope and binding annotations on these methods to configure the bindings.
-
org.evolizer.versioncontrol.cvs.model.entities.Module
This class represents the concept of a Module, e.g. a plug-in of Eclipse, the client-part of a client-server application etc. Introducing this model entity allows us to distinguish files that occur twice, e.g., once in plug-in A and once in plug-in B.
@author wuersch
-
org.exist.xquery.Module
Defines an XQuery library module. A module consists of function definitions and global variables. It is uniquely identified by a namespace URI and an optional default namespace prefix. All functions provided by the module have to be defined in the module's namespace. Modules can be either internal or external: internal modules are collections of Java classes, each being a subclass of {@link org.exist.xquery.Function}. External modules are defined by the XQuery "module" directive and can be loaded with "import module". Modules are dynamically loaded by class {@link org.exist.xquery.XQueryContext}, either during the initialization phase of the query engine (for the standard library modules) or upon an "import module" directive.
@author Wolfgang Meier (wolfgang@exist-db.org)
-
org.fcrepo.server.Module
Base class for Fedora server modules.
A Module
is a singleton object of a Fedora Server
instance with a simple lifecycle, supported by the initModule()
and shutdownModule()
methods, which are automatically called during server startup and shutdown, respectively.
Modules are configured via "param" elements inside module elements in the configuration file. An instance of each module specified in the configuration file is automatically created at startup and is available via the getModule(String)
instance method of the Server
class.
@author Chris Wilper
-
org.gatein.portal.controller.resource.script.Module
-
org.gradle.api.artifacts.Module
A {@code Module} represents the meta-information about a project which should be used when publishing themodule.
-
org.jabusuite.core.modules.Module
@author hilwers
-
org.jahia.ajax.gwt.client.widget.edit.mainarea.Module
Interface defining what is a mdoule on a rendered page in edit mode A module could be selected, edited, dragged etc.
-
org.jayasoft.woj.tools.dl.Module
-
org.jboss.as.console.client.shared.subsys.ejb3.model.Module
@author Heiko Braun
@date 11/28/11
-
org.jboss.classloading.spi.dependency.Module
-
org.jboss.gravia.runtime.Module
An installed module in the Runtime.
A module must have a unique {@link ResourceIdentity} in the Runtime.
Gravia stays out of the business of resolving module's at runtime. Every module has an associated {@link ClassLoader} when it is installed in the runtime already.Modularity must be dealt with in the layer using the Gravia runtime.
For example, a servlet container like Tomcat may choose to create one Module per web application. Multiple modules may share the same class loader or may even all have the same class loader association. This allows GRavia to run on a flat class path (e.g. a plain JUnit test)
When installed it is also assigned a {@code long} identity, chosen by the Runtime.This identity does not change during the lifecycle of a module. Uninstalling and then reinstalling the module creates a new unique {@code long} identity.
A module can be in one of six states:
- {@link State#INSTALLED}
- {@link State#RESOLVED}
- {@link State#STARTING}
- {@link State#ACTIVE}
- {@link State#STOPPING}
- {@link State#UNINSTALLED}
A module should only have active threads of execution when its state is one of {@code STARTING}, {@code ACTIVE}, or {@code STOPPING}. An {@code UNINSTALLED} module can not be set to another state;it can only be reached because references are kept somewhere.
The Runtime is the only entity that is allowed to create {@code Module}objects, and these objects are only valid within the Runtime that created them.
Modules have a natural ordering such that if two {@code Module}s have the same {@link #getModuleId() module id} they are equal. A {@code Module} isless than another {@code Module} if it has a lower {@link #getModuleId() module id} and is greater if it has a higher module id.
@author thomas.diesler@jboss.com
@since 27-Sep-2013
@ThreadSafe
-
org.jboss.modules.Module
A module is a unit of classes and other resources, along with the specification of what is imported and exported by this module from and to other modules. Modules are created by {@link ModuleLoader}s which build modules from various configuration information and resource roots.
@author
David M. Lloyd
@author
John Bailey
@author
Flavia Rainone
@author Jason T. Greene
@author thomas.diesler@jboss.com
@apiviz.landmark
-
org.jdesktop.wonderland.modules.Module
The Module class represents a single module within Wonderland. A module consists of several possible subcomponents: artwork, WFSs, and plugins. Artwork either includes textures, images, and 3D geometry. Modules may also contain Wonderland Filesystems (WFSs) that assemble the artwork resources into a subworld component. Plugins are runnable code that extend the functionality of the server and/or client.
A module is stored within a jar/zip archive file. To open an existing module archive file, use the ModuleFactory.open() method. Once open, users of this class may query for the module's artwork, WFSs, and plugins.
Modules also have major.minor version numbers and a list of other modules upon which this module depends.
This is an abstract class -- it is typically subclassed to handle whether the module was loaded on disk or from an archive file.
@author Jordan Slott
-
org.jfrog.build.api.Module
Contains the build module information
@author Noam Y. Tenne
-
org.jivesoftware.openfire.container.Module
Logical, server-managed entities must implement this interface. A module represents an operational unit and may contain zero or more services and rely on zero or more services that may be hosted by the container.
In order to be hosted in the Jive server container, all modules must:
- Implement the Module interface
- Have a public no-arg constructor
The Jive container will run all modules through a simple lifecycle:
constructor -> initialize() -> start() -> stop() -> destroy() -> finalizer |<-----------------------| ^ | | V----------------------------------->
The Module interface is intended to provide the simplest mechanism for creating, deploying, and managing server modules.
@author Iain Shigeoka
-
org.lilyproject.runtime.module.Module
A module.
-
org.molgenis.model.elements.Module
Annotation classes. Multiple entities can refer to one module.
@author Morris Swertz
-
org.openbravo.model.ad.module.Module
Entity class for entity ADModule (stored in table AD_Module). NOTE: This class should not be instantiated directly. To instantiate this class the {@link org.openbravo.base.provider.OBProvider} should be used.
-
org.openbravo.services.webservice.Module
-
org.openhab.binding.netatmo.internal.messages.DeviceListResponse.Module
-
org.openquark.cal.machine.Module
Warning- this class should only be used by the CAL runtime implementation. It is not part of the external API of the CAL platform.
Module collects together machine specific information about the contents of a module and associates it with the MoudleTypeInfo for that module. Modules contain the executable program elements and have a name. Creation date: (3/6/00 9:48:37 AM)
@author LWE
-
org.pdtextensions.repos.Module
Default implementation of a module that knows its versions.
@author mepeisen
-
org.pentaho.reporting.libraries.base.boot.Module
A module encapsulates optional functionality within a project. Modules can be used as an easy way to make projects more configurable.
The module system provides a controled way to check dependencies and to initialize the modules in a controlled way.
@author Thomas Morgner
-
org.python.pydev.parser.jython.ast.Module
-
org.qi4j.api.structure.Module
API for interacting with a Module. Instances of this can be accessed by using the {@link Structure}injection scope.
-
org.rascalmpl.ast.Module
-
org.richfaces.application.Module
Configuration module allows to configure RichFaces services.
Implementations are loaded in conformance with {@link java.util.ServiceLoader} (/META-INF/services/org.richfaces.services.Module).
@author asmirnov@exadel.com
-
org.sgx.yuigwt.galleryexplorer.client.api.Module
-
org.springframework.xd.integration.util.jmxresult.Module
Represents an XD Module that is returned from a JMX Query.
@author Glenn Renfro
-
org.springframework.xd.module.core.Module
@author Mark Fisher
@author David Turanski
@author Gary Russell
-
org.terasology.module.Module
-
org.unidal.initialization.Module
-
org.xtext.tortoiseshell.lib.Module
-
org.zkybase.model.Module
A module, which is a version-free abstraction over packages.
@author Willie Wheeler (willie.wheeler@gmail.com)
-
pl.patrykpacewicz.guice.Module
-
promauto.jroboplc.Module
@author denis
-
pushy.Module
Module is the base class of all objects returned by {@link Client#getModule}.
-
scalaxb.compiler.Module
-
test.list.types.Module
-
tree.Module
-
xbird.xquery.Module
@author Makoto YUI (yuin405+xbird@gmail.com)