I like this idea. Would this be a front end to things like Castor and Digester, or would they move to this component?

Also, do you already have a codebase you have in mind for this?

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net

P.S. Out of curiosity, are you familiar with any open source EDI transformation code?

[EMAIL PROTECTED] wrote:

-----------------------------------------------------
Commons Data Transformer - Sandbox Component proposal
-----------------------------------------------------

Data Transformation is essential part of day to day
computing, whether it is xml-to-xml transformation,
xml-to-java transformation, edi-to-java transformation
etc.

Lets take a simple example of xml-to-java
transformation (or vice versa)
There are several implementations : Castor, JAXB to
name a few. Usage of these introduces dependencies on
the implementation. This immediately draws similarity with commons-logging.
Commons-Logging acts as a Adapter between the user code
and the implementation, freeing the user code from
Log4J and J2SE Logging imports. (Thus allowing plug and
play logging at the code level.)


A similar approach for Data transformations in general
(xml-to-java objects in particular) is highly
desirable. Programmers like to access in memory Java
object representations of external data.

Hence I propose a Commons "Data Transformer", freeing
the user from implementation specific imports. I
envision Commons Data transformer will perform
"x-to-java" (direct transform) and "java-to-x" (inverse
transform) transformations.

PS : It is interesting to note that certain kinds of
Configuration are really a subset of data
transformation.

Thanks,
Srikanth



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to