DOCSLIB.ORG

Java™ Persistence API: Portability Do's and Don'ts

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Java™ Persistence API: Portability Do's and Don'ts Java™ Persistence API: Portability Do’s and Don’ts Mike Keith Oracle Corp. http://otn.oracle.com/jpa TS-4568 2007 JavaOneSM Conference | Session TS-4568 | GoalGoal To learn more about Java™ Persistence API (JPA), what the portability issues are, and what you need to know to write more portable code. 2007 JavaOneSM Conference | Session TS-4568 | 2 Agenda Background and Status The Portability Struggle Built-in Strategies Other Strategies Voice of Warning (A Case Study) Review and Summary 2007 JavaOneSM Conference | Session TS-4568 | 3 Agenda Background and Status The Portability Struggle Built-in Strategies Other Strategies Voice of Warning (A Case Study) Review and Summary 2007 JavaOneSM Conference | Session TS-4568 | 4 Background • Unifying POJO persistence technology into a standard enterprise API • Part of Enterprise JavaBeans™ (EJB™) 3.0 specification, but is separately documented • May be used in either Java Platform, Enterprise Edition (Java EE platform) or Java Platform, Standard Edition (Java SE platform) • Superior ease of use within host container • Client API with local transactions in Java SE platform • Service Provider Interface (SPI) for container/persistence provider pluggability 2007 JavaOneSM Conference | Session TS-4568 | 5 Primary Features • POJO-based persistence model • Simple Java class files—not components • Supports traditional O-O modelling concepts • Inheritance, polymorphism, encapsulation, etc. • Standard abstract relational query language • Standard O/R mapping metadata • Using annotations and/or XML • Portability across providers (implementations) 2007 JavaOneSM Conference | Session TS-4568 | 6 Where Are We Now? • JPA 1.0 finalized in May 2006 • Released as part of Java EE 5 platform • All major vendors have implemented or are working towards offering EJB 3.0 specification/JPA • Developer interest and adoption proving to be extremely strong • 80–90% of useful ORM features specified • Additional features will be added to JPA 2.0 2007 JavaOneSM Conference | Session TS-4568 | 7 Implementations • Persistence provider vendors include: • Oracle, Sun/TopLink Essentials (RI) • Eclipse JPA—EclipseLink Project • BEA Kodo/Apache OpenJPA • RedHat/JBoss Hibernate • SAP JPA • JPA containers • Sun, Oracle, SAP, BEA, JBoss, Spring 2.0 • IDEs • Eclipse, NetBeans™ IDE, IntelliJ, JDeveloper 2007 JavaOneSM Conference | Session TS-4568 | 8 Agenda Background and Status The Portability Struggle Built-in Strategies Other Strategies Voice of Warning (A Case Study) Review and Summary 2007 JavaOneSM Conference | Session TS-4568 | 9 Forces Acting Upon Us Portability Features Simplicity 2007 JavaOneSM Conference | Session TS-4568 | 10 Portability vs. Added Value Innovation Is Good! • Vendors are expected to add features their customers ask for and need • Popular features will be moved into the JPA spec • Less used features shouldn’t clutter the API Corollary 1: We will always have to live with the presence of non-standard features Corollary 2: If you are ever in the position of needing a feature that is not in the spec then you will be glad Corollary 1 is true 2007 JavaOneSM Conference | Session TS-4568 | 11 Accessing Vendor Features • Vendor features show up in different forms • Persistence properties • Query hints • Casting to vendor-specific class • Customization code • Vendor-specific annotations • Additional proprietary XML descriptors 2007 JavaOneSM Conference | Session TS-4568 | 12 Agenda Background and Status The Portability Struggle Built-in Strategies Other Strategies Voice of Warning (A Case Study) Review and Summary 2007 JavaOneSM Conference | Session TS-4568 | 13 Integrating the Proprietary • Hooks are built into JPA to support vendor- specific features at two different levels • Persistence unit properties • Query hints • Unrecognized options must be ignored by the provider • Provides source code and compile-time portability • Not necessarily semantically portable 2007 JavaOneSM Conference | Session TS-4568 | 14 Persistence Unit Properties • Set of optional key-value properties specified in persistence.xml file • Apply to the entire persistence unit • May have multiple vendor properties specifying the same or different things • Property only has meaning to the vendor that defines and interprets it 2007 JavaOneSM Conference | Session TS-4568 | 15 Persistence Unit Properties <persistence> <persistence-unit name=“HR”> <properties> <property name=“toplink.logging.thread” value=“false”/> <property name=“toplink.cache.shared.default” value=“false”/> </properties> </persistence-unit> </persistence> 2007 JavaOneSM Conference | Session TS-4568 | 16 Query Hints • Vendor directives may be defined statically in named query metadata (annotations or XML) • Applied at query execution time @NamedQuery(name=“Trade.findBySymbol”, query=“SELECT t FROM Trade t “ + “WHERE t.symbol = :sym”, hints={ @QueryHint( name=“toplink.pessimistic-lock”, value=“Lock”), @QueryHint( name=“openjpa.ReadLockLevel”, value=“write”) } ) 2007 JavaOneSM Conference | Session TS-4568 | 17 Query Hints • May be defined dynamically using the Query API • More flexible because any Java object may be passed in as the value • Lose source-code portability if object is vendor-specific Query query = em.createQuery( “SELECT t FROM Trade t WHERE t.symbol = :sym”); query.setHint(“toplink.pessimistic-lock”,“Lock”); .setHint(“openjpa.ReadLockLevel” “write”); .setParameter(“sym”,“ORCL”) .getResultList(); 2007 JavaOneSM Conference | Session TS-4568 | 18 Pessimistic Transactions • Optimistic concurrency is built into JPA, but no support for pessimistic locking is specified • Will likely be addressed in a future JPA release • All credible JPA implementations support pessimistic locks in some way or another • No completely portable way to pessimistically lock, but many provide query hints like those shown in previous slides • EntityManager lock() method can be used with optimistic locking, and error handling 2007 JavaOneSM Conference | Session TS-4568 | 19 Java DataBase Connectivity (JDBC™) Connection Settings • Resource-level JDBC technology settings are vendors responsibility • Need to specify the four basic JDBC technology properties to obtain driver connections • Driver class, URL, username, password • The property keys will be different, but the values for a given JDBC technology data source will be the same for all vendors • Used when not in a container, or when managed data sources are not available or not desired 2007 JavaOneSM Conference | Session TS-4568 | 20 JDBC Technology Connection Settings <properties> ... <!–- TopLink --> <property name=“toplink.jdbc.driver” value=“oracle.jdbc.Driver”/> <property name=“toplink.jdbc.url” value=“jdbc:oracle:thin:@localhost:1521:XE”/> <property name=“toplink.jdbc.user value=“scott”/> <property name=“toplink.jdbc.password” value=“tiger”/> 2007 JavaOneSM Conference | Session TS-4568 | 21 JDBC Technology Connection Settings ... <!–- OpenJPA --> <property name="openjpa.ConnectionDriverName" value=“oracle.jdbc.Driver”/> <property name="openjpa.ConnectionURL" value="jdbc:oracle:thin:@localhost:1521:XE"/> <property name="openjpa.ConnectionUserName" value="scott"/> <property name="openjpa.ConnectionPassword" value=“tiger"/> ... </properties> 2007 JavaOneSM Conference | Session TS-4568 | 22 DDL Generation • Standard enables it but does not currently dictate that providers support it • Mapping metadata specifies how DDL should be generated • Vendors may offer differing levels of support, including: • Generating DDL to a file only • Generating and executing DDL in DB • Dropping existing tables before creating new ones 2007 JavaOneSM Conference | Session TS-4568 | 23 DDL Generation <properties> ... <!–- TopLink --> <property name="toplink.ddl-generation" value="create-tables"/> <!–- OpenJPA --> <property name="openjpa.jdbc.SynchronizeMappings" value=“buildSchema"/> ... </properties> 2007 JavaOneSM Conference | Session TS-4568 | 24 Database Platform • No standard way to define the database platform being used at the back end • If provider knows the database then it can: • Generate corresponding SQL • Make use of db-specific features and types • Make adjustments for db-specific constraints and limitations • Implementations usually automatically discover database platform 2007 JavaOneSM Conference | Session TS-4568 | 25 Database Platform <properties> ... <!–- TopLink --> <property name="toplink.target-database" value="Derby"/> <!–- OpenJPA --> <property name="openjpa.jdbc.DBDictionary" value="derby"/> ... </properties> 2007 JavaOneSM Conference | Session TS-4568 | 26 Logging • Users want to control over logging, but vendors use different logging APIs • Can usually configure to use one of the well- known logging APIs • java.util.logging, log4J, etc. • Common requirement is to configure the logging level to show the generated SQL 2007 JavaOneSM Conference | Session TS-4568 | 27 Logging <properties> ... <!–- TopLink --> <property name="toplink.logging.level" value="FINE"/> <!–- OpenJPA --> <property name="openjpa.Log" value=“Query=TRACE, SQL=TRACE"/> ... </properties> 2007 JavaOneSM Conference | Session TS-4568 | 28 Agenda Background and Status The Portability Struggle Built-in Strategies Other Strategies Voice of Warning (A Case Study) Review and Summary 2007 JavaOneSM Conference | Session TS-4568 | 29 Casting to Implementation Artifacts • Cast specification-defined interface to a vendor implementation type public Employee pessimisticRead1(int id) { Employee emp = em.find(Employee.class, id); UnitOfWork uow = (TopLinkEntityManager) em.getUnitOfWork();
Load more

