Download JAR files tagged by layer with all dependencies
struts from group struts (version 1.2.9)
The core of the Struts framework is a flexible control layer based on standard technologies like Java Servlets, JavaBeans, ResourceBundles, and Extensible Markup Language (XML), as well as various Jakarta Commons packages. Struts encourages application architectures based on the Model 2 approach, a variation of the classic Model-View-Controller (MVC) design paradigm. Struts provides its own Controller component and integrates with other technologies to provide the Model and the View. For the Model, Struts can interact with any standard data access technology, including Enterprise Java Beans, JDBC, and Object Relational Bridge. For the View, Struts works well with JavaServer Pages, including JSTL and JSF, as well as Velocity Templates, XSLT, and other presentation systems. The Struts framework provides the invisible underpinnings every professional web application needs to survive. Struts helps you create an extensible development environment for your application, based on published standards and proven design patterns.
366 downloads
Artifact struts
Group struts
Version 1.2.9
Last update 23. March 2006
Organization The Apache Software Foundation
URL http://struts.apache.org/
License not specified
Dependencies amount 8
Dependencies commons-beanutils, commons-digester, commons-fileupload, commons-logging, commons-validator, oro, antlr, xalan,
There are maybe transitive dependencies!
Group struts
Version 1.2.9
Last update 23. March 2006
Organization The Apache Software Foundation
URL http://struts.apache.org/
License not specified
Dependencies amount 8
Dependencies commons-beanutils, commons-digester, commons-fileupload, commons-logging, commons-validator, oro, antlr, xalan,
There are maybe transitive dependencies!
prolobjectlink-jpi from group io.github.prolobjectlink (version 1.1)
Java Prolog Interface (JPI) is an Application Provider Interface (API) for interaction between Java and Prolog programming languages. Is a bidirectional interface that communicate Java applications with Prolog program or database and Prolog procedures with Java class and methods.
JPI is an abstraction layer over concrete prolog drivers over Prolog Engines. This API define all mechanism to interact with any Prolog Engine and maintain the application independent to a specific underlying engine. JPI have several connectors to open source prolog engines like SWI, YAP, XSB native engines and tuProlog, jTrolog, jLog Java based prolog engines.
JPI study all related Java-Prolog integration libraries and take the betters features from each solution with the propose to achieve a common integration interface. The last feature allows switch the under laying Prolog Engine driver and the application code still be the same.
JPI run over any Java Virtual Machine that support Java SE 5 or above. The project was tested over HotSpot, Open J9 and JRockit Virtual Machines over Operating Systems like Windows (7,8,10), Linux (Debian, Ubuntu) and Mac OS X. Can be deployed on Servlets Containers like Jetty, Tomcat or Glassfish Application Server.
JPI can be include in any Java Project using the commonest Java Integration Development Enviroment (IDE) like Eclipse, Netbeans, IntelijIDEA and so on.
JPI is developed and maintained by Prolobjectlink Project an open source initiative for build logic based applications using Prolog like fundamental Logic Programming Language in the persistence layer and application programming.
Group: io.github.prolobjectlink Artifact: prolobjectlink-jpi
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact prolobjectlink-jpi
Group io.github.prolobjectlink
Version 1.1
Last update 02. June 2022
Organization Prolobjectlink Project
URL https://prolobjectlink.github.io/${project.name}
License MIT
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group io.github.prolobjectlink
Version 1.1
Last update 02. June 2022
Organization Prolobjectlink Project
URL https://prolobjectlink.github.io/${project.name}
License MIT
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
multiLayerPerceptrons from group nz.ac.waikato.cms.weka (version 1.0.10)
This package currently contains classes for training multilayer perceptrons with one hidden layer, where the number of hidden units is user specified. MLPClassifier can be used for classification problems and MLPRegressor is the corresponding class for numeric prediction tasks. The former has as many output units as there are classes, the latter only one output unit. Both minimise a penalised squared error with a quadratic penalty on the (non-bias) weights, i.e., they implement "weight decay", where this penalised error is averaged over all training instances. The size of the penalty can be determined by the user by modifying the "ridge" parameter to control overfitting. The sum of squared weights is multiplied by this parameter before added to the squared error. Both classes use BFGS optimisation by default to find parameters that correspond to a local minimum of the error function. but optionally conjugated gradient descent is available, which can be faster for problems with many parameters. Logistic functions are used as the activation functions for all units apart from the output unit in MLPRegressor, which employs the identity function. Input attributes are standardised to zero mean and unit variance. MLPRegressor also rescales the target attribute (i.e., "class") using standardisation. All network parameters are initialised with small normally distributed random values.
Group: nz.ac.waikato.cms.weka Artifact: multiLayerPerceptrons
Show all versions Show documentation Show source
Show all versions Show documentation Show source
10 downloads
Artifact multiLayerPerceptrons
Group nz.ac.waikato.cms.weka
Version 1.0.10
Last update 31. October 2016
Organization University of Waikato, Hamilton, NZ
URL http://weka.sourceforge.net/doc.packages/multiLayerPerceptrons
License GNU General Public License 3
Dependencies amount 1
Dependencies weka-dev,
There are maybe transitive dependencies!
Group nz.ac.waikato.cms.weka
Version 1.0.10
Last update 31. October 2016
Organization University of Waikato, Hamilton, NZ
URL http://weka.sourceforge.net/doc.packages/multiLayerPerceptrons
License GNU General Public License 3
Dependencies amount 1
Dependencies weka-dev,
There are maybe transitive dependencies!
osgi-tests from group org.apache.axis2 (version 1.6.3)
Artifact osgi-tests
Group org.apache.axis2
Version 1.6.3
Last update 27. June 2015
Organization not specified
URL http://axis.apache.org/axis2/java/core/
License not specified
Dependencies amount 1
Dependencies axis2-testutils,
There are maybe transitive dependencies!
Group org.apache.axis2
Version 1.6.3
Last update 27. June 2015
Organization not specified
URL http://axis.apache.org/axis2/java/core/
License not specified
Dependencies amount 1
Dependencies axis2-testutils,
There are maybe transitive dependencies!
axis2-parent from group org.apache.axis2 (version 1.6.3)
Axis2 is an effort to re-design and totally re-implement both Axis/Java and
(eventually) Axis/C++ on a new architecture. Evolving from the now standard "handler chain"
model which Axis1 pioneered, Axis2 is developing a more flexible pipeline architecture which
can yet be managed and packaged in a more organized manner. This new design acknowledges the
maturing of the Web services space in terms of new protocols such as WS-ReliableMessaging,
WS-Security and WS-Addressing that are built on top of the base SOAP system. At the time
Axis1 was designed, while it was fully expected that other protocols such as
WS-ReliableMessaging would be built on top of it, there was not a proper extension
architecture defined to enable clean composition of such layers. Thus, one of the key
motivations for Axis2 is to provide a clean and simple environment for like Apache Sandesha
and Apache WSS4J to layer on top of the base SOAP system. Another driving force for Axis2 as
well as the move away from RPC oriented Web services towards more document-oriented, message
style asynchronous service interactions. The Axis2 project is centered on a new
representation for SOAP messages called AXIOM (AXIs Object Model). AXIOM consists of two
parts: a complete XML Infoset representation and a SOAP Infoset representation on top of
that. The XML Infoset representation provides a JDOM-like simple API but is built on a
deferred model via a StAX-based (Streaming API for XML) pull parsing API. A key feature of
AXIOM is that it allows one to stop building the XML tree and just access the pull stream
directly; thus enabling both maximum flexibility and maximum performance. This approach
allows us to support multiple levels of abstraction for consuming and offering Web services:
using plain AXIOM, using generated code and statically data-bound data types and so on. At
the time of Axis1's design, RPC-style, synchronous, request-response interactions were the
order of the day for Web services. Today service interactions are much more message
-oriented and exploit many different message exchange patterns. The Axis2 engine
architecture is careful to not build in any assumptions of request-response patterns to
ensure that it can be used easily to support arbitrary message exchange
patterns.
Group: org.apache.axis2 Artifact: axis2-parent
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact axis2-parent
Group org.apache.axis2
Version 1.6.3
Last update 27. June 2015
Organization not specified
URL http://axis.apache.org/axis2/java/core/
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.apache.axis2
Version 1.6.3
Last update 27. June 2015
Organization not specified
URL http://axis.apache.org/axis2/java/core/
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
xapi-gwt-parent from group net.wetheinter (version 0.5)
This is the main aggregator for all gwt submodules.
All gwt-specific code resides here.
Submodules should avoid inheriting from each other unless necessary.
This goes for maven structure and gwt.xml structure.
The super module is where our jre emulation layer and super-source live;
all modules should inherit super, and a minimum of other modules.
Some modules, like injection, are fulfilling an api in the core module,
and should be accessed only through core service interfaces.
Other modules, like reflection, are capable of being standalone inherits,
but can benefit from core utilities like injection,
so, two (or more) .gwt.xml modules may be provided.
As XApi nears 1.0, all submodules will be routinely stitched together into
an uber-jar, in order to have a single jar with a single gwt module
that can provide all of the services at once.
Internal projects will never use the uber jar, to help maintain modularity,
but external projects that want to use more than one service
will certainly prefer inheriting one artifact, instead of twelve.
When distributed in uber-jar format, it will likely be necessary for
either the uber jar, or just xapi-gwt-api.jar to appear before gwt-dev
on your compile-time classpath. If using gwt-maven-plugin, the
gwtFirstOnClasspath option may become problematic. If so, we will provide
a forked gwt-plugin to make sure our compiler enhancements are included in
the build process.
There is also work going on to make a super-source-everything plugin,
which will use maven to find source files, and generate synthetic .gwt.xml
for you, as part of an effort to create a wholly unified programming
environment. In addition to java-to-javascript, we intend to compile
java-to-java and possibly other languages, like go; imagine implementing
gwt deferred binding to eliminate cross-platform differences between
server environments, or operating systems, or versions of a platform,
or anywhere else a core api needs to bind to multiple implementations,
depending on the runtime environment.
Group: net.wetheinter Artifact: xapi-gwt-parent
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact xapi-gwt-parent
Group net.wetheinter
Version 0.5
Last update 30. May 2015
Organization not specified
URL WeTheInter.net
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group net.wetheinter
Version 0.5
Last update 30. May 2015
Organization not specified
URL WeTheInter.net
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- 79
- 80
- 81
- 82
- 83
- 84
- 85
- 86
- 87
- 88
- 89
- 90
- 91
- 92
- 93
- 94
- 95
- 96
- 97
- 98
- 99
- 100
- 101
- 102
- 103
- 104
- 105
- 106
- 107
- 108
- 109
- 110
- 111
- 112
- 113
- 114
- 115
- 116
- 117
- 118
- 119
- 120
- 121
- 122
- 123
- 124
- 125
- 126
- 127
- 128
- 129
- 130
- 131
- 132
- 133
- 134
- 135
- 136
- 137
- 138
- 139
- 140
- 141
- 142
- 143
- 144
- 145
- 146
- 147
- 148
- 149
- 150
- 151
- 152
- 153
- 154
- 155
- 156
- 157
- 158
- 159
- 160
- 161
- 162
- 163
- 164
- 165
- 166
- 167
- 168
- 169
- 170
- 171
- 172
- 173
- 174
- 175
- 176
- 177
- 178
- 179
- 180
- 181
- 182
- 183
- 184
- 185
- 186
- 187
- 188
- 189
- 190
- 191
- 192
- 193
- 194
- 195
Page 195 from 195 (items total 1946)