Forum :: openmamba » Forum: news

Forum :: openmamba » Forum: news - Recent Posts http://forum.openmamba.org/forum.php?id=6 openmamba forum en Thu, 23 May 2013 01:21:55 +0000 http://bbpress.org/?v=1.0.3 <![CDATA[Search]]> q http://forum.openmamba.org/search.php silvan on "Release: openmamba livecd snapshot for x86_64 (installable)" http://forum.openmamba.org/topic.php?id=2669#post-6890 Thu, 07 Feb 2013 12:46:26 +0000 silvan 6890@http://forum.openmamba.org/ The first 64 bit version of <code>openmamba livecd</code> is <a href="http://www.openmamba.org/distribution/announcements.html?distrelease=devel&medium=livecd&version=20130207">available</a>. The live system is based on KDE 4 and provides all the features of the classic 32 bit version including the tool to install the system on the PC. The porting of the second-stage installed additional components is yet to be completed, but those who want to install 64 bit openmamba today will be able to add the missing components later as soon as they become available. To boot and install a live openmamba medium you need to follow one of the following procedures: <ul> <li>download the ISO image and burn into a CD/DVD medium </li> <li>prepare a USB pendrive starting from an openmamba system: <ul> <li>using the <code>usbinstall</code> tool that is available in the system applications menu </li> <li>installing the modified <code>unetbootin</code> package (*) through <code>Add/Remove software packages...</code> </li> </ul> </li> <li>prepare a bootable USB pendrive from any Linux system by following the instructions found in the <a href="http://www.openmamba.org/distribution/media/bootusb.html">openmamba bootusb archive</a> page</li> </ul> (*) support for openmamba in all <code>unetbootin</code> Linux version will be available when the <a href="https://bugs.launchpad.net/unetbootin/+bug/1114339">patch I have submitted</a> will be accepted and integrated upstream. silvan on "Release: openmamba milestone2 2.0pre7 "LinuxDay Preview"" http://forum.openmamba.org/topic.php?id=625#post-4187 Sat, 22 Oct 2011 11:45:01 +0000 silvan 4187@http://forum.openmamba.org/ The ISO images and archives of the seventh openmamba milestone2 pre-release are available for download. - LibreOffice 3.4 - Firefox 7 - support for 4GB+ RAM system extended also to livecd-light version for server installations - cdrtool -> cdrkit switch - installation and system bugfixes The downloadable media are: - livedvd: complete and recommended for most installations, kernel for 4GB+ RAM systems can be selected at boot - livecd: base system release limited to fit into a CD, the installation of the additional components in the livedvd version can be made after installation through a network connection - livecd-gnome: GNOME desktop environment version for CD medium. Additional components can be installed from network after the installation. The system is stable and usable but the work on GNOME desktop is still in progress and any problem seen and reported will be rapidly fixed through system updates - livecd-light: light version for optimized server installations and old for hardware with limited resources - sdk: ARM EABI compatible root filesystem with the LXDE graphical environment. Suitable for the installation on ARM based mobile and embedded devices - bootusb: auxiliary archive for booting and installing live media through a USB storage device. All targets support x86 compatible archs (with the exception of sdk) and are available in english, italian and spanish languages. The ISO images can be burnt on CD/DVD media or installed in a USB pendrive and used to boot a live system and install it. A detailed list of changes can be found on these pages: <a href="http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog" rel="nofollow">http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog</a> <a href="http://www.openmamba.org/distribution/distromatic.html?tag=milestone2-updates&changelog" rel="nofollow">http://www.openmamba.org/distribution/distromatic.html?tag=milestone2-updates&changelog</a> and on the git repository: <a href="http://git.openmamba.org" rel="nofollow">http://git.openmamba.org</a> Thanks to all the people who contributed in different ways to the development of this new release of openmamba. Silvan silvan on "Release: openmamba milestone2 2.0pre6" http://forum.openmamba.org/topic.php?id=618#post-4146 Sat, 08 Oct 2011 18:22:52 +0000 silvan 4146@http://forum.openmamba.org/ The ISO images and archives of the sixth openmamba milestone2 pre-release are available for download. This new release adds the following new features: - Linux kernel 3.0.4 - support for 4GB+ RAM system (livedvd version) - live-gnome: new stable live CD based on the Gnome desktop environment, version 2.32. 3.x will be optionally available as an upgrade when ready - live-light: new stable live CD based on the LXDE environment - USB 3.0 support for the USB live version of openmamba - KDE 4.6.5 (KDE 4.7.x will be available as an update as soon as the changes and tests for painless user upgrades will be completed) - Chromium is the new default and recommended browser - added support for the open source 'nouveau' video driver for system having an NVIDIA graphical chipset, as well as X.org updates with all other graphic drivers The downloadable media are: - livedvd: complete and recommended for most installations, kernel for 4GB+ RAM systems can be selected at boot - livecd: base system release limited to fit into a CD, the installation of the additional components in the livedvd version can be made after installation through a network connection - livecd-gnome: GNOME desktop environment version for CD medium. Additional components can be installed from network after the installation. The system is stable and usable but the work on GNOME desktop is still in progress and any problem seen and reported will be rapidly fixed through system updates - livecd-light: light version for optimized server installations and old for hardware with limited resources - sdk: ARM EABI compatible root filesystem with the LXDE graphical environment. Suitable for the installation on ARM based mobile and embedded devices - bootusb: auxiliary archive for booting and installing live media through a USB storage device. All targets support x86 compatible archs (with the exception of sdk) and are available in english, italian and spanish languages. The ISO images can be burnt on CD/DVD media or installed in a USB pendrive and used to boot a live system and install it. Please note that the livegames target is no longer available as a stable release but is still available as a weekly development snapshot. A long and detailed list of changes can be found on these pages: <a href="http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog" rel="nofollow">http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog</a> <a href="http://www.openmamba.org/distribution/distromatic.html?tag=milestone2-updates&changelog" rel="nofollow">http://www.openmamba.org/distribution/distromatic.html?tag=milestone2-updates&changelog</a> and on the new git repository: <a href="http://git.openmamba.org" rel="nofollow">http://git.openmamba.org</a> Thanks to all the people who contributed in different ways to the development of this new release of openmamba. Silvan silvan on "Release: openmamba milestone2 2.0pre4" http://forum.openmamba.org/topic.php?id=558#post-3803 Mon, 04 Apr 2011 20:22:28 +0000 silvan 3803@http://forum.openmamba.org/ The ISO images of the fouth pre-release of openmamba milestone 2 are available for download. This new release adds the following new features: - "longterm" 2.6.35.11 Linux kernel - Linux kernel 2.6.37.6 can now be installed optionally by enabling the new milestone2-kernel channel - KDE desktop environment 4.5.5 - network connections management is now based on NetworkManager in order to provide an integrated and simple solution for ethernet, wireless, mobile broadband, ADSL (PPPoE) and more - 500+ software components updated openmamba is available for PC (x86 compatibles) in english, italian and spanish languages. It is distributed as ISO images in livecd, livedvd and livegames flavours and can be freely downloaded from <a href="http://www.openmamba.org" rel="nofollow">http://www.openmamba.org</a>. The ISO images can be burnt on CD/DVD media or installed in a USB pendrive and used to boot a live system and install it. A long and detailed list of changes is available on this page: <a href="http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog" rel="nofollow">http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog</a> I also would like to announce the availability of a couple of new weekly snapshot targets: - openmamba SDK: a root filesystem that can be used as a development environment with many recent devices that are based on ARM compatible processors (tablets, smartphones, smartbooks and plug computers) which also provides a LXDE based graphical environment and NetworkManager, rpm and smart to allow the installation of the 1600+ openmamba packages that have been ported at the date (see <a href="http://www.openmamba.org/distribution/distromatic.html?tag=devel&arch=arm" rel="nofollow">http://www.openmamba.org/distribution/distromatic.html?tag=devel&arch=arm</a> for the full list) - openmamba livecd-light: a light openmamba release based on the LXDE graphical environment intended for use with computers which have less than 512MB of RAM openmamba head maintainer wants to say thanks to all the people who contributed in different ways to the development of this new release of openmamba. Beta testers and developers are welcome to help improve this project and can join by subscribing and writing to the development Lists (<a href="http://www.openmamba.org/lists/" rel="nofollow">http://www.openmamba.org/lists/</a>) or in the Forum (<a href="http://forum.openmamba.org)" rel="nofollow">http://forum.openmamba.org)</a>. Note: we are aware of download problems from our main server and a migration to a new more functional and performant infrastructure is due within the next weeks. Meanwhile we recommend people having download problems to use a download manager with resume capability and to make use of the information from page <a href="http://www.openmamba.org/distribution/download.html" rel="nofollow">http://www.openmamba.org/distribution/download.html</a> to perform a MD5 check of the downloaded files. Silvan silvan on "Upgrade: openmamba milestone2 2.0pre4" http://forum.openmamba.org/topic.php?id=554#post-3795 Mon, 07 Mar 2011 00:04:07 +0000 silvan 3795@http://forum.openmamba.org/ Users of openmamba milestone2 will get an upgrade to the fourth pre-release with the following main new features: - "longterm" 2.6.35.11 kernel - KDE desktop environment 4.5.5 - network connections management is now based on NetworkManager in order to provide an integrated and simple solution for ethernet, wireless, mobile broadband, ADSL (PPPoE) and more - 400+ software components updated - initial support for the "light" LXDE desktop environment, suitable for computers with limited CPU and memory resources IMPORTANT NOTES: - upon upgrade completion the system must be rebooted - network settings like password for Wireless connection, static IP and DNS and any other custom settings have to be reconfigured with the new interface - in order to decrease the risk of an upgrade failure due to the new kernel it is now possible to start the system using the previous kernel (2.6.33), available as a choice in the boot menu - in order to use the LXDE environment the "lxde" package must be installed, then logout from KDE and login again after selecting "lxde" session type Within a few days live installation media will be available and the official release will be published. Wishing you a pleasant upgrade, Silvan silvan on "Maintenance: openmamba server shutdown from december, 18 2010 at 9.00" http://forum.openmamba.org/topic.php?id=543#post-3770 Fri, 17 Dec 2010 12:45:02 +0000 silvan 3770@http://forum.openmamba.org/ Due to a maintenance task planned by our ISP, openmamba server will not be reachable from 9.00 of saturday 12/18/2010 till the end of operations. Silvan silvan on "Release: openmamba milestone2 2.0pre3" http://forum.openmamba.org/topic.php?id=539#post-3762 Sat, 27 Nov 2010 03:49:14 +0000 silvan 3762@http://forum.openmamba.org/ There are no preset passwords in openmamba, normally when this happens it's because of a bug in desktop environment startup. You can press CTRL-ALT-F2 to access a console where you can set a password but that won't fix the problem. The cause of the problem might be visible in /root/.xsession-errors or you can generate a detailed report by running the command openmamba-makereport and then send the output file to <a href="mailto:reports@openmamba.org">reports@openmamba.org</a> for us to examine it. Regards. jerrybee on "Release: openmamba milestone2 2.0pre3" http://forum.openmamba.org/topic.php?id=539#post-3761 Sat, 27 Nov 2010 03:00:13 +0000 jerrybee 3761@http://forum.openmamba.org/ I've just downloaded the latest iso file and burned it to a DVD. I booted the DVD, hoping to install openmamba onto a hard drive. But the process ended with a text screen asking me for a username and password, which, of course, I don't have. Please supply the default username and password so that I can proceed with the installation. I tried a username of "admin", and it seemed to accept that. But when then asked for a password, I tried all I could think of and it accepted none of them. silvan on "Release: openmamba milestone2 2.0pre3" http://forum.openmamba.org/topic.php?id=539#post-3760 Fri, 26 Nov 2010 19:08:02 +0000 silvan 3760@http://forum.openmamba.org/ The third pre-release of openmamba milestone 2 is out with over 1000 software updates. The system is based on Linux kernel 2.6.33.7 and provides a modern desktop environment that includes, among the others, KDE (4.5.3), OpenOffice (3.2), Firefox (3.6.12), Amarok (2.3.2). openmamba is available for PC (x86 compatibles) in english, italian and spanish languages, it is distributed as ISO images in livecd, livedvd and livegames flavours and can be freely downloaded from <a href="http://www.openmamba.org" rel="nofollow">http://www.openmamba.org</a>. The ISO image can be burned on CD/DVD media or installed in a USB pendrive and used to boot a live system and install it. Users of previous 2.0 pre-releases will receive a consistent upgrade from network to get aligned with the new release. In case of problems it is recommended to write in the Forum at <a href="http://forum.openmamba.org" rel="nofollow">http://forum.openmamba.org</a> or to use the Bug Tracking page at <a href="http://bugs.openmamba.org" rel="nofollow">http://bugs.openmamba.org</a> The full list of changes is available on this page: <a href="http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog" rel="nofollow">http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog</a> Thanks to all the people who contributed in different ways to the development of this new release of openmamba. Beta testers and developers are welcome and can subscribe and write to the development Lists (<a href="http://www.openmamba.org/lists/" rel="nofollow">http://www.openmamba.org/lists/</a>) or in the Forum (<a href="http://forum.openmamba.org)" rel="nofollow">http://forum.openmamba.org)</a>. Silvan silvan on "openmamba milestone2 pre-release 3" http://forum.openmamba.org/topic.php?id=536#post-3752 Thu, 18 Nov 2010 13:35:44 +0000 silvan 3752@http://forum.openmamba.org/ This morning repository sync operations for version 2.0 pre-release3 have been activated. openmamba milestone2 users will get a consistent update that will align the system with the most recent software packages and features. In case of problems it is possibile to use the usual channels to communicate with the developers. Installation and live media and the official announcement will be made in the next days. Silvan aleprova on "Release: openmamba milestone2 2.0pre2" http://forum.openmamba.org/topic.php?id=518#post-3705 Tue, 07 Sep 2010 15:35:05 +0000 aleprova 3705@http://forum.openmamba.org/ ORM OBJECT RELATIONAL MAPPING It mapping between the objects and the database.ORM, in essence, works by (reversibly) transforming data from one representation to another. CRUD (create, read, update, delete) operations - Dati persistent - Operation:ORM OBJECT RELATIONAL MAPPING It mapping between the objects and the database.ORM, in essence, works by (reversibly) transforming data from one representation to another. CRUD (create, read, update, delete) operations - Dati persistent - Operation: ■ Storage, organization, and retrieval of structured data ■ Concurrency and data integrity ■ Data sharing - Granularità If one application holds a lock on a database object, another application might not be able to access that object. For this reason, row-level locks, which minimize the amount of data that is locked and therefore inaccessible, are better for maximum concurrency than block-level, data partition-level or table-level locks. However, locks require storage and processing time, so a single table lock minimizes lock overhead. The LOCKSIZE clause of the ALTER TABLE statement specifies the scope (granularity) of locks at the row, data partition, block, or table level. By default, row locks are used. Only S (Shared) and X (Exclusive) locks are requested by these defined table locks. The ALTER TABLE statement LOCKSIZE ROW clause does not prevent normal lock escalation from occurring. A permanent table lock defined by the ALTER TABLE statement might be preferable to a single-transaction table lock using LOCK TABLE statement in the following cases: - The table is read-only, and will always need only S locks. Other users can also obtain S locks on the table. - The table is usually accessed by read-only applications, but is sometimes accessed by a single user for brief maintenance, and that user requires an X lock. While the maintenance program runs, the read-only applications are locked out, but in other circumstances, read-only applications can access the table concurrently with a minimum of locking overhead. PAG 52 Cap2. The persistence consists in storing data in a relational database using SQL. Hibernate applications define persistent classes that are “mapped” to database tables. package hello; public class Message { private Long id; private String text; private Message nextMessage; private Message() { } public Message(String text) { this.text = text; } public Long getId() { return id; } private void setId(Long id) { this.id = id; } public String getText() { return text; } } public void setText(String text) { this.text = text; } public Message getNextMessage() { return nextMessage; } public void setNextMessage(Message nextMessage) { this.nextMessage = nextMessage; } } It prints "Hello World" to the console. Message message = new Message("Hello World"); System.out.println( message.getText() ); Our persistent class can be used in any execution context at all. Of course, you came here to see Hibernate itself, so let’s save a new Message to the database: Session session = getSessionFactory().openSession(); Transaction tx = session.beginTransaction(); Message message = new Message("Hello World"); session.save(message); tx.commit(); session.close(); This code calls the Hibernate Session and Transaction interfaces. It results in the execution of something similar to the following SQL: insert into MESSAGES (MESSAGE_ID, MESSAGE_TEXT, NEXT_MESSAGE_ID) values (1, 'Hello World', null) We can also assume that the MESSAGES table already exists. Session newSession = getSessionFactory().openSession(); Transaction newTransaction = newSession.beginTransaction(); List messages = newSession.find("from Message as m order by m.text asc"); // HIBERNATE QUERY: select m.MESSAGE_ID, m.MESSAGE_TEXT, m.NEXT_MESSAGE_ID from MESSAGES m order by m.MESSAGE_TEXT asc // System.out.println( messages.size() + " message(s) found:" ); for ( Iterator iter = messages.iterator(); iter.hasNext(); ) { Message message = (Message) iter.next(); System.out.println( message.getText() ); } newTransaction.commit(); newSession.close(); All SQL is generated at runtime. XML MAPPING HIBERNATE CODE <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD//EN" "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd"> <hibernate-mapping> <class name="hello.Message" table="MESSAGES"> <id name="id" column="MESSAGE_ID"> <generator class="increment"/> </id> <property name="text" column="MESSAGE_TEXT"/> <many-to-one name="nextMessage" cascade="all" column="NEXT_MESSAGE_ID"/> </class> </hibernate-mapping> The Hibernate interfaces may be approximately classified as follows: ■ Interfaces called by applications to perform basic CRUD and querying operations. These interfaces are the main point of dependency of application business/control logic on Hibernate. They include Session, Transaction, and Query. ■ Interfaces called by application infrastructure code to configure Hibernate, most importantly the Configuration class. ■ Callback interfaces that allow the application to react to events occurring inside Hibernate, such as Interceptor, Lifecycle, and Validatable. ■ Interfaces that allow extension of Hibernate’s powerful mapping functionality, such as UserType, CompositeUserType, and IdentifierGenerator. These interfaces are implemented by application infrastructure code (if necessary). • SESSION The Session interface is the primary interface used by Hibernate applications. Hibernate sessions are not thread safe and should by design be used by only one thread at a time. • SESSION FACTORY It’s intended to be shared among many application threads. There is typically a single SessionFactory for the whole application. However, if your application accesses multiple databases using Hibernate, you’ll need a SessionFactory for each database. The SessionFactory caches generated SQL statements and other mapping metadata that Hibernate uses at runtime. The following code starts Hibernate: Configuration cfg = new Configuration(); cfg.addResource("hello/Message.hbm.xml"); cfg.setProperties( System.getProperties() ); SessionFactory sessions = cfg.buildSessionFactory(); The location of the mapping file, Message.hbm.xml, is relative to the root of the application classpath. If we had another persistent class, it would be defined in its own mapping file. You can load multiple mapping files by calling addResource() as often as you have to. Alternatively, if you follow the convention just described, you can use the method addClass(), passing a persistent class as the parameter: SessionFactory sessions = new Configuration() .addClass(org.hibernate.auction.model.Item.class) .addClass(org.hibernate.auction.model.Category.class) .addClass(org.hibernate.auction.model.Bid.class) .setProperties( System.getProperties() ) .buildSessionFactory(); If another SessionFactory is needed—if there are multiple databases, for example—you repeat the process. To specify configuration options, you may use any of the following techniques: ■ Used except for quick testing and prototypes: ■ Pass an instance of java.util.Properties to Configuration.setProperties(). ■ Set system properties using java -Dproperty=value. ■ Place a file called hibernate.properties in the classpath. ■ Include <property> elements in hibernate.cfg.xml in the classpath. • CONFIGURATION The Configuration object is used to configure and bootstrap Hibernate. The application uses a Configuration instance to specify the location of mapping documents and Hibernate-specific properties and then create the SessionFactory. Configuration in non-managed environment: Java applications should use a pool of JDBC connections. There are three reasons for using a pool: ■ Acquiring a new connection is expensive. ■ Maintaining many idle connections is expensive. ■ Creating prepared statements is also expensive for some drivers. hibernate.connection.driver_class = org.postgresql.Driver hibernate.connection.url = jdbc:postgresql://localhost/auctiondb hibernate.connection.username = auctionuser hibernate.connection.password = secret hibernate.dialect = net.sf.hibernate.dialect.PostgreSQLDialect hibernate.c3p0.min_size=5 hibernate.c3p0.max_size=20 hibernate.c3p0.timeout=300 hibernate.c3p0.max_statements=50 hibernate.c3p0.idle_test_period=3000 Specifying properties of the form hibernate.c3p0.* selects C3P0 as Hibernate’s connection pool. Configuration managed environment: A managed environment handles certain cross-cutting concerns, such as application security (authorization and authentication), connection pooling, and transaction management. hibernate.connection.datasource = java:/comp/env/jdbc/AuctionDB hibernate.transaction.factory_class = \ net.sf.hibernate.transaction.JTATransactionFactory hibernate.transaction.manager_lookup_class = \ net.sf.hibernate.transaction.JBossTransactionManagerLookup hibernate.dialect = net.sf.hibernate.dialect.PostgreSQLDialect XML-based Configuration: The hibernate.cfg.xml file may also specify the location of mapping documents. ?xml version='1.0'encoding='utf-8'?> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD//EN" "http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd"> <hibernate-configuration> <session-factory name="java:/hibernate/HibernateFactory"> <property name="show_sql">true</property> <property name="connection.datasource"> java:/comp/env/jdbc/AuctionDB</property> <property name="dialect"> net.sf.hibernate.dialect.PostgreSQLDialect </property> <property name="transaction.manager_lookup_class"> net.sf.hibernate.transaction.JBossTransactionManagerLookup </property> <mapping resource="auction/Item.hbm.xml"/> <mapping resource="auction/Category.hbm.xml"/> <mapping resource="auction/Bid.hbm.xml"/> </session-factory> </hibernate-configuration> Now you can initialize Hibernate using: SessionFactory sessions = new Configuration() .configure().buildSessionFactory(); When configure() was called, Hibernate searched for a file named hibernate.cfg.xml in the classpath. If you wish to use a different filename or have Hibernate look in a subdirectory, you must pass a path to the configure() method: SessionFactory sessions = new Configuration().configure("/hibernate-config/auction.cfg.xml").buildSessionFactory(); Using an XML configuration file is certainly more comfortable than a properties file or even programmatic property configuration. Logging When you find yourself troubleshooting a difficult problem, you need to be able to see exactly what’s going on inside Hibernate. You can use logging to get a view of Hibernate’s internals. Hibernate logs all interesting events using Apache commons-logging, a thin abstraction layer that directs output to either Apache log4j (if you put log4j.jar in your classpath). JNDI è acronimo di Java Naming and Directory Interface. All’interno di un Application Server (e anche in applicazioni non necessariamente web). Tutte le operazioni fondamentali che si possono compiere in un Application Server possono essere rimappate utilizzando JNDI. Elenchiamo alcune delle principali operazioni che normalmente vengono compiute: Transazioni (UserTransaction & TransactionManager) Pool di Connessioni ai Database (Datasource) Pool di Connessioni Transazionali ai Database (XADatasource). Con JNDI si possono rimappare tutti i percorsi fisici a cui è necessario puntare, in una sorta di tabella chiave-valore, una specie di HashTable, che rende facilmente configurabile, e quindi portabile, la nostra applicazione. Per maggiori informazioni ed esempi vi invito caldamente a visitare i link correlati. In particolare nel primo link è mostrato come accedere a JNDI in un Application Server Bea Weblogic. Finally, you have the hibernate.properties, hibernate.cfg.xml, and log4j.properties configuration files. Or JMX: JAVA MANAGEMENT EXTENSION The JMX specification defines the following components: ■ The JMX MBean—A reusable component (usually infrastructural) that exposes an interface for management (administration) ■ The JMX container—Mediates generic access (local or remote) to the MBean ■ The (usually generic) JMX client—May be used to administer any MBean via the JMX container An application server with support for JMX (such as JBoss) acts as a JMX container and allows an MBean to be configured and initialized as part of the application server startup process. <server> <mbean code="net.sf.hibernate.jmx.HibernateService" name="jboss.jca:service=HibernateFactory, name=HibernateFactory"> <depends>jboss.jca:service=RARDeployer</depends> <depends>jboss.jca:service=LocalTxCM, name=DataSource</depends> <attribute name="MapResources"> auction/Item.hbm.xml, auction/Bid.hbm.xml </attribute> <attribute name="JndiName"> java:/hibernate/HibernateFactory </attribute> <attribute name="Datasource"> java:/comp/env/jdbc/AuctionDB </attribute> <attribute name="Dialect"> net.sf.hibernate.dialect.PostgreSQLDialect </attribute> <attribute name="TransactionStrategy"> net.sf.hibernate.transaction.JTATransactionFactory </attribute> <attribute name="TransactionManagerLookupStrategy"> net.sf.hibernate.transaction.JBossTransactionManagerLookup </attribute> <attribute name="UserTransactionName"> java:/UserTransaction </attribute> </mbean> </server> • TRANSICTION The Transaction interface is an optional API. Hibernate applications may choose not to use this interface, instead managing transactions in their own infrastructure code. A Transaction abstracts application code from the underlying transaction implementation allowing the application to control transaction boundaries via a consistent API. • CALLBACK Callback interfaces allow the application to receive a notification when something interesting happens to an object—for example, when an object is loaded, saved, or deleted. Hibernate applications don’t need to implement these callbacks, but they’re useful for implementing certain kinds of generic functionality, such as creating audit records. The Lifecycle and Validatable interfaces allow a persistent object to react to events relating to its own persistence lifecycle. • TYPE A Hibernate Type object maps a Java type to a database column type (actually, the type may span multiple columns). All persistent properties of persistent classes, including associations, have a corresponding Hibernate type. This design makes Hibernate extremely flexible and extensible. • EXTENSION POINTS: ■ Primary key generation (IdentifierGenerator interface) ■ SQL dialect support (Dialect abstract class) ////Serve e a specificare quale database stiamo utilizzando oracledialect; mysqldialect ecc... ■ Caching strategies (Cache and CacheProvider interfaces) ■ JDBC connection management (ConnectionProvider interface) ■ Transaction management (TransactionFactory, Transaction, and TransactionManagerLookup interfaces) ■ ORM strategies (ClassPersister interface hierarchy) ■ Property access strategies (PropertyAccessor interface) ■ Proxy creation (ProxyFactory interface) <a href="http://www.roseindia.net/hibernate/firstexample.shtml" rel="nofollow">http://www.roseindia.net/hibernate/firstexample.shtml</a> ARCHITETTURA: Session, Transaction, and Query (Create and compile a persistent class (the initial Message, for example), copy Hibernate and its required libraries to the classpath together with a hibernate.properties file, and build a SessionFactory. The next section covers advanced Hibernate configuration options. Some of them are recommended, such as logging executed SQL statements for debugging or using the convenient XML configuration file instead of plain properties.) Cap3. You shouldn’t put code that addresses these cross-cutting concerns in the classes that implement the domain model. When these concerns start to appear in the domain model classes, we call this an example of leakage of concerns. The EJB standard tries to solve the problem of leaky concerns. Indeed, if we implemented our domain model using entity beans, the container would take care of some concerns for us (or at least externalize those concerns to the deployment descriptor). The EJB container prevents leakage of certain cross-cutting concerns using interception. An EJB is a managed component, always executed inside the EJB container. The container intercepts calls to your beans and executes its own functionality. Hibernate isn’t an application server, and it doesn’t try to implement all the cross-cutting concerns mentioned in the EJB specification. Hibernate is a solution for just one of these concerns: persistence. If you require declarative security and transaction management, you should still access your domain model via a session bean, taking advantage of the EJB container’s implementation of these concerns. Hibernate is commonly used together with the well-known session façade J2EE pattern. Much discussion has gone into the topic of persistence, and both Hibernate and EJB entity beans take care of that concern. However, Hibernate offers something that entity beans don’t: transparent persistence. Our Item class, for example, will not have any code-level dependency to any Hibernate API. Furthermore: ■ Hibernate doesn’t require that any special superclasses or interfaces be inherited or implemented by persistent classes. Nor are any special classes used to implement properties or associations. Thus, transparent persistence improves code readability, as you’ll soon see. ■ Persistent classes may be reused outside the context of persistence, in unit tests or in the user interface (UI) tier, for example. Testability is a basic requirement for applications with rich domain models. ■ In a system with transparent persistence, objects aren’t aware of the underlying data store; they need not even be aware that they are being persisted or retrieved. Persistence concerns are externalized to a generic persistence manager interface —in the case of Hibernate, the Session and Query interfaces. By this definition of transparent persistence, you see that certain non-automated persistence layers are transparent (for example, the DAO pattern) because they decouple the persistence-related code with abstract programming interfaces. The programming model we’ll introduce is a non-intrusive mix of JavaBean specification details, POJO best practices, and Hibernate requirements. A POJO declares business methods, which define behavior, and properties, which represent state. Some properties represent associations to other POJOs. It’s an implementation of the User entity of our domain model. public class User implements Serializable { private String username; private Address address; public User() { } public String getUsername() { return username; } public void setUsername(String username) { this.username = username; } public Address getAddress() { return address; public void setAddress(Address address) { this.address = address; } ... } } You use properties to express associations between POJO classes, and you use accessor methods to navigate the object graph at runtime. scaffolding code:codice di “collegamento”(ER model). For example let’s implement the scaffolding code for the one-to-many self-association of Category: public class Category implements Serializable { private String name; private Category parentCategory; private Set childCategories = new HashSet(); public Category() { } ... } To allow bidirectional navigation of the association, we require two attributes. The parentCategory attribute implements the single-valued end of the association and is declared to be of type Category. The many-valued end, implemented by the child-Categories attribute, must be of collection type. We choose a Set, since duplicates are disallowed, and initialize the instance variable to a new instance of HashSet. We now have some private instance variables but no public interface to allow access from business code or property management by Hibernate. Let’s add some accessor methods to the Category class: public String getName() { return name; } public void setName(String name) { this.name = name; } public Set getChildCategories() { return childCategories; } public void setChildCategories(Set childCategories) { this.childCategories = childCategories; } public Category getParentCategory() { return parentCategory; } public void setParentCategory(Category parentCategory) { this.parentCategory = parentCategory; } Again, these accessor methods need to be declared public only if they’re part of the external interface of the persistent class, the public interface used by the application logic. The basic procedure for adding a child Category to a parent Category looks like this: Category aParent = new Category(); Category aChild = new Category(); aChild.setParentCategory(aParent); aParent.getChildCategories().add(aChild); ■ The parentCategory of the child must be set, effectively breaking the association between the child and its old parent (there can be only one parent for any child). ■ The child must be added to the child Categories collection of the new parent. Programming models like EJB entity beans muddle this behavior by introducing container-managed relationships. The container automatically changes the other side of a relationship if one side is modified by the application. Hibernate doesn’t care if property access methods are private or public, so we can focus on good API design. One of the reasons we like to use JavaBeans-style access methods is that they provide encapsulation: The hidden internal implementation of a property can be changed without any changes to the public interface. This allows you to abstract the internal data structure of a class—the instance variables—from the design of the database. For example, if your database stores a name of the user as a single NAME column, but your User class has first name and last name properties, you can add the following persistent name property to your class: Public class User { private String firstname; private String lastname; ... public String getName() { return firstname + ' ' + lastname; } public void setName(String name) { StringTokenizer t = new StringTokenizer(name); firstname = t.nextToken(); lastname = t.nextToken(); ) ... } Later, you’ll see that a Hibernate custom type is probably a better way to handle many of these kinds of situations. Hibernate will later use our accessor methods to populate the state of an object when loading the object from the database. Hibernate result in unnecessary SQL UPDATEs. This kind of code should almost always be avoided in accessor methods: public void setNames(List namesList) { names = (String[]) namesList.toArray(); } public List getNames() { return Arrays.asList(names); } METADATA ORM tools require a metadata format for the application to specify the mapping between classes and tables, properties and columns, associations and foreign keys, Java types and SQL types. This information is called the object/relational mapping metadata. It defines the transformation between the different data type systems and relationship representations. XML mapping: (DTD = document type definition) <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD//EN" "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd"> <hibernate-mapping> <class name="org.hibernate.auction.model.Category" table="CATEGORY"> <id name="id" column="CATEGORY_ID" type="long"> <generator class="native"/> </id> <property name="name" column="NAME" type="string"/> </class> </hibernate-mapping> If you omit the type, Hibernate will use the Hibernate type string by default. The <property> element (and especially the <column> element) also defines certain attributes that apply mainly to automatic database schema generation. <property name="initialPrice" column="INITIAL_PRICE" not-null="true"/> <property name="totalIncludingTax" formula="TOTAL + TAX_RATE * TOTAL" type="big_decimal"/> The given SQL formula is evaluated every time the entity is retrieved from the database. The property doesn’t have a column attribute (or sub-element) and appears in an SQL SELECTs. Formulas may refer to columns of the database table, call SQL functions, and include SQL subselects. This example, mapping a derived property of item, uses a correlated subselect to calculate the average amount of all bids for an item: <property name="averageBidAmount" formula="( select AVG(b.AMOUNT) from BID b ➾where b.ITEM_ID = ITEM_ID )" type="big_decimal"/> access="field" Access to properties via accessor methods is considered best practice by the Hibernate community. It provides an extra level of abstraction between the Java domain model and the data model. insert="false" update="false" The property name of the JavaBean is therefore immutable and can be read from the database but not modified in any way. If the complete class is immutable, set the immutable="false" in the class mapping. The dynamic-update attribute tells Hibernate whether to include unmodified properties in the SQL UPDATE: <class name="org.hibernate.auction.model.User" dynamic-insert="true" dynamic-update="true"> ... </class> These are both class-level settings. Enabling either of these settings will cause Hibernate to generate some SQL at runtime, instead of using the SQL cached at startup time. SQL schemas You can specify a default schema using the hibernate.default_schema configuration option. Alternatively, you can specify a schema in the mapping document. A schema may be specified for a particular class or collection mapping: <hibernate-mapping> <class name="org.hibernate.auction.model.Category" table="CATEGORY" schema="AUCTION"> ... </class> </hibernate-mapping> It can even be declared for the whole document: <hibernate-mapping default-schema="AUCTION"> .. </hibernate-mapping> This isn’t the only thing the root <hibernate-mapping> element is useful for. ( <a href="http://www.mokabyte.it/2005/11/hibernate.htm" rel="nofollow">http://www.mokabyte.it/2005/11/hibernate.htm</a> tag of XDOCLET: <a href="http://xdoclet.sourceforge.net/xdoclet/tags/hibernate-tags.html#@hibernate_property__0__1_" rel="nofollow">http://xdoclet.sourceforge.net/xdoclet/tags/hibernate-tags.html#@hibernate_property__0__1_</a> using a script build.xml of Ant ) using declaration type ... // Define a new column for the USER table Column column = new Column(); column.setType(Hibernate.STRING); column.setName("ETA"); column.setNullable(false); column.setUnique(true); userMapping.getTable().addColumn(column); // Wrap the column in a Value SimpleValue value = new SimpleValue(); value.setTable( userMapping.getTable() ); value.addColumn(column); value.setType(Hibernate.STRING); // Define a new property of the User class Property prop = new Property(); prop.setValue(value); prop.setName("eta"); userMapping.addProperty(prop); // Build a new session factory, using the new mapping SessionFactory sf = cfg.buildSessionFactory(); ■ Object identity—Objects are identical if they occupy the same memory location in the JVM. This can be checked by using the == operator. ■ Object equality—Objects are equal if they have the same value, as defined by the equals(Object o) method. Classes that don’t explicitly override this method inherit the implementation defined by java.lang.Object, which compares object identity. ■ Database identity—Objects stored in a relational database are identical if they represent the same row or, equivalently, share the same table and primary key value. Hibernate has several built-in identifier generation strategies: Tab Pag.114 <component name="homeAddress" class="Address"> <parent name="user"/> <property name="street" type="string" column="HOME_STREET"/> <property name="city" type="string" column="HOME_CITY"/> <property name="zipcode" type="short" column="HOME_ZIPCODE"/> </component> The <parent> element maps a property of type User to the owning entity, in this example, the property is named user. We then call Address.getUser() to navigate in the other direction. A Hibernate component may own other components and even associations to other entities. This flexibility is the foundation of Hibernate’s support for finegrained object models. There are two important limitations to classes mapped as components: ■ Shared references aren’t possible. The component Address doesn’t have its own database identity (primary key) and so a particular Address object can’t be referred to by any object other than the containing instance of User. ■ There is no elegant way to represent a null reference to an Address. Hibernate represents null components as null values in all mapped columns of the component. This means that if you store a component object with all null property values, Hibernate will return a null component when the owning entity object is retrieved from the database. Mapping <a href="http://docs.jboss.org/hibernate/core/3.3/reference/en/html/mapping.html#mapping-declaration-discriminator" rel="nofollow">http://docs.jboss.org/hibernate/core/3.3/reference/en/html/mapping.html#mapping-declaration-discriminator</a> Table per concrete class We could use exactly one table for each (non-abstract) class. The main problem with this approach is that it doesn’t support polymorphic associations very well. (can’t be represented as a simple foreign key relationship.) Table per class hierarchy Alternatively, an entire class hierarchy could be mapped to a single table. This table would include columns for all properties of all classes in the hierarchy. There is one major problem: Columns for properties declared by subclasses must be declared to be nullable. If your subclasses each define several non-nullable properties, the loss of NOT NULL constraints could be a serious problem from the point of view of data integrity. [ The <discriminator> element is required for polymorphic persistence using the table-per-class-hierarchy mapping strategy. It declares a discriminator column of the table. The discriminator column contains marker values that tell the persistence layer what subclass to instantiate for a particular row. A restricted set of types can be used: string, character, integer, byte, short, boolean, yes_no, true_false. ] Table per subclass The third option is to represent inheritance relationships as relational foreign key associations. Every subclass that declares persistent properties—including abstract, classes and even interfaces—has its own table. The primary advantage of this strategy is that the relational model is completely normalized. Schema evolution and integrity constraint definition are straightforward. A polymorphic association to a particular subclass may be represented as a foreign key pointing to the table of that subclass. In Hibernate, we use the <joined-subclass> element to indicate a table-per-subclass mapping. <?xml version="1.0"?> <hibernate-mapping> <class name="BillingDetails" table="BILLING_DETAILS"> <id name="id" column="BILLING_DETAILS_ID" type="long"> <generator class="native"/> </id> <property name="owner" column="OWNER" type="string"/> ... <joined-subclass name="CreditCard" table="CREDIT_CARD"> <key column="CREDIT_CARD_ID"> <property name="type" column="TYPE"/> ... </joined-subclass> ... </class> </hibernate-mapping> (Association (1-n, n-m, 1-1) dal sito) To remodel the Item to Bid association as a parent/child relationship, the only change we need to make is to the cascade attribute: <class name="Item" table="ITEM"> ... <set name="bids" inverse="true" cascade="all-delete-orphan"> <key column="ITEM_ID"/> <one-to-many class="Bid"/> </set> </class> CASCADE 1) cascade="none", the default, tells Hibernate to ignore the association. 2) cascade="save-update" tells Hibernate to navigate the association when the transaction is committed and when an object is passed to save() or update() and save newly instantiated transient instances and persist changes to detached instances. 3) cascade="delete" tells Hibernate to navigate the association and delete persistent instances when an object is passed to delete(). 4) cascade="all" means to cascade both save-update and delete, as well as calls to evict and lock. 5) cascade="all-delete-orphan" means the same as cascade="all" but, in addition, Hibernate deletes any persistent entity instance that has been removed (dereferenced) from the association (for example, from a collection). 6) cascade="delete-orphan" Hibernate will delete any persistent entity instance that has been removed (dereferenced) from the association (for example, from a collection). Cap4. The application must interact with the persistence layer whenever it needs to propagate state held in memory to the db or vice versa. PAG 164 ORM OBJECT RELATIONAL MAPPING It mapping between the objects and the database.ORM, in essence, works by (reversibly) transforming data from one representation to another. CRUD (create, read, update, delete) operations - Dati persistent - Operation: ■ Storage, organization, and retrieval of structured data ■ Concurrency and data integrity ■ Data sharing - Granularità If one application holds a lock on a database object, another application might not be able to access that object. For this reason, row-level locks, which minimize the amount of data that is locked and therefore inaccessible, are better for maximum concurrency than block-level, data partition-level or table-level locks. However, locks require storage and processing time, so a single table lock minimizes lock overhead. The LOCKSIZE clause of the ALTER TABLE statement specifies the scope (granularity) of locks at the row, data partition, block, or table level. By default, row locks are used. Only S (Shared) and X (Exclusive) locks are requested by these defined table locks. The ALTER TABLE statement LOCKSIZE ROW clause does not prevent normal lock escalation from occurring. A permanent table lock defined by the ALTER TABLE statement might be preferable to a single-transaction table lock using LOCK TABLE statement in the following cases: - The table is read-only, and will always need only S locks. Other users can also obtain S locks on the table. - The table is usually accessed by read-only applications, but is sometimes accessed by a single user for brief maintenance, and that user requires an X lock. While the maintenance program runs, the read-only applications are locked out, but in other circumstances, read-only applications can access the table concurrently with a minimum of locking overhead. PAG 52 Cap2. The persistence consists in storing data in a relational database using SQL. Hibernate applications define persistent classes that are “mapped” to database tables. package hello; public class Message { private Long id; private String text; private Message nextMessage; private Message() { } public Message(String text) { this.text = text; } public Long getId() { return id; } private void setId(Long id) { this.id = id; } public String getText() { return text; } } public void setText(String text) { this.text = text; } public Message getNextMessage() { return nextMessage; } public void setNextMessage(Message nextMessage) { this.nextMessage = nextMessage; } } It prints "Hello World" to the console. Message message = new Message("Hello World"); System.out.println( message.getText() ); Our persistent class can be used in any execution context at all. Of course, you came here to see Hibernate itself, so let’s save a new Message to the database: Session session = getSessionFactory().openSession(); Transaction tx = session.beginTransaction(); Message message = new Message("Hello World"); session.save(message); tx.commit(); session.close(); This code calls the Hibernate Session and Transaction interfaces. It results in the execution of something similar to the following SQL: insert into MESSAGES (MESSAGE_ID, MESSAGE_TEXT, NEXT_MESSAGE_ID) values (1, 'Hello World', null) We can also assume that the MESSAGES table already exists. Session newSession = getSessionFactory().openSession(); Transaction newTransaction = newSession.beginTransaction(); List messages = newSession.find("from Message as m order by m.text asc"); // HIBERNATE QUERY: select m.MESSAGE_ID, m.MESSAGE_TEXT, m.NEXT_MESSAGE_ID from MESSAGES m order by m.MESSAGE_TEXT asc // System.out.println( messages.size() + " message(s) found:" ); for ( Iterator iter = messages.iterator(); iter.hasNext(); ) { Message message = (Message) iter.next(); System.out.println( message.getText() ); } newTransaction.commit(); newSession.close(); All SQL is generated at runtime. XML MAPPING HIBERNATE CODE <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD//EN" "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd"> <hibernate-mapping> <class name="hello.Message" table="MESSAGES"> <id name="id" column="MESSAGE_ID"> <generator class="increment"/> </id> <property name="text" column="MESSAGE_TEXT"/> <many-to-one name="nextMessage" cascade="all" column="NEXT_MESSAGE_ID"/> </class> </hibernate-mapping> The Hibernate interfaces may be approximately classified as follows: ■ Interfaces called by applications to perform basic CRUD and querying operations. These interfaces are the main point of dependency of application business/control logic on Hibernate. They include Session, Transaction, and Query. ■ Interfaces called by application infrastructure code to configure Hibernate, most importantly the Configuration class. ■ Callback interfaces that allow the application to react to events occurring inside Hibernate, such as Interceptor, Lifecycle, and Validatable. ■ Interfaces that allow extension of Hibernate’s powerful mapping functionality, such as UserType, CompositeUserType, and IdentifierGenerator. These interfaces are implemented by application infrastructure code (if necessary). • SESSION The Session interface is the primary interface used by Hibernate applications. Hibernate sessions are not thread safe and should by design be used by only one thread at a time. • SESSION FACTORY It’s intended to be shared among many application threads. There is typically a single SessionFactory for the whole application. However, if your application accesses multiple databases using Hibernate, you’ll need a SessionFactory for each database. The SessionFactory caches generated SQL statements and other mapping metadata that Hibernate uses at runtime. The following code starts Hibernate: Configuration cfg = new Configuration(); cfg.addResource("hello/Message.hbm.xml"); cfg.setProperties( System.getProperties() ); SessionFactory sessions = cfg.buildSessionFactory(); The location of the mapping file, Message.hbm.xml, is relative to the root of the application classpath. If we had another persistent class, it would be defined in its own mapping file. You can load multiple mapping files by calling addResource() as often as you have to. Alternatively, if you follow the convention just described, you can use the method addClass(), passing a persistent class as the parameter: SessionFactory sessions = new Configuration() .addClass(org.hibernate.auction.model.Item.class) .addClass(org.hibernate.auction.model.Category.class) .addClass(org.hibernate.auction.model.Bid.class) .setProperties( System.getProperties() ) .buildSessionFactory(); If another SessionFactory is needed—if there are multiple databases, for example—you repeat the process. To specify configuration options, you may use any of the following techniques: ■ Used except for quick testing and prototypes: ■ Pass an instance of java.util.Properties to Configuration.setProperties(). ■ Set system properties using java -Dproperty=value. ■ Place a file called hibernate.properties in the classpath. ■ Include <property> elements in hibernate.cfg.xml in the classpath. • CONFIGURATION The Configuration object is used to configure and bootstrap Hibernate. The application uses a Configuration instance to specify the location of mapping documents and Hibernate-specific properties and then create the SessionFactory. Configuration in non-managed environment: Java applications should use a pool of JDBC connections. There are three reasons for using a pool: ■ Acquiring a new connection is expensive. ■ Maintaining many idle connections is expensive. ■ Creating prepared statements is also expensive for some drivers. hibernate.connection.driver_class = org.postgresql.Driver hibernate.connection.url = jdbc:postgresql://localhost/auctiondb hibernate.connection.username = auctionuser hibernate.connection.password = secret hibernate.dialect = net.sf.hibernate.dialect.PostgreSQLDialect hibernate.c3p0.min_size=5 hibernate.c3p0.max_size=20 hibernate.c3p0.timeout=300 hibernate.c3p0.max_statements=50 hibernate.c3p0.idle_test_period=3000 Specifying properties of the form hibernate.c3p0.* selects C3P0 as Hibernate’s connection pool. Configuration managed environment: A managed environment handles certain cross-cutting concerns, such as application security (authorization and authentication), connection pooling, and transaction management. hibernate.connection.datasource = java:/comp/env/jdbc/AuctionDB hibernate.transaction.factory_class = \ net.sf.hibernate.transaction.JTATransactionFactory hibernate.transaction.manager_lookup_class = \ net.sf.hibernate.transaction.JBossTransactionManagerLookup hibernate.dialect = net.sf.hibernate.dialect.PostgreSQLDialect XML-based Configuration: The hibernate.cfg.xml file may also specify the location of mapping documents. ?xml version='1.0'encoding='utf-8'?> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD//EN" "http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd"> <hibernate-configuration> <session-factory name="java:/hibernate/HibernateFactory"> <property name="show_sql">true</property> <property name="connection.datasource"> java:/comp/env/jdbc/AuctionDB</property> <property name="dialect"> net.sf.hibernate.dialect.PostgreSQLDialect </property> <property name="transaction.manager_lookup_class"> net.sf.hibernate.transaction.JBossTransactionManagerLookup </property> <mapping resource="auction/Item.hbm.xml"/> <mapping resource="auction/Category.hbm.xml"/> <mapping resource="auction/Bid.hbm.xml"/> </session-factory> </hibernate-configuration> Now you can initialize Hibernate using: SessionFactory sessions = new Configuration() .configure().buildSessionFactory(); When configure() was called, Hibernate searched for a file named hibernate.cfg.xml in the classpath. If you wish to use a different filename or have Hibernate look in a subdirectory, you must pass a path to the configure() method: SessionFactory sessions = new Configuration().configure("/hibernate-config/auction.cfg.xml").buildSessionFactory(); Using an XML configuration file is certainly more comfortable than a properties file or even programmatic property configuration. Logging When you find yourself troubleshooting a difficult problem, you need to be able to see exactly what’s going on inside Hibernate. You can use logging to get a view of Hibernate’s internals. Hibernate logs all interesting events using Apache commons-logging, a thin abstraction layer that directs output to either Apache log4j (if you put log4j.jar in your classpath). JNDI è acronimo di Java Naming and Directory Interface. All’interno di un Application Server (e anche in applicazioni non necessariamente web). Tutte le operazioni fondamentali che si possono compiere in un Application Server possono essere rimappate utilizzando JNDI. Elenchiamo alcune delle principali operazioni che normalmente vengono compiute: Transazioni (UserTransaction & TransactionManager) Pool di Connessioni ai Database (Datasource) Pool di Connessioni Transazionali ai Database (XADatasource). Con JNDI si possono rimappare tutti i percorsi fisici a cui è necessario puntare, in una sorta di tabella chiave-valore, una specie di HashTable, che rende facilmente configurabile, e quindi portabile, la nostra applicazione. Per maggiori informazioni ed esempi vi invito caldamente a visitare i link correlati. In particolare nel primo link è mostrato come accedere a JNDI in un Application Server Bea Weblogic. Finally, you have the hibernate.properties, hibernate.cfg.xml, and log4j.properties configuration files. Or JMX: JAVA MANAGEMENT EXTENSION The JMX specification defines the following components: ■ The JMX MBean—A reusable component (usually infrastructural) that exposes an interface for management (administration) ■ The JMX container—Mediates generic access (local or remote) to the MBean ■ The (usually generic) JMX client—May be used to administer any MBean via the JMX container An application server with support for JMX (such as JBoss) acts as a JMX container and allows an MBean to be configured and initialized as part of the application server startup process. <server> <mbean code="net.sf.hibernate.jmx.HibernateService" name="jboss.jca:service=HibernateFactory, name=HibernateFactory"> <depends>jboss.jca:service=RARDeployer</depends> <depends>jboss.jca:service=LocalTxCM, name=DataSource</depends> <attribute name="MapResources"> auction/Item.hbm.xml, auction/Bid.hbm.xml </attribute> <attribute name="JndiName"> java:/hibernate/HibernateFactory </attribute> <attribute name="Datasource"> java:/comp/env/jdbc/AuctionDB </attribute> <attribute name="Dialect"> net.sf.hibernate.dialect.PostgreSQLDialect </attribute> <attribute name="TransactionStrategy"> net.sf.hibernate.transaction.JTATransactionFactory </attribute> <attribute name="TransactionManagerLookupStrategy"> net.sf.hibernate.transaction.JBossTransactionManagerLookup </attribute> <attribute name="UserTransactionName"> java:/UserTransaction </attribute> </mbean> </server> • TRANSICTION The Transaction interface is an optional API. Hibernate applications may choose not to use this interface, instead managing transactions in their own infrastructure code. A Transaction abstracts application code from the underlying transaction implementation allowing the application to control transaction boundaries via a consistent API. • CALLBACK Callback interfaces allow the application to receive a notification when something interesting happens to an object—for example, when an object is loaded, saved, or deleted. Hibernate applications don’t need to implement these callbacks, but they’re useful for implementing certain kinds of generic functionality, such as creating audit records. The Lifecycle and Validatable interfaces allow a persistent object to react to events relating to its own persistence lifecycle. • TYPE A Hibernate Type object maps a Java type to a database column type (actually, the type may span multiple columns). All persistent properties of persistent classes, including associations, have a corresponding Hibernate type. This design makes Hibernate extremely flexible and extensible. • EXTENSION POINTS: ■ Primary key generation (IdentifierGenerator interface) ■ SQL dialect support (Dialect abstract class) ////Serve e a specificare quale database stiamo utilizzando oracledialect; mysqldialect ecc... ■ Caching strategies (Cache and CacheProvider interfaces) ■ JDBC connection management (ConnectionProvider interface) ■ Transaction management (TransactionFactory, Transaction, and TransactionManagerLookup interfaces) ■ ORM strategies (ClassPersister interface hierarchy) ■ Property access strategies (PropertyAccessor interface) ■ Proxy creation (ProxyFactory interface) <a href="http://www.roseindia.net/hibernate/firstexample.shtml" rel="nofollow">http://www.roseindia.net/hibernate/firstexample.shtml</a> ARCHITETTURA: Session, Transaction, and Query (Create and compile a persistent class (the initial Message, for example), copy Hibernate and its required libraries to the classpath together with a hibernate.properties file, and build a SessionFactory. The next section covers advanced Hibernate configuration options. Some of them are recommended, such as logging executed SQL statements for debugging or using the convenient XML configuration file instead of plain properties.) Cap3. You shouldn’t put code that addresses these cross-cutting concerns in the classes that implement the domain model. When these concerns start to appear in the domain model classes, we call this an example of leakage of concerns. The EJB standard tries to solve the problem of leaky concerns. Indeed, if we implemented our domain model using entity beans, the container would take care of some concerns for us (or at least externalize those concerns to the deployment descriptor). The EJB container prevents leakage of certain cross-cutting concerns using interception. An EJB is a managed component, always executed inside the EJB container. The container intercepts calls to your beans and executes its own functionality. Hibernate isn’t an application server, and it doesn’t try to implement all the cross-cutting concerns mentioned in the EJB specification. Hibernate is a solution for just one of these concerns: persistence. If you require declarative security and transaction management, you should still access your domain model via a session bean, taking advantage of the EJB container’s implementation of these concerns. Hibernate is commonly used together with the well-known session façade J2EE pattern. Much discussion has gone into the topic of persistence, and both Hibernate and EJB entity beans take care of that concern. However, Hibernate offers something that entity beans don’t: transparent persistence. Our Item class, for example, will not have any code-level dependency to any Hibernate API. Furthermore: ■ Hibernate doesn’t require that any special superclasses or interfaces be inherited or implemented by persistent classes. Nor are any special classes used to implement properties or associations. Thus, transparent persistence improves code readability, as you’ll soon see. ■ Persistent classes may be reused outside the context of persistence, in unit tests or in the user interface (UI) tier, for example. Testability is a basic requirement for applications with rich domain models. ■ In a system with transparent persistence, objects aren’t aware of the underlying data store; they need not even be aware that they are being persisted or retrieved. Persistence concerns are externalized to a generic persistence manager interface —in the case of Hibernate, the Session and Query interfaces. By this definition of transparent persistence, you see that certain non-automated persistence layers are transparent (for example, the DAO pattern) because they decouple the persistence-related code with abstract programming interfaces. The programming model we’ll introduce is a non-intrusive mix of JavaBean specification details, POJO best practices, and Hibernate requirements. A POJO declares business methods, which define behavior, and properties, which represent state. Some properties represent associations to other POJOs. It’s an implementation of the User entity of our domain model. public class User implements Serializable { private String username; private Address address; public User() { } public String getUsername() { return username; } public void setUsername(String username) { this.username = username; } public Address getAddress() { return address; public void setAddress(Address address) { this.address = address; } ... } } You use properties to express associations between POJO classes, and you use accessor methods to navigate the object graph at runtime. scaffolding code:codice di “collegamento”(ER model). For example let’s implement the scaffolding code for the one-to-many self-association of Category: public class Category implements Serializable { private String name; private Category parentCategory; private Set childCategories = new HashSet(); public Category() { } ... } To allow bidirectional navigation of the association, we require two attributes. The parentCategory attribute implements the single-valued end of the association and is declared to be of type Category. The many-valued end, implemented by the child-Categories attribute, must be of collection type. We choose a Set, since duplicates are disallowed, and initialize the instance variable to a new instance of HashSet. We now have some private instance variables but no public interface to allow access from business code or property management by Hibernate. Let’s add some accessor methods to the Category class: public String getName() { return name; } public void setName(String name) { this.name = name; } public Set getChildCategories() { return childCategories; } public void setChildCategories(Set childCategories) { this.childCategories = childCategories; } public Category getParentCategory() { return parentCategory; } public void setParentCategory(Category parentCategory) { this.parentCategory = parentCategory; } Again, these accessor methods need to be declared public only if they’re part of the external interface of the persistent class, the public interface used by the application logic. The basic procedure for adding a child Category to a parent Category looks like this: Category aParent = new Category(); Category aChild = new Category(); aChild.setParentCategory(aParent); aParent.getChildCategories().add(aChild); ■ The parentCategory of the child must be set, effectively breaking the association between the child and its old parent (there can be only one parent for any child). ■ The child must be added to the child Categories collection of the new parent. Programming models like EJB entity beans muddle this behavior by introducing container-managed relationships. The container automatically changes the other side of a relationship if one side is modified by the application. Hibernate doesn’t care if property access methods are private or public, so we can focus on good API design. One of the reasons we like to use JavaBeans-style access methods is that they provide encapsulation: The hidden internal implementation of a property can be changed without any changes to the public interface. This allows you to abstract the internal data structure of a class—the instance variables—from the design of the database. For example, if your database stores a name of the user as a single NAME column, but your User class has first name and last name properties, you can add the following persistent name property to your class: Public class User { private String firstname; private String lastname; ... public String getName() { return firstname + ' ' + lastname; } public void setName(String name) { StringTokenizer t = new StringTokenizer(name); firstname = t.nextToken(); lastname = t.nextToken(); ) ... } Later, you’ll see that a Hibernate custom type is probably a better way to handle many of these kinds of situations. Hibernate will later use our accessor methods to populate the state of an object when loading the object from the database. Hibernate result in unnecessary SQL UPDATEs. This kind of code should almost always be avoided in accessor methods: public void setNames(List namesList) { names = (String[]) namesList.toArray(); } public List getNames() { return Arrays.asList(names); } METADATA ORM tools require a metadata format for the application to specify the mapping between classes and tables, properties and columns, associations and foreign keys, Java types and SQL types. This information is called the object/relational mapping metadata. It defines the transformation between the different data type systems and relationship representations. XML mapping: (DTD = document type definition) <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD//EN" "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd"> <hibernate-mapping> <class name="org.hibernate.auction.model.Category" table="CATEGORY"> <id name="id" column="CATEGORY_ID" type="long"> <generator class="native"/> </id> <property name="name" column="NAME" type="string"/> </class> </hibernate-mapping> If you omit the type, Hibernate will use the Hibernate type string by default. The <property> element (and especially the <column> element) also defines certain attributes that apply mainly to automatic database schema generation. <property name="initialPrice" column="INITIAL_PRICE" not-null="true"/> <property name="totalIncludingTax" formula="TOTAL + TAX_RATE * TOTAL" type="big_decimal"/> The given SQL formula is evaluated every time the entity is retrieved from the database. The property doesn’t have a column attribute (or sub-element) and appears in an SQL SELECTs. Formulas may refer to columns of the database table, call SQL functions, and include SQL subselects. This example, mapping a derived property of item, uses a correlated subselect to calculate the average amount of all bids for an item: <property name="averageBidAmount" formula="( select AVG(b.AMOUNT) from BID b ➾where b.ITEM_ID = ITEM_ID )" type="big_decimal"/> access="field" Access to properties via accessor methods is considered best practice by the Hibernate community. It provides an extra level of abstraction between the Java domain model and the data model. insert="false" update="false" The property name of the JavaBean is therefore immutable and can be read from the database but not modified in any way. If the complete class is immutable, set the immutable="false" in the class mapping. The dynamic-update attribute tells Hibernate whether to include unmodified properties in the SQL UPDATE: <class name="org.hibernate.auction.model.User" dynamic-insert="true" dynamic-update="true"> ... </class> These are both class-level settings. Enabling either of these settings will cause Hibernate to generate some SQL at runtime, instead of using the SQL cached at startup time. SQL schemas You can specify a default schema using the hibernate.default_schema configuration option. Alternatively, you can specify a schema in the mapping document. A schema may be specified for a particular class or collection mapping: <hibernate-mapping> <class name="org.hibernate.auction.model.Category" table="CATEGORY" schema="AUCTION"> ... </class> </hibernate-mapping> It can even be declared for the whole document: <hibernate-mapping default-schema="AUCTION"> .. </hibernate-mapping> This isn’t the only thing the root <hibernate-mapping> element is useful for. ( <a href="http://www.mokabyte.it/2005/11/hibernate.htm" rel="nofollow">http://www.mokabyte.it/2005/11/hibernate.htm</a> tag of XDOCLET: <a href="http://xdoclet.sourceforge.net/xdoclet/tags/hibernate-tags.html#@hibernate_property__0__1_" rel="nofollow">http://xdoclet.sourceforge.net/xdoclet/tags/hibernate-tags.html#@hibernate_property__0__1_</a> using a script build.xml of Ant ) using declaration type ... // Define a new column for the USER table Column column = new Column(); column.setType(Hibernate.STRING); column.setName("ETA"); column.setNullable(false); column.setUnique(true); userMapping.getTable().addColumn(column); // Wrap the column in a Value SimpleValue value = new SimpleValue(); value.setTable( userMapping.getTable() ); value.addColumn(column); value.setType(Hibernate.STRING); // Define a new property of the User class Property prop = new Property(); prop.setValue(value); prop.setName("eta"); userMapping.addProperty(prop); // Build a new session factory, using the new mapping SessionFactory sf = cfg.buildSessionFactory(); ■ Object identity—Objects are identical if they occupy the same memory location in the JVM. This can be checked by using the == operator. ■ Object equality—Objects are equal if they have the same value, as defined by the equ silvan on "Release: openmamba milestone2 2.0pre2" http://forum.openmamba.org/topic.php?id=518#post-3579 Wed, 09 Jun 2010 15:38:25 +0000 silvan 3579@http://forum.openmamba.org/ The second pre-release of openmamba milestone 2 is ready with over 700 software package updates to the latest releases. The system is based on Linux kernel 2.6.31.13 and offers a modern desktop environment that includes KDE (4.4.4), OpenOffice (3.2), Firefox (3.6.3), Amarok (2.3.1) and much more. The full list of changes is available at this link: <a href="http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog" rel="nofollow">http://www.openmamba.org/distribution/distromatic.html?tag=milestone2&changelog</a> Changes were made to the installation application from live media, as it now supports a "cloned" installation of the live pendrive system and the configuration of a separated partition for the "/home" folder. openmamba is available for download in livecd, livedvd and livegames flavours for english, italian and spanish languages at this page: <a href="http://www.openmamba.org/distribution/download.html" rel="nofollow">http://www.openmamba.org/distribution/download.html</a> Users of the first pre-release will receive a consistent upgrade from network to get aligned with the latest system release. In case of problems it is recommended to write on the forum at <a href="http://forum.openmamba.org" rel="nofollow">http://forum.openmamba.org</a> or to use the bug-tracking page at <a href="http://bugs.openmamba.org" rel="nofollow">http://bugs.openmamba.org</a>. openmamba milestone2 consists of contributions from packagers, graphic designers and translators and of an automatized maintainance and update system that characterizes the distribution update level. Beta-tester and developers are welcome and can subscribe and write to the development lists at <a href="http://www.openmamba.org/lists/" rel="nofollow">http://www.openmamba.org/lists/</a> or in the forum. mambaSoft wishes everybody a pleasant experience with openmamba. Silvan silvan on "Release: openmamba milestone2 2.0pre1" http://forum.openmamba.org/topic.php?id=510#post-3518 Thu, 11 Mar 2010 01:44:43 +0000 silvan 3518@http://forum.openmamba.org/ I've seen in past such problems with combinations of IDE/SATA disks, is that your situation? Can you provide the installation log that is called /var/log/install*.log and is in the installed openmamba partition? You may attach it here or more privately to reports<at>openmamba<dot>org. Thanks. erick111 on "Release: openmamba milestone2 2.0pre1" http://forum.openmamba.org/topic.php?id=510#post-3517 Thu, 11 Mar 2010 00:22:40 +0000 erick111 3517@http://forum.openmamba.org/ Hi Silvan, I like openmamba it works great as a live cd, my problem is when I installit as a second hard drive system after I reboot it goes to Grub Rescue & will not boot any system is there a problem with Grub installation I have not experienced this with any other linux distro silvan on "Release: openmamba milestone2 2.0pre1" http://forum.openmamba.org/topic.php?id=510#post-3504 Tue, 02 Mar 2010 04:13:53 +0000 silvan 3504@http://forum.openmamba.org/ I'm happy to announce the immediate availability of openmamba milestone2 2.0pre1, the new version of the GNU/Linux operating system for laptop, desktop and server PC's. The second "milestone" of the openmamba development project has been reached thanks to the integration of the modern KDE 4 desktop environment, the most recent improvements to the Linux kernel and system software and the best open source applications. milestone2 offers a renewed tecnological experience thanks to the introduction of automatic maintainance and update mechanisms and to the contribution of mambaSoft and the openmamba developers community, thus providing the user a simple and smart instrument for the interaction with present computer technologies and the internet. After months devoted to development and testing, this release is for the users who look for a optimal combination of innovation, reliability and stability. The use of stable repositories with few massive upgrades scheduled, give the user the needed reliability for most purposes. openmamba milestone2 is available for free download from this web site in the form of ISO images for livecd and livedvd media. The bootusb distribution can be used with the ISO images to install openmamba on a pen drive, thus also offering a personal system that can be used on many different PC's. openmamba media are available in three languages: italian, english and spanish (new!). silvan on "Announcement: openmamba milestone1 1.1 stable" http://forum.openmamba.org/topic.php?id=451#post-3142 Tue, 04 Aug 2009 14:01:16 +0000 silvan 3142@http://forum.openmamba.org/ The new 1.1 release of openmamba milestone1 is available for download. It is a maintainance release since 1.0, with support for recent hardware platforms and fixes to improve system usability and stability. This release includes: - all software updates made available afer openmamba 1.0 release - 2.6.28.10 kernel with wireless and audio drivers backport with support for the most recent devices - wicd network manager for easier access to wireless networks - X.org server 1.4 with updated video drivers - new installdvd media that allows a full system installation rapidly and without using the network - new bootusb media for system startup and installation from an USB storage device - update from openmamba milestone1 1.0 can be performed without reinstallation openmamba milestone1 1.1 is available as a free download in english and italian languages. Other languages are supported after installation. Within the next weeks the first pre-release of openmamba2 will be made available. This is where most of the work of the latest months has been addressed with many important system new features. This release can already be downloaded and installed through the weekly snapshot. silvan on "Release: openmamba milestone1 1.1pre4" http://forum.openmamba.org/topic.php?id=408#post-2784 Thu, 19 Feb 2009 15:36:32 +0000 silvan 2784@http://forum.openmamba.org/ The forth pre-release of openmamba milestone1 is available for download. It is a maintainance release of openmamba stable with the aim of correcting the hardware support problems detected with release 1.0 especially with new hardware. The most important new features are: * 2.6.26.8 kernel * backport of the latest release of audio drivers from the ALSA project * backport of the latest release of wireless drivers from the Compat-Wireless project * update of video drivers (Intel GMA4500, NVidia) * Xorg 1.4.3 * disabled by default the Jack low-latency audio server (it can be enabled through QJackCtrl before using professional audio applications) openmamba milestone1 1.1pre4 is available in the following CD/DVD live media: * livecd * livestudio * installdvd Download can be started from this page: <a href="http://www.openmamba.org/distribution/download.html" rel="nofollow">http://www.openmamba.org/distribution/download.html</a> openmamba 1.0 installations can be upgraded to 1.1 by adding the milestone1 1.1 repository to the list of apt installation sources and performing a system update. It is adviced, before doing this operatrion, to check the compatibility of the new kernel with your hardware by testing one of the 1.1pre4 release live CD/DVD media. The stable release of milestone1 1.1 requiest a period of testing. Please send any bug report using the bugs site <a href="http://bugs.openmamba.org" rel="nofollow">http://bugs.openmamba.org</a>. Thanks for your attention and have a nice day, Silvan silvan on "Announcement: openmamba milestone1 1.0 stable" http://forum.openmamba.org/topic.php?id=285#post-1730 Fri, 01 Aug 2008 18:36:05 +0000 silvan 1730@http://forum.openmamba.org/ The first stable release of the openmamba GNU/Linux distribution is available today for download. openmamba is a GNU/Linux distribution for Personal Computer (Intel i686 compatibles) that can be used on notebooks, desktop and servers. The milestone1 distribution provides almost 4000 software packages made from scratch which include the most popular applications as well as advanced software technologies like Compiz-Fusion and Jack audio server. The system is thought to be simple and fast to install and easy to use for most users, and the website (www.openmamba.org) provides services to help users and developers to maintain and develop the distribution, such as a forum, a wiki and a bug tracking website. Though most development and tests have been made in Italy the distribution installation media are available in both Italian and English languages and the system can later be customized to support other languages. The stable system lets users make use of it in production environments, where software updates need to be limited and focused on security and bug fixes. At the same time the development of the second milestone has begun and users will be able to install a test system using the weekly development snapshots with the latest software releases and support for new hardware that may not be supported in milestone1. To get started with openmamba milestone1 please visit <a href="http://www.openmamba.org/distribution/" rel="nofollow">http://www.openmamba.org/distribution/</a>. The openmamba GNU/Linux distribution is provided and maintained by mambaSoft and developed by a community made of self organized individuals and development groups. silvan on "Announcement: openmamba milestone1 pre-release 7" http://forum.openmamba.org/topic.php?id=275#post-1680 Mon, 28 Jul 2008 16:58:25 +0000 silvan 1680@http://forum.openmamba.org/ A new pre-release of openmamba milestone1, the 7th, is available for download. This version provides the correction of some installation problems with SATA devices, a general update of wireless drivers and the update of most system libraries. If the tests won't reveal show-stopping problems, this release with minor or no changes will be tagged as stable 1.0. The livecd release can be downloaded at the address: <a href="http://www.openmamba.org/distribution/media/livecd.html" rel="nofollow">http://www.openmamba.org/distribution/media/livecd.html</a> The livestudio release can be downloaded at the address: <a href="http://www.openmamba.org/distribution/media/livestudio.html" rel="nofollow">http://www.openmamba.org/distribution/media/livestudio.html</a> Silvan silvan on "Announcement: new openmamba milestone 1 pre-release 5" http://forum.openmamba.org/topic.php?id=221#post-1281 Mon, 02 Jun 2008 17:35:47 +0000 silvan 1281@http://forum.openmamba.org/ **openmamba milestone1 pre-release 5** A new release of openmamba livecd and livestudio is available for download. What's new in this release: * Test and correction of international (english) release * Added installation group with base web server packages (Apache, PHP, MySQL) * Added integrated support for internet access through proxy server * Support for PDA and cellullar phones syncronization with kitchensync (beta) * Supporto for Skype installation from network * System and desktop final changes for stable release * Many updates and bugfixes The livecd release can be downloaded from <a href="http://www.openmamba.org/distribution/media/livecd.html" rel="nofollow">http://www.openmamba.org/distribution/media/livecd.html</a> The livestudio release can be downloaded from <a href="http://www.openmamba.org/distribution/media/livestudio.html" rel="nofollow">http://www.openmamba.org/distribution/media/livestudio.html</a> If the tests won't expose big problems, in a short period the milestone 1 repository will be freezed and stable openmamba milestone 1 1.0 will be released. This will give users a stable system with limited updates and developers a development branch for the future milestone 2 release. Have a nice day, Silvan silvan on "Announcement: openmamba milestone1 1.0pre3 (third pre-release)" http://forum.openmamba.org/topic.php?id=57#post-192 Tue, 26 Feb 2008 15:04:14 +0000 silvan 192@http://forum.openmamba.org/ The third openmamba pre-release is available with tag <code>snapshot 20080224</code>. The tests on the previous releases let us face and solve some relevant installation problems and the result is a more simple installation procedure for most users. Many thanks to all the beta testers who made this possible! Here are the most important changes of this release: <ul> <li>added support for installation in systems with different combinations of IDE, SATA and SCSI disks <li>boot menu (grub 2): fixed support for Windows Vista boot</li> <li>installation wizard: check on partitions improved and the whole process has been made simpler by adding more pages to the wizard <li>many system bugfixes</li> </ul> Before the stable release is ready we plan to release a forth (and last) pre-release with the following changes: <ul> <li>kernel: update to version 2.6.24</li> <li>configuration dialog for language, country, keyboard and time when installation starts</li> <li>boot menu: support for Windows and other chainloaded system boot from secondary disks</li> <li>boot menu: support for automatic configuration of other Linux systems</li> </ul> If you want to be informed about the latest news you may subscribe to the openmamba newsletter by <a href="http://www.openmamba.org/registration.html">registering</a> on the website. The latest release can be downloaded from <a href="http://www.openmamba.org/distribution/download.html">this page</a>. A first-use guide and a problems resolution guided procedure are available in the <a href="http://wiki.openmamba.org">wiki</a>. The wiki is currently being written in italian language, but we are looking forward to find help for translations! If you want to help us in this job please <a href="mailto:info@openmamba.org">contact us</a>. If you have problems you may submit a <a href="http://bugs.openmamba.org">bug report</a>, or use the <a href="http://forum.openmamba.org">forum</a> or the <a href="http://lists.openmamba.org">mailing lists</a>. openmamba adventure continues, we wish you an amazing experience! silvan on "Announcement: openmamba milestone1 pre-release ready for wide testing" http://forum.openmamba.org/topic.php?id=47#post-170 Thu, 24 Jan 2008 15:05:11 +0000 silvan 170@http://forum.openmamba.org/ After one year of development the first stable release of openmamba is almost ready. The distribution, available in english and italian languages, is ready for wide testing and especially the international release might need some more test because most development so far was made in italy. <a href="http://www.openmamba.org/distribution/download.html">Download</a> the installable livecd (snapshot 20080124), see the <a href="http://wiki.openmamba.org">wiki</a> to get more information and use the <a href="http://forum.openmamba.org">forums</a> or <a href="http://www.openmamba.org/distribution">mailing lists</a> to share information with other users and developers. If you fall into a bug, please post a <a href="http://bugs.openmamba.org">report</a>. If you want to use openmamba in the easiest and most powerful way see the new <a href="http://store.mambasoft.it">openmamba-based laptops</a> distributed by <a href="http://www.mambasoft.it">mambaSoft</a>, the creator and maintainer of this project. openmamba is free software, please read the <a href="http://www.openmamba.org/licensing.html">licensing terms</a> for more information. silvan on "New openmamba documentation site (Wiki)" http://forum.openmamba.org/topic.php?id=40#post-138 Thu, 03 Jan 2008 13:15:48 +0000 silvan 138@http://forum.openmamba.org/ Hi everybody and happy new year from openmamba! The new year begins with the new wiki, in english and italian languages, available at the following address: <a href="http://wiki.openmamba.org" rel="nofollow">http://wiki.openmamba.org</a> The site is ready to accept contents about the distribution and the openmamba community. Currently there is just a very simple main page but you are invited since now to discuss and add pages to share your openmamba experience. Silvan silvan on "New openmamba bug tracking system is online" http://forum.openmamba.org/topic.php?id=35#post-115 Tue, 18 Dec 2007 13:35:32 +0000 silvan 115@http://forum.openmamba.org/ The new openmamba bug tracking system is available (in beta) at the address <a href="http://bugs.openmamba.org">bugs.openmamba.org</a>. You are kindly invited to use this service to send bug reports and to give us feedback if you have problems with the web interface. Thank you! Silvan silvan on "Announcement: openmamba livegames and livestudio" http://forum.openmamba.org/topic.php?id=27#post-89 Thu, 15 Nov 2007 18:05:46 +0000 silvan 89@http://forum.openmamba.org/ It's a pleasure for me to announce the availability of two new live medias: <ul> <li><a href="http://www.openmamba.org/distribution/media/livegames.html">livegames</a>: a collection of the best games in the distribution including Torcs, Tuxracer, Tuxkart, Pingus, FlightGear, Frozen Bubble, KSudoku. It's perfect for entertainment moments anywhere a personal computer is available.</li> <li><a href="http://www.openmamba.org/distribution/media/livestudio.html">livestudio</a>: a collection of programs for creative, artistic and multimedia-oriented creativity that includes Blender, GIMP, Mixxx, Lives, Qtractor, Rosegarden, Audacity, ZynAddSubFX, Hydrogen, Kino. Conceived for musicians, designers, graphics, photographers and who loves expressing it's own creativity through new technologies.</li> </ul> <code></code> Like openmamba livecd, livegames and livestudio let you perform an openmamba installation on a computer providing a specialized set of programs that are immediately available for use. After the installation the mamba tool let's perform a network installation of any other software components desired. Images are made available as weekly snapshots and thus are useful to simplify the development and test process of the base system. livegames and livestudio are based on the openmamba milestone1 (Release Candidate 1) system. Freshly included softwares are considered at a beta-test stage. bye Silvan silvan on "livecd 20071018: completed installation and many bugfixes" http://forum.openmamba.org/topic.php?id=18#post-55 Thu, 18 Oct 2007 14:11:09 +0000 silvan 55@http://forum.openmamba.org/ A new livecd release worth a try! With this release, the system installation is complete with all the necessary components and the first stable release (<code>milestone 1</code>) of openmamba is getting closer. The news are: * new <code>mamba</code> tool that completes the installation from network and lets install and update group of packages as well as non distributable softwares (Flash plugin, Win32 codes, Microsoft TrueType Corefonts) * support for installation in extended partitions and secondary disks * support for boot from USB, SCSI, SATA and PATA cdrom * a lot of bugfixes You are invited to <a href="http://www.openmamba.org/distribution/media/livecd.html">download</a> the livecd and report any problem to this forum or to the <a href="http://www.openmamba.org/distribution">mailing lists</a>. Silvan silvan on "livecd 20070920: video support and installer news" http://forum.openmamba.org/topic.php?id=14#post-46 Fri, 21 Sep 2007 02:04:47 +0000 silvan 46@http://forum.openmamba.org/ Turn of the screw on the livecd system with the following news: * nvidia legacy drivers support, automatic configuration and compiz startup * fix: window manager crash (compiz) when direct rendering is not available * fix: error detecting usb pens due to a wrong /dev/sda1 entry in /etc/fstab * lanuch keyboard setting dialog on first startup (english release only) * various bugfixes News in the installer (0.3): * italian language translation * non-linux operating systems choice for the boot menu * linux installed partition is (optionally) flagged as bootable Updates are available for flash-1GB and bootcd distributions, too. cheers, Silvan silvan on "livecd e flash-1GB: important bugfix release (20070910)" http://forum.openmamba.org/topic.php?id=9#post-24 Tue, 11 Sep 2007 10:36:58 +0000 silvan 24@http://forum.openmamba.org/ This release mostly fixes a couple of bugs: - automatic libGL alternatives management corrrected (dri,fglrx,nvidia) thus fixing the problem of the window manager not starting at boot and enabling direct rendering where supported; - detected disk partitions are now configured for mounting in /mnt/disk[0-9] instead of all in /mnt/disk Silvan silvan on "livecd 20070905: fix for nvidia proprietary driver and compiz" http://forum.openmamba.org/topic.php?id=8#post-22 Thu, 06 Sep 2007 11:35:08 +0000 silvan 22@http://forum.openmamba.org/ The latest livecd release (20070905) has a fix for the autodetection of nvidia proprietary drivers. If you have a GPU supported by the latest release of the driver, the system will automatically start with Compiz 3D desktop support! We are looking for beta-tester for verifying and adding AIGLX + Compiz support on other supported GPUs (Intel, ATI Radeon, ...). bye Silvan silvan on "New openmamba forum" http://forum.openmamba.org/topic.php?id=6#post-7 Tue, 04 Sep 2007 13:30:09 +0000 silvan 7@http://forum.openmamba.org/ The new openmamba forum is available. You can register <a href="http://www.openmamba.org/registration.html">here</a>. Good blogging! Silvan