| Statistics |
We have 1813 registered users
The newest registered user is masdark.john
Our users have posted a total of 59 articles |
| Newest Pics |
| No Pics |
| [ Album ] |
|
 |
| Software Tree - Discussion Forums for JDX and NJDX OR-Mappers |
Welcome to phpBB2 Plus 1.52
Your new Forum is waiting for you now,
Have a good time! ^_^
|
|
|
Posted on 12-22-2006 11:43:05 am by dperiwal |
 |
Software Tree Updates JDX OR-Mapper to Version 4.7
New Version Adds MySQL Examples and Enhanced Exception Reporting
Santa Clara, Calif. December 20, 2006: Software Tree has released JDX 4.7, the innovative and versatile Object-Relational Mapping (OR-Mapping) software that significantly accelerates the development of Java applications by eliminating tedious, low-level JDBC/SQL coding for persistence. The new version adds many enhancements based on user feedback and an example directory for the MySQL database.
Following some well-researched KISS (Keep It Simple and Straightforward) principles, JDX offers a simple, fast, dynamic, non-Intrusive, and lightweight O/R Mapping solution. JDX works with most of the popular databases including Oracle, IBM DB2, Microsoft SQL Server, Access, Sybase, and MySQL.
JDX 4.7 also adds support for attributes whose values are automatically initialized by the underlying database system. Additionally, the new version has enhanced trapping and reporting of exceptions.
A free 21-day evaluation version of JDX OR-Mapper is available from Software Tree’s web site at http://www.softwaretree.com.
About Software Tree
Founded in 1997, Software Tree is a Silicon Valley-based technology leader in providing superior software infrastructure that simplifies data integration. Software Tree has licensed its products to leading-edge organizations around the world, such as British Telecom, Xerox, CNT, Los Alamos National Labs, UAB Medical Center, Electronic Arts, and Darden Business School. For more information, visit http://www.softwaretree.com.
Note: JDX and “The KISS OR-Mapper” are trademarks of Software Tree. Java is a registered trademark of Sun Microsystems. All other marks are the property of their respective owners.
|
|
|
|
|
|
Posted on 09-14-2006 06:05:43 pm by administrator |
 |
