Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

DataNucleus Access Platform 1.1.0.m1 (Rutherford branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News DataNucleus Access Platform 1.1.0.m1 (Rutherford branch)
# 1  
Old 09-23-2008
DataNucleus Access Platform 1.1.0.m1 (Rutherford branch)
DataNucleus Access Platform is a standards-compliant Java persistence product. It is fully compliant with the JDO1, JDO2, JDO2.1, and JPA1 Java standards. It also complies with the OGC Simple Feature Specification for persistence of geospatial Java types. It allows access to all popular RDBMSs available today, together with db4o, LDAP, NeoDatis, JSON, Excel documents, and XML databases. License: The Apache License 2.0 Changes:
The JDK requirement for 1.1 has been changed to JDK 1.5 or later. Support for JPQL bulk delete has been added for db4o, NeoDatis, Excel, XML, LDAP, and JSON datastores. RDBMS table existence checks have been improved. RDBMS datastore log startup has been cleaned up. Support for db4o has been raised to version 7.0 or later. Support for NucleusSQL querying for RDBMS has been removed. Support for (cast) and JPQL "" generic query compilation has been added. Several bugs have been fixed. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT SUNOS

deploytool

deploytool(1m)						    Application Server Utility						    deploytool(1m)

NAME

       deploytool - launches the deploytool utility to deploy, package, and edit your J2EE applications

SYNOPSIS

       deploytool [--help] [--userdir user_directory] [--configdir configuration_directory]

       Use  the  deploytool  utility to deploy and package your J2EE applications and components, create and edit J2EE deployment descriptors, and
       create and edit J2EE Application Server specific deployment descriptors. If the application is not J2EE compliant, an error message is dis-
       played.

       Only  one  session of the deploytool utility can run with a specific user directory. A lock file is created to ensure that only one utility
       session is running. A message is displayed if a lock file is detected.

OPTIONS

       --help			displays the arguments for launching the AssemblyTool.

       --userdir	       identifies the user directory. The default user directory is  .deploytool  under  your  home  directory.  Only  one
			       deploytool  session  can  be  running per user directory. A lock file is created under the user directory to ensure
			       that only one session of the deploytool is running. The deploytool utility uses this directory to store	configura-
			       tion information.

				 o  On Solaris, the default directory is at ~/.deploytool

       --configdir	       identifies the configuration directory. The configuration directory is where the asenv.conf file is located.

			       On Solaris the asenv.conf can be found at:

				 o  Bundled installation: /etc/appserver

				 o  Unbundled installation: default is /etc/opt/SUNWappserver7 or user	specified

				 o  Evaluation	installation:  AS_SERVER_INSTALL/config.  Where  AS_SERVER_INSTALL is the directory where you have
				    installed the Java 2 Platform, Enterprise Edition 1.4 Application Server Beta 2.

EXAMPLES

       Example 1: Using deploytool

       example% deploytool --userdir /myapplication --config_dir /myconfigdir

       Where --userdir specifies the destination directory, and -config_dir identifies the configuration directory.

SEE ALSO

       verifier(1M)

Sun Java System Application Server				    March 2004							    deploytool(1m)