Recommended publications
  • Oracle Application Server 10G R3 (10.1.3.1) New Features Overview
    Oracle Application Server 10g R3 (10.1.3.1) New Features Overview An Oracle White Paper October 2006 Oracle Application Server 10gR3 New Features Overview 1.0 Introduction................................................................................................. 4 2.0 Standards Support: J2EE Infrastructure ................................................. 5 2.1 Presentation Tier – Java Server Pages and JavaServer Faces........... 6 2.2 Business Tier – Enterprise Java Beans................................................ 7 2.3 Persistence - TopLink............................................................................ 8 2.3.1 Oracle TopLink............................................................................... 8 2.3.2 EJB 3.0 Persistence......................................................................... 9 2.3.3 Object-XML.................................................................................... 9 2.4 Data Sources and Transactions ............................................................ 9 2.4.1 Data Sources.................................................................................... 9 2.4.2 Transactions................................................................................... 10 2.5 Java 2 Connector Architecture ........................................................... 10 2.6 Security................................................................................................... 11 2.6.1 Core Container.............................................................................
    [Show full text]
  • Oracle® Toplink Release Notes Release 12C (12.1.2)
    Oracle® TopLink Release Notes Release 12c (12.1.2) E40213-01 June 2013 This chapter describes issues associated with Oracle TopLink. It includes the following topics: ■ Section 1, "TopLink Object-Relational Issues" ■ Section 2, "Oracle Database Extensions with TopLink" ■ Section 3, "Allowing Zero Value Primary Keys" ■ Section 4, "Managed Servers on Sybase with JCA Oracle Database Service" ■ Section 5, "Logging Configuration with EclipseLink Using Container Managed JPA" ■ Section 6, "Documentation Accessibility" 1 TopLink Object-Relational Issues This section contains information on the following issues: ■ Section 1.1, "Cannot set EclipseLink log level in WLS System MBean Browser" ■ Section 1.2, "UnitOfWork.release() not Supported with External Transaction Control" ■ Section 1.3, "Returning Policy for UPDATE with Optimistic Locking" ■ Section 1.4, "JDBC Drivers returning Timestamps as Strings" ■ Section 1.5, "Unit of Work does not add Deleted Objects to Change Set" 1.1 Cannot set EclipseLink log level in WLS System MBean Browser Use Oracle Enterprise Manager to set the EclipseLink log level; do not use the WLS System MBean Browser to complete this action. 1.2 UnitOfWork.release() not Supported with External Transaction Control A unit of work synchronized with a Java Transaction API (JTA) will throw an exception if it is released. If the current transaction requires its changes to not be persisted, the JTA transaction must be rolled back. When in a container-demarcated transaction, call setRollbackOnly() on the EJB/session context: @Stateless public class MySessionBean { @Resource SessionContext sc; public void someMethod() { ... 1 sc.setRollbackOnly(); } } When in a bean-demarcated transaction then you call rollback() on the UserTransaction obtained from the EJB/session context: @Stateless @TransactionManagement(TransactionManagementType.BEAN) public class MySessionBean implements SomeInterface { @Resource SessionContext sc; public void someMethod() { sc.getUserTransaction().begin(); ..
    [Show full text]
  • 1 Shounak Roychowdhury, Ph.D
    Shounak Roychowdhury, Ph.D. 10213 Prism Dr., Austin, TX, 78726 || 650-504-8365 || email: [email protected] Profile • Software development and research experience at Oracle and LG Electronics. • Deep understanding of data science methods: machine learning; probability and statistics. • 5 US patents and 40+ peer reviewed publications in international conferences and top refereed journals Research Interests • Published research papers on computational intelligence, neural networks and fuzzy theory, numerical optimization, and natural language processing, and information theory. Education • Ph.D. (Computer Engineering), University of Texas at Austin, Austin, TX, (Dec. 2013) o Dissertation: A Mixed Approach to Spectrum-based Fault Localization Using Information Theoretic Foundations. (Machine Learning in Software Engineering) • M.S. (Computer Science), University of Tulsa, Tulsa, OK, (May 1997) o Thesis: Encoding and Decoding of Fuzzy Rules Patents • Chaos washing systems and a method of washing thereof (US Patent #5,560,230) • System and method for generating fuzzy decision trees (US Patent #7,197,504) • Method for extracting association rules from transactions in a database (U.S. Patent # 7,370,033) • Expediting K-means cluster analysis data mining using subsample elimination preprocessing (U.S. Patent # 8,229,876) • Bayes-like classifier with fuzzy likelihood (U.S. Patent # 8,229,875) Computer Languages • Python, Java, C/C++, MATLAB, R, SQL, PL/SQL, Perl, Ruby, Tcl/Tk Teaching Experience Adjunct Faculty Texas State University 2017- Present Professional Experience Hewlett Packard Enterprise, Austin, TX (Oct 2018 - present) Expert Technologist • Executed software development processes for composable rack team of HPE’s OneView cloud management system. • Developed a Python-based system to test the scalability of OneView connections across multiple layers of Plexxi switches.
    [Show full text]
  • Reference Guide
    Apache Syncope - Reference Guide Version 2.1.9 Table of Contents 1. Introduction. 2 1.1. Identity Technologies. 2 1.1.1. Identity Stores . 2 1.1.2. Provisioning Engines . 4 1.1.3. Access Managers . 5 1.1.4. The Complete Picture . 5 2. Architecture. 7 2.1. Core . 7 2.1.1. REST . 7 2.1.2. Logic . 8 2.1.3. Provisioning . 8 2.1.4. Workflow. 9 2.1.5. Persistence . 9 2.1.6. Security . 9 2.2. Admin UI. 10 2.2.1. Accessibility . 10 2.3. End-user UI. 12 2.3.1. Password Reset . 12 2.3.2. Accessibility . 13 2.4. CLI . 15 2.5. Third Party Applications. 15 2.5.1. Eclipse IDE Plugin . 15 2.5.2. Netbeans IDE Plugin. 15 3. Concepts . 16 3.1. Users, Groups and Any Objects . 16 3.2. Type Management . 17 3.2.1. Schema . 17 Plain . 17 Derived . 18 Virtual . 18 3.2.2. AnyTypeClass . 19 3.2.3. AnyType . 19 3.2.4. RelationshipType . 21 3.2.5. Type Extensions . 22 3.3. External Resources. 23 3.3.1. Connector Bundles . 24 3.3.2. Connector Instance details . 24 3.3.3. External Resource details . 25 3.3.4. Mapping . 26 3.3.5. Linked Accounts . 29 3.4. Realms . 29 3.4.1. Realm Provisioning . 30 3.4.2. LogicActions . 31 3.5. Entitlements. 31 3.6. Privileges . 31 3.7. Roles. 31 3.7.1. Delegated Administration . 32 3.8. Provisioning. 33 3.8.1. Overview. 33 3.8.2.
    [Show full text]
  • Tracking Known Security Vulnerabilities in Third-Party Components
    Tracking known security vulnerabilities in third-party components Master’s Thesis Mircea Cadariu Tracking known security vulnerabilities in third-party components THESIS submitted in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE in COMPUTER SCIENCE by Mircea Cadariu born in Brasov, Romania Software Engineering Research Group Software Improvement Group Department of Software Technology Rembrandt Tower, 15th floor Faculty EEMCS, Delft University of Technology Amstelplein 1 - 1096HA Delft, the Netherlands Amsterdam, the Netherlands www.ewi.tudelft.nl www.sig.eu c 2014 Mircea Cadariu. All rights reserved. Tracking known security vulnerabilities in third-party components Author: Mircea Cadariu Student id: 4252373 Email: [email protected] Abstract Known security vulnerabilities are introduced in software systems as a result of de- pending on third-party components. These documented software weaknesses are hiding in plain sight and represent the lowest hanging fruit for attackers. Despite the risk they introduce for software systems, it has been shown that developers consistently download vulnerable components from public repositories. We show that these downloads indeed find their way in many industrial and open-source software systems. In order to improve the status quo, we introduce the Vulnerability Alert Service, a tool-based process to track known vulnerabilities in software projects throughout the development process. Its usefulness has been empirically validated in the context of the external software product quality monitoring service offered by the Software Improvement Group, a software consultancy company based in Amsterdam, the Netherlands. Thesis Committee: Chair: Prof. Dr. A. van Deursen, Faculty EEMCS, TU Delft University supervisor: Prof. Dr. A.
    [Show full text]
  • Return of Organization Exempt from Income
    OMB No. 1545-0047 Return of Organization Exempt From Income Tax Form 990 Under section 501(c), 527, or 4947(a)(1) of the Internal Revenue Code (except black lung benefit trust or private foundation) Open to Public Department of the Treasury Internal Revenue Service The organization may have to use a copy of this return to satisfy state reporting requirements. Inspection A For the 2011 calendar year, or tax year beginning 5/1/2011 , and ending 4/30/2012 B Check if applicable: C Name of organization The Apache Software Foundation D Employer identification number Address change Doing Business As 47-0825376 Name change Number and street (or P.O. box if mail is not delivered to street address) Room/suite E Telephone number Initial return 1901 Munsey Drive (909) 374-9776 Terminated City or town, state or country, and ZIP + 4 Amended return Forest Hill MD 21050-2747 G Gross receipts $ 554,439 Application pending F Name and address of principal officer: H(a) Is this a group return for affiliates? Yes X No Jim Jagielski 1901 Munsey Drive, Forest Hill, MD 21050-2747 H(b) Are all affiliates included? Yes No I Tax-exempt status: X 501(c)(3) 501(c) ( ) (insert no.) 4947(a)(1) or 527 If "No," attach a list. (see instructions) J Website: http://www.apache.org/ H(c) Group exemption number K Form of organization: X Corporation Trust Association Other L Year of formation: 1999 M State of legal domicile: MD Part I Summary 1 Briefly describe the organization's mission or most significant activities: to provide open source software to the public that we sponsor free of charge 2 Check this box if the organization discontinued its operations or disposed of more than 25% of its net assets.
    [Show full text]
  • Oracle Glassfish Server Application Development Guide Release 3.1.2 E24930-01
    Oracle GlassFish Server Application Development Guide Release 3.1.2 E24930-01 February 2012 This Application Development Guide describes how to create and run Java Platform, Enterprise Edition (Java EE platform) applications that follow the open Java standards model for Java EE components and APIs in the Oracle GlassFish Server environment. Topics include developer tools, security, and debugging. This book is intended for use by software developers who create, assemble, and deploy Java EE applications using Oracle servers and software. Oracle GlassFish Server Application Development Guide, Release 3.1.2 E24930-01 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]
  • IBM Websphere Application Server Community Edition V3.0 Helps Streamline the Creation of Osgi and Java Enterprise Edition 6 Applications
    IBM United States Software Announcement 211-083, dated September 27, 2011 IBM WebSphere Application Server Community Edition V3.0 helps streamline the creation of OSGi and Java Enterprise Edition 6 applications Table of contents 1 Overview 6 Technical information 2 Key prerequisites 8 Ordering information 2 Planned availability date 9 Services 3 Description 9 Order now 6 Product positioning At a glance With WebSphere® Application Server Community Edition V3.0: • Developers can select just the components they need for optimum productivity (using OSGi and a component assembly model). • Developers can get JavaTM Enterprise Edition (Java EE) 6 applications started quickly for no charge. • System administrators are given more deployment and management options. • Organizations can take advantage of world-class, IBM® support options under a socket-based pricing model that can help reduce the cost burden in larger configurations. • You have access to a comprehensive and proven portfolio of middleware products from the WebSphere family. Overview WebSphere Application Server Community Edition V3.0 is the IBM open source- based application server that provides: • Java Enterprise Edition (Java EE) 6 support • An enterprise OSGi application programming model • Java Standard Edition (Java SE) 6 support Version 3 is built on Apache Geronimo and integrated with best-of-breed, open- source technology such as Apache Tomcat, Eclipse Equinox OSGi Framework, Apache Aries, Apache OpenEJB, Apache OpenJPA, Apache OpenWebBeans, and Apache MyFaces. Eclipse-based
    [Show full text]
  • Oracle® Fusion Middleware Solutions Guide for Oracle Toplink 12C (12.1.2) E28610-02
    Oracle® Fusion Middleware Solutions Guide for Oracle TopLink 12c (12.1.2) E28610-02 August 2013 This document describes a number of scenarios, or use cases, that illustrate TopLink features and typical TopLink development processes. Oracle Fusion Middleware Solutions Guide for Oracle TopLink, 12c (12.1.2) E28610-02 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Oracle Application Server Toplink Getting Started Guide, 10G Release 2 (10.1.2) Part No
    Oracle® Application Server TopLink Getting Started Guide 10g Release 2 (10.1.2) Part No. B15902-01 April 2005 Oracle Application Server TopLink Getting Started Guide, 10g Release 2 (10.1.2) Part No. B15902-01 Copyright © 2000, 2005 Oracle. All rights reserved. Primary Author: Jacques-Antoine Dubé Contributing Authors: Rick Sapir, Arun Kuzhimattathil, Janelle Simmons, Madhubala Mahabaleshwar, Preeti Shukla The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]
  • Ultrasparc T2
    © 2014 IJIRT | Volume 1 Issue 6 | ISSN : 2349-6002 MyEclipse-A Rapid Application Development Tool Abstract- MyEclipse 2014 could be a commercially on the • Connectors for databases of Oracle information, market Java EE and Ajax IDE created and maintained by MySQL, Microsoft SQL Server, Sybase the corporate Genuitec, a beginning member of the Eclipse • HTML five mobile tools Foundation. MyEclipse is made upon the Eclipse platform, • REST API cloud tools and integrates each proprietary and open ASCII text file Not gift within the Spring or Bling editions into the event surroundings. Some of the options enclosed (except within the Spring or I. INTRODUCTION Bling editions) are: MyEclipse has 2 primary versions (apart from the "Blue • HTML5 Visual Designer Edition and "MyEclipse Spring Edition cited below): • PhoneGap (Apache Cordova) support knowledgeable and a regular edition. the quality edition • etc. adds information tools, a visible net designer, persistence Present in each editions tools, Spring tools, Struts and JSF tooling, and variety of Some of the options enclosed altogether editions are: different options to the fundamental Eclipse Java • Ajax Tools Developer profile. It competes with the online Tools • Java Persistence Tools: Hibernate, TopLink, Project, that could be a a part of Eclipse itself, however Apache OpenJPA MyEclipse could be a separate project entirely and offers • Spring Framework Tools a distinct feature set. • Apache Struts Designer MyEclipse 2015 Continuous Integration Stream version • JavaServer Faces Designer five (September twenty five, 2014) is currently on the • Application server Connectors market to developers WHO need the newest versions of • JavaServer Pages Development MyEclipse designed with regular updates.
    [Show full text]
  • Full-Graph-Limited-Mvn-Deps.Pdf
    org.jboss.cl.jboss-cl-2.0.9.GA org.jboss.cl.jboss-cl-parent-2.2.1.GA org.jboss.cl.jboss-classloader-N/A org.jboss.cl.jboss-classloading-vfs-N/A org.jboss.cl.jboss-classloading-N/A org.primefaces.extensions.master-pom-1.0.0 org.sonatype.mercury.mercury-mp3-1.0-alpha-1 org.primefaces.themes.overcast-${primefaces.theme.version} org.primefaces.themes.dark-hive-${primefaces.theme.version}org.primefaces.themes.humanity-${primefaces.theme.version}org.primefaces.themes.le-frog-${primefaces.theme.version} org.primefaces.themes.south-street-${primefaces.theme.version}org.primefaces.themes.sunny-${primefaces.theme.version}org.primefaces.themes.hot-sneaks-${primefaces.theme.version}org.primefaces.themes.cupertino-${primefaces.theme.version} org.primefaces.themes.trontastic-${primefaces.theme.version}org.primefaces.themes.excite-bike-${primefaces.theme.version} org.apache.maven.mercury.mercury-external-N/A org.primefaces.themes.redmond-${primefaces.theme.version}org.primefaces.themes.afterwork-${primefaces.theme.version}org.primefaces.themes.glass-x-${primefaces.theme.version}org.primefaces.themes.home-${primefaces.theme.version} org.primefaces.themes.black-tie-${primefaces.theme.version}org.primefaces.themes.eggplant-${primefaces.theme.version} org.apache.maven.mercury.mercury-repo-remote-m2-N/Aorg.apache.maven.mercury.mercury-md-sat-N/A org.primefaces.themes.ui-lightness-${primefaces.theme.version}org.primefaces.themes.midnight-${primefaces.theme.version}org.primefaces.themes.mint-choc-${primefaces.theme.version}org.primefaces.themes.afternoon-${primefaces.theme.version}org.primefaces.themes.dot-luv-${primefaces.theme.version}org.primefaces.themes.smoothness-${primefaces.theme.version}org.primefaces.themes.swanky-purse-${primefaces.theme.version}
    [Show full text]