Download JAR files tagged by element with all dependencies

JSefa (Java Simple exchange format api) is a simple library for stream-based serialization of java objects to XML, CSV, FLR or any other format and back again using an iterator-style interface independent of the serialization format. The mapping between java object types and types of the serialization format (e. g. xml complex element types) can be defined either by annotating the java classes or programmatically using a simple API. The current implementation supports XML, CSV and FLR - for XML it is based on JSR 173.

Class implementing a GSP algorithm for discovering sequential patterns in a sequential data set. The attribute identifying the distinct data sequences contained in the set can be determined by the respective option. Furthermore, the set of output results can be restricted by specifying one or more attributes that have to be contained in each element/itemset of a sequence. For further information see: Ramakrishnan Srikant, Rakesh Agrawal (1996). Mining Sequential Patterns: Generalizations and Performance Improvements.

Causes JAXB RI 2 XJC to generate a value constructor, where each embedded element is included as a constructor parameter. This is usedful when you want to make sure that you have handled every single possible embedded element. The plugin also generates a default (no argument) constructor, so existing code runs as expected.

JSefa (Java Simple exchange format api) is a simple library for stream-based serialization of java objects to XML, CSV, FLR or any other format and back again using an iterator-style interface independent of the serialization format. The mapping between java object types and types of the serialization format (e. g. xml complex element types) can be defined either by annotating the java classes or programmatically using a simple API. The current implementation supports XML, CSV and FLR - for XML it is based on JSR 173.

JSefa (Java Simple exchange format api) is a simple library for stream-based serialization of java objects to XML, CSV, FLR or any other format and back again using an iterator-style interface independent of the serialization format. The mapping between java object types and types of the serialization format (e. g. xml complex element types) can be defined either by annotating the java classes or programmatically using a simple API. The current implementation supports XML, CSV and FLR - for XML it is based on JSR 173.

JSefa (Java Simple exchange format api) is a simple library for stream-based serialization of java objects to XML, CSV, FLR or any other format and back again using an iterator-style interface independent of the serialization format. The mapping between java object types and types of the serialization format (e. g. xml complex element types) can be defined either by annotating the java classes or programmatically using a simple API. The current implementation supports XML, CSV and FLR - for XML it is based on JSR 173 for the standard version and XmlPull for the android version.

When generating XML schema from Java source code using the schemagen tool a common approach is to use the @XmlElementWrapper and @XmlElement annotations to handle schema generation for collections. However, when generating Java source from a schema using the xjc tool the resulting code is not created with these annotations. Instead, the generated Java source contains "injected" inner classes to accommodate the collection of elements contained within an element.

This is an XJC plugin to set default values in the XJC generated classes based on the default attribute to <xs:element>. Note that JAXB handles defaults for <xs:attribute> natively, so this plugin is not necessary for an attribute default. The plugin is particularly useful while generating Value Objects for a user interface from an XML schema. User interface tags such as the Struts HTML tags use reflection on bean properties to render themselves, so it is often useful to have a set of sensible defaults set in the Java Beans mapping to the user interface themselves.

The goal of this project is to connect architecture documentation and models while identifying missing or deviating elements (inconsistencies). An element can be any representable item of the model, like a component or a relation. To do so, we first create trace links and then make use of them and other information to identify inconsistencies. ArDoCo is actively developed by researchers of the Modelling for Continuous Software Engineering (MCSE) group of KASTEL - Institute of Information Security and Dependability at the KIT.

EnOS Device And Asset API pojo 0.2.14-SNAPSHOT ota api pojo and event 0.2.20-SNAPSHOT The Response objects returned by GetEvent and SearchEvent queries are added (including: outputData, eventName, outputNames fields) 0.2.21-SNAPSHOT Increase the internationalization of the four-element description field of the model 0.2.22-SNAPSHOT add some pojo class for private api 0.2.23-SNAPSHOT model-service open api的接口中thingModel增加category模型类型字段 0.2.24-SNAPSHOT 部分search接口增加realTime字段 0.2.25-SNAPSHOT firmware add tag function 0.2.27-SNAPSHOT add max and min fields 0.2.28-SNAPSHOT asset tree api for amc/city infra 0.2.29-SNAPSHOT fix thingModel enableMeasurepointValidate 0.2.30-SNAPSHOT enhancement of search model and update asset and alert engine 增加告警规则sdk 0.2.31-SNAPSHOT move asset node 2.4.0-SNAPSHOT upgrade to 2.4 for support DCM 2.4GA 2.4.1-SNAPSHOT service parameter supports "Required" and "Default Value" fields 2.4.2-SNAPSHOT upgrade to 2.4 for support DCM 2.4GA jar 升级 2.4.3-SNAPSHOT add alert-engine v2.5 alertRule openAPI