LazyBoy SQL

The LazyBoy SQL component acts like a medium via which a Java code can communicate with a Database. It assists in the execution of simple SQL statements like the following on single Tables:

1. Insert.
2. Select.
3. Update.
4. Delete.

Currently, it has been configured for MySQL, MS SQL and Oracle.

This component is designed so as to facilitate the execution of simple SQL statements currently and is not in the league of other powerful components like Hibernate. It is an attempt to avoid the coding of the Database layer in projects or applications where complicated SQL statements are not involved.

Let me know your feedback. You can download the JAR, Documentation and Examples from the following location:

LazyBoy SQL v1.0

Known Issues and Limitations:

1. The LazyBoy SQL component attempts to minimize the Development with respect to communications with the Database. However, it does not cover all types of simple or complex SQL Statements / Queries.
2. It carries out functions like Insert, Select, Update and Delete only.
3. It carries out functions on single Database Tables for an operation and not multiple Database Tables.
4. The Where clause supports comparisons on the basis of Equality only and not other expressions like Less Than, Greater Than, Not Equal To, etc.
5. The LazyBoy SQL component is dependent on the Conversion Box component when Maps and Java Objects are involved. Thus, the issues and limitations in the Conversion Box will be a factor in LazyBoy SQL for these scenarios.

Messenger Box

The Messenger Box component acts as a means of communication between two entities that use Web Services for the same. The component accepts XMLs, Maps and JSONs as inputs and can return the same as outputs for Web Service calls.

Let me know your feedback. You can download the JAR, Documentation and Examples from the following location:

Messenger Box v1.0

Known Issues and Limitations:

1. The Messenger Box component is dependent on the Conversion Box component when Maps and JSONs are involved either in the Request or the Response. Thus, the issues and limitations in the Conversion Box will be a factor in the Messenger Box for these scenarios.
2. If the keys contain JSON specific symbols (like ‘:’) in them, there is a chance that the resultant JSON may not be generated correctly.

Conversion Box

The Conversion Box component works with the idea of converting data from one structure to another. It can be used to carry out conversions between Maps, JSONs, XMLs and Java Objects. It also converts Lists of Maps embedded within them to their corresponding equivalent. Also, the hierarchy within the data structure is maintained.

Additionally, the key can also be substituted with another value in the final conversion if a Map containing the value with which it can be substituted with, is provided. While the conversion is in progress, the component will refer to this Map and substitute all the keys with the value mentioned in the Map.

It offers the following conversions:

1. Map to JSON.
2. Map to XML.
3. Map to Java Object.
4. JSON to Map.
5. JSON to XML.
6. JSON to Java Object.
7. XML to Map.
8. XML to JSON.
9. XML to Java Object.
10. Java Object to Map.
11. Java Object to JSON.
12. Java Object to XML.

Let me know your feedback. You can download the JAR, Documentation, Release Notes and Examples from the following locations:

Conversion Box v1.1

Conversion Box v1.0

Known Issues and Limitations:

1. All Lists embedded within a data structure need to be Lists of Maps and not just Lists.
2. Special characters are not escaped or handled.
3. In case of conversions where Java Objects are involved, Maps and Lists of Maps within a Java Object are supported. However, Java Objects within Maps or Lists are not supported.
4. Every key in the data structure (nested or not) needs to be unique.