General:
What should be typical complexity of the database (in terms of tables, their relationships, SPs,...) for JDX to be usefully deployed?
Once you go beyond 10 tables, JDX starts becoming appealing because at that point the complexity of writing and maintaining low level SQL code becomes overwhelming. Also, the following situations would greatly benefit from an OR-Mapping tool like JDX:
· Complex Object structure involving relationships and inheritance
· Rapidly evolving object model where new fields and relationships are being added and modified
· Need to exploit legacy data by reverse-engineering existing schema
In what data access/manipulation situations in our software, does it not make sense to use JDX?
If you have simple object model with only a few classes. Or if you need to deal with your data in a simple tabular structure.
Is there any cost I pay in terms of memory or performance for implementing an O/R layer as compared to a conventional, handcoded database layer?
JDX is very lightweight with a small runtime memory footprint.
JDX uses reflection for object instantiations and setting/getting values. Although reflection does cause some extra overhead compared to hard-coded accessors, the additional cost is not that much because 1) JDX caches most of the reflective metadata for fast reuse, and 2) most modern virtual machines have very efficient handling of reflection calls. So the resulting simplification and modularization of the code because of using JDX is well worth the nominal overhead of reflection. Besides, JDX provides following optimizations:
· Internal connection pooling
· Using prepared statements
· Minimizing database trips
How well do I need to know JDBC, SQL, or XML to use JDX?
JDX does not require you to know any of these technologies. JDX has a small set of simple yet powerful APIs that can effectively be used by application programmers to meet their object persistence needs without knowing any database query language. The mapping specification is done using a simple grammar; there is no need to struggle with complex XML files.
Does JDX generate JDBC specific source code?
JDX does not do any source code or bye code generation. It’s very dynamic in nature - all the required SQL is generated at runtime. JDX does not require your persistent classes to inherit from any particular base class; it does not require them to implement any specific interfaces. You have all the flexibility in defining your persistent classes without worrying about the data access aspects.
How easy it is to use JDBC transactions? Do we need to code extra for this?
JDX provided support for implicit and explicit transactions, where you can combine multiple operations in one database transaction. JDX can also work in the context of an external transaction manager working in an application server environment.
Which all databases can be used with JDX?
JDX uses JDBC interface for optimal performance and can be used with any database for which JDBC provider is available. For example, JDX can be used with Oracle, IBM DB2, Microsoft SQL Server, MySQL, MS Access, etc. The software comes with many example directories showing the usage of JDX with various databases.
What type of reference material comes with JDX?
The software comes with extensive documentation in the form of detailed user manual, working examples, API specifications, and useful tutorials. ANTt scripts are available for running the examples.
Troubleshooting:
ClassNotFoundException
This exception may show up in many situations. Here are some suggestions to solve the problem:
• First of all, make sure that %JX_HOME%\lib\jxclasses.jar and
%JX_HOME%\lib\jdxtools.jar are in your CLASSPATH.
• If you are invoking JDXStudio from the desktop icon (i.e., not from the command
line), make sure that the CLASSPATH environment variable is set for the JDBC driver
class and the object classes used in defining mapping.
• Make sure that you have compiled (javac) your java source files before executing or
using them.
• Make sure that you have recompiled your java source files after modifying them. This is a very common source of many different problems.
• If your needed java classes are created in the current directory (“.”), make sure that it is in the CLASSPATH (either “.” or the full path of the current directory).
• If a class belongs to a package and you are using the name of that class in a JDX API call, the fully qualified class names should be used.
• In the object-relational mapping specification, a packaged class should be specified in its fully qualified form.
No Suitable Driver found
Make sure that you have specified the needed JDBC drivers (through jdbc.drivers property) on the command line before starting your JDX application. For example, if MyServer uses JDX to connect to a Sybase server with jConnect driver then it should be started as following:
java -Djdbc.drivers= com.sybase.jdbc.SybDriver MyServer <other arguments>
Equally important is to make sure that the location of the base directory for the needed JDBC driver is in your CLASSPATH.
Non-initialized class for JDX: foo
Make sure that ‘foo” is part of object space - that is, it is configured in the object-relational mapping specification.
If “foo” is part of a package, specify it in its fully qualified form (e.g., “package1.part2.foo”).
When I do object query through JDXDemo, I don’t see all the objects even though I can see the corresponding records in the database. Why?
Well, make sure that Max Objects is set to the desired number (default is 3; use -1 for all objects). Also check if the Search Criteria might have filtered the objects you are expecting to see.
In JDXDemo, I see different results between object query and SQL statement. How can it be explained?
First of all make sure that the table name corresponding to the object class is same as the table name you are using for your direct SQL stmt.
Secondly, please note that Search Criteria box in JDXDemo applies only to the object query. An SQL stmt should have its own WHERE clause if needed. So, you should verify that equivalent filtering of objects/rows is happening in those methods.
Thirdly, if the database has multiple rows with same values for the primary key attributes (columns), JDX will return only one corresponding object whereas SQL Stmt may return all of them. Normally this should not happen if the database enforces primary/unique key constraints properly. Make sure that you have identified the right set of attributes (columns) for the primary key specification.
Diagnostic help available?
JDX can run at different DEBUG_LEVELs ranging from 0 (most verbose) to 5 (no debug information). At DEBUG_LEVEL=3, you can see all the SQL statements issued by JDX. By setting appropriate DEBUG_LEVEL in the JDXURL string, you can diagnose most problems easily.
|
|
|
|
|
|
Posted on 04-24-2006 11:58:35 am by dperiwal |
 |
