0 - 15 of 15 tags for eclipse ide

Teradata’s latest and greatest Eclipse offering has been released and is available in the Teradata Developer Exchange download section (Teradata Plug-in for Eclipse) . The 14.01.00 release builds on the 14.00.00 offering by boasting increased functionality.

Teradata’s latest and greatest Eclipse offering has been released and is available in the Teradata Developer Exchange download section (Teradata Plug-in for Eclipse) . The 14.01.00 release builds on the 14.00.00 offering by boasting increased functionality.

Teradata’s latest and greatest Eclipse offering has been released and is available in the Teradata Developer Exchange download section (Teradata Plug-in for Eclipse) . The 14.00.00 release builds on the 13.11.00 offering by boasting increased functionality.

Teradata’s latest and greatest Eclipse offering has been released and is available in the Teradata Developer Exchange download section (Teradata Plug-in for Eclipse) . The 13.11.00 release builds on the 13.10.00 offering by boasting increased functionality.

The iBatis DAO with Web Services Wizard will generate a Web Service from an iBatis SQL Map. The wizard derives all of the information needed from the iBatis SQL Map to generate the following components to create a Web service:

  • DAO (Data Access Object)
  • WSDL (Web Service Definition Language)
  • XSD (XML Schema Definition)
  • Spring Configuration files

The wizard will then use the Eclipse Web Tools Platform (WTP) and Apache Axis to generate the server and client classes for the Web service. The generated classes will include code that supports Query Bands via the Teradata Access Session Manager.

 

The iBatis framework is a lightweight data mapping framework and persistence API. It couples objects with stored procedures or SQL statements using a XML descriptor. The iBatis SQL Map wizard allows you to quickly generate an iBatis SQL map for a given SQL statement or stored procedure.

The Teradata project is an extension of a Java project in Eclipse and it can be created by using the Teradata Project Wizard. This new type of project is set up based on Teradata Standards which can be overridden with preferences. The Teradata project will give you access to Teradata libraries.


In the last article, it was shown how to create Java Bean Wrapper classes that can be called from a Spring Data Access Object (DAO) using the Java Bean Wrapper Wizard.

This article will demonstrate how to tie Java Bean Wrapper classes together using the Spring DAO Wizard to create a reusable data access layer for a business service. Also it will be shown how to create an automated unit test for your DAO.

This will be a series of articles explaining how the Spring framework can be used with the Teradata Plug-in for Eclipse to create a data access layer for your business services. The Java Bean Wrapper wizard allows the user to quickly generate a Java Bean class for a given SQL statement or stored procedure. Also the Wizard has an option to generate a Java Bean which can be run with the Spring Data Access Object (DAO) framework. By calling a generated Java Bean from a DAO, the Bean will have access to the Spring transaction management. Also the Java Wrapper Beans are reusable components which could be used in different DAOs. The Bean Helper Classes can be used as Spring domain objects. Also the Bean will facilitate the support of OUT parameters for stored procedures and multiple result sets inside of a Spring DAO.

This article will show how to setup a project that uses Spring DAOs with the Teradata Plug-in for Eclipse. This article will also show how to create Java Bean Wrapper classes that can be called from a Spring DAO using the Java Bean Wrapper Wizard.

A Teradata Database Java User Defined Function (JUDF) is a program that operates on data stored in relational tables. UDFs allow users to add their own extensions to the Teradata SQL language. JUDFs are implemented as external functions. This means the source is compiled externally to the DBS and kept in Java Archive (JAR) files. These JAR files are installed into the database using stored procedures in the SQLJ database. Once a JAR file is installed a JUDF can be defined to use a Java class and method within the JAR file. The JUDF is executed via a protected mode server separate from the database process. Parameters passed from the DBS are converted to their Java form and the Java return type from the JUDF  is converted back to its DBS form.
 

In the last article, it was shown how a user can create a Java External Stored Procedure (JXSP) that reads SQL using answers sets with the Teradata Plug-in for Eclipse. This article will show how a JXSP can be automatically created that reads SQL. The only thing that is required is a SQL query from the user and the content of the JXSP is automatically generated.

The Java Bean Wrapper wizard allows the user to quickly generate a Java Bean class for a given SQL statement or stored procedure. The Java Bean Wrapper Wizard has an option to create a JXSP that calls the wrapped SQL from the Java Bean.

In the last article, it was shown how a user can create an ant script to automate a build so the user can deploy a JAR and install a DDL for a Java External Stored Procedure (JXSP) outside of Eclipse. This article will show how a user can create a JXSP that reads SQL using answers sets.

Answer sets are extended result sets returned by stored procedures. This is a new feature for JXSPs in the 13.0 version of the Teradata database.

A little over a month ago, we released our plug-in for Eclipse 13.0.  It already rocketed to one of our top downloads, so you likely know about it, but I felt this was something that shouldn't be missed.

Bottom line:  If you don't have it, get it!

In the last article, it was shown how Teradata Plug-in facilitates the process of creating and installing the Java parts and DDL for a Java External Stored Procedure (JXSP) using the JXSP Wizard and Multi-page Editor.

A Java External Stored Procedure (JXSP) is a program written in Java that is kept and executed with in a database server. Java stored procedures are implemented as external stored procedures. This means the source is compiled externally to the DBS and kept in Java Archive (JAR) files. These JAR files are installed into the database using stored procedures in the SQLJ database. Once a JAR file is installed the JXSP can be defined to use the Java class and methods within the JAR file. The JXSP are executed via a protected mode server separate from the database process.