Software Tree Updates NJDX, The KISS OR-Mapper™ for .NET
NJDX Version 1.5 Supports Visual Studio 2005
Santa Clara, Calif. April 17, 2006: Software Tree has announced NJDX 1.5, the innovative and versatile Object-Relational Mapping (OR-Mapping) software that significantly accelerates the development of .NET applications by eliminating tedious, low-level ADO.NET/SQL coding for persistence. The new version provides tight integration with Microsoft’s Visual Studio 2005 (VS2005). NJDXStudio, the Visual Studio add-In, makes it a breeze to perform O/R Mapping related configuration and verification tasks like reverse engineering of object model from an existing relational schema and vice-versa. In addition to enhanced type compatibility with the .NET framework, the new release of this database-agnostic OR-Mapper also provides many new examples of stored procedure integration.
Following some well-researched KISS (Keep It Simple and Straightforward) principles, NJDX offers a simple, fast, dynamic, non-Intrusive, and lightweight O/R Mapping solution. NJDX works with most of the popular databases including Microsoft SQL Server, Oracle, IBM DB2, and Access.
Now, with just a few button clicks, one can create a database schema from an object model (forward-engineering) or generate C# classes from an existing database schema (reverse-engineering) from right within VS2005. The NJDX user manual, the mapping grammar, the API documentation, and many demos have also been integrated with VS2005. All this functionality is also available with VS2003.
To illustrate the simple and intuitive integration of database stored procedures within NJDX OR-Mapping framework, many new examples involving in/out parameters and result sets have been included in the package.
"NJDX allows me to focus on the business objects rather than on the low level SQL, “ says David Lypka, an independent .NET consultant. “NJDX facilitates rapid experiments with different variations of the database design with a minimum amount of work. I designed my Corporate Tax application without even inspecting the underlying SQL. This high-performance O/R Mapper is working great in my ASP.NET 2.0 Web application.”
“Thanks to great feedback from early evaluators, we have rapidly evolved our OR-Mapping technology and associated tools to meet most common data integration needs of .NET developers, “ says Damodar Periwal, President & CEO of Software Tree. “On the heels of providing an extremely simplified implementation of the data access layer (DAL) for the .NET Pet Shop application, we are proud to present NJDX 1.5 supporting Visual Studio 2005.“
A free 30-day evaluation version of NJDX OR-Mapper is available from Software Tree’s web site at http://www.softwaretree.com.
About Software Tree
Founded in 1997, Software Tree is a Silicon Valley-based technology leader in providing superior software infrastructure that simplifies data integration. Software Tree has licensed its products to leading-edge organizations around the world, such as British Telecom, Xerox, CNT, Los Alamos National Labs, UAB Medical Center, Electronic Arts, and Darden Business School. For more information, visit http://www.softwaretree.com.
Note: NJDX and The KISS OR-Mapper are trademarks of Software Tree. .NET is a trademark of Microsoft. All other marks are the property of their respective owners.
|
|
|
|
|
|
Posted on 11-24-2005 09:32:23 am by dperiwal |
 |
Software Tree Introduces NJDX, The KISS OR-Mapper™ for .NET
NJDX Drives The Complexity Out Of .NET/Database Integration Efforts
Free Licenses Available For Limited Time
Santa Clara, Calif. November 21, 2005: Software Tree has introduced today the NJDX 1.0 Object-Relational Mapper (OR-Mapper), which dramatically reduces the complexity of developing modern object-oriented applications on the .NET platform by eliminating the painful need to write huge amounts of complicated infrastructure code for data integration. Adhering to some well thought-out KISS (Keep It Simple and Straightforward) principles, NJDX provides smooth integration with popular databases including Microsoft SQL Server, Oracle, IBM DB2, and Microsoft Access. NJDX has also been tightly integrated with Visual Studio .NET and can be used with any CLR-based language including C#, VB.NET, and J#.
NJDX provides a high-performance, user-friendly, and practical OR-Mapping solution for seamlessly bridging the gap between the .NET object model and SQL relational model. By eliminating endless lines of tedious ADO.NET/OleDB/SQL code, NJDX boosts developer productivity and reduces maintenance hassles.
The KISS principles that have served as the guiding philosophy behind development of NJDX include:
· Solve the most important problem in the simplest possible way
· Don’t make the solution more complex than the original problem
· Be completely non-intrusive to the object model
· Make it easy to define, modify, comprehend, and share the mapping specification
· Avoid source code generation for data access
· No mind reading
· Expose small number of simple and consistent APIs
· Optimize data access logic automatically
· Keep the internal implementation simple, extensible, and efficient
· Offer intuitive tools to deal with object models, database schema, and mapping
· Provide a straightforward installer, lucid documentation, and readymade examples
“NJDX is an amazingly simple and intuitive OR-Mapper,” says Bill Ryan, a Microsoft MVP (Most Valuable Professional). “I'm extremely impressed with just about every facet of it. NJDX is powerful, flexible, easy-to-use, performant, reliable, and most importantly, it fits seamlessly into any architectural model.”
“Software Tree has been a pioneer in the field of Object-Relational Mapping technology,” comments Damodar Periwal, President & CEO of Software Tree. “In March 1998, we released JDX™, our innovative and patented OR-Mapping product for the Java platform. .NET developers have long been clamoring for a fast, flexible, and practical OR-Mapping solution. We are delighted to present NJDX, the KISS OR-Mapper for .NET, to help those developers with a versatile and efficient data integration product. Software Tree now has a unique set of lightweight OR-Mapping products (JDX and NJDX), which share a common proven architecture and present similar interfaces for both the Java and the .NET worlds.”
Availability and Pricing
NJDX 1.0 software is available now. To celebrate it’s entry into the .NET market, Software Tree is offering free licenses of NJDX for a limited time only. Please visit the company website for more details including demos, a white paper on the KISS principles, and a free evaluation download of NJDX.
About Software Tree
Founded in 1997, Software Tree is a Silicon Valley-based technology leader in providing superior software infrastructure that simplifies data integration. Software Tree has licensed its products to leading-edge organizations around the world, such as British Telecom, Xerox, CNT, Los Alamos National Labs, UAB Medical Center, Electronic Arts, and Darden Business School. For more information, visit http://www.softwaretree.com.
Note: NJDX, JDX, and The KISS OR-Mapper are trademarks of Software Tree. .NET is a trademark of Microsoft. Java is a trademark of Sun Microsystems. All other marks are the property of their respective owners.
|
|
|
|
|
 |
| Who is Online |
|
In total there are 2 users online :: 0 Registered, 0 Hidden and 2 Guests
None
[ View complete list ]
Most users ever online was 42 on Sun Aug 24, 2008 4:05 am |
|
Calendar
|
 | February 2012 |  |
| Mo |
Tu |
We |
Th |
Fr |
Sa |
So |
| |
|
1 |
2 |
3 |
4 |
5 |
| 6 |
7 |
8 |
9 |
10 |
11 |
12 |
| 13 |
14 |
15 |
16 |
17 |
18 |
19 |
| 20 |
21 |
22 |
23 |
24 |
25 |
26 |
| 27 |
28 |
29 |
|
| No users have a birthday today |
| Users with a birthday within the next 7 days: !!Wrambubmefnab (32), AceT (32), AdrianoMano (36), AlexEU (31), AnaebSpone (27), andrewclumbs (46), BokWaitteeBot (32), BoodadetaNoth (37), dogitgod (38), equipamma (34), GaillaCeree (34), gorodinkey (33), Greeneuct (38), hiceUtenttoop (26), johneglienradb (41), NalsleltKex (35), nincDiolf (34), NucemWecilu (40), olgaevkud (40), OlimpineszaidynesX (36), Oppottenjoync (37), Pieliflenty (33), Poorpossy3464 (50), Quathtadway (30), Shiguegriedge (34), sloclaips (45), Soaltyspoot (34), SpeemiaxImige (44), Spommadotbabe (51), Sussanterranvik (34), Tauganige (32), UserfromLV (37), Ventmaiseemix (39) |
| Upcoming Events: |
| None |
| Last Seen |
| In total 69 user have visited this site today :: 0 Registered, 0 Hidden and 69 Guests, 4 of them within the last hour. |
| Nogblobia on Thu Feb 02, 2012 4:02 am |
| bifssleerehip on Sun Jan 15, 2012 11:44 pm |
| dperiwal on Mon Jan 09, 2012 8:13 am |
| stydayelalt on Mon Jan 09, 2012 7:53 am |
| ReseEvini on Sun Jan 08, 2012 4:50 am |
|