You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "bert.robben (JIRA)" <tu...@ws.apache.org> on 2007/07/31 09:17:52 UTC
[jira] Created: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Snapshot mapping framework to convert DataObjects to and from Java objects
--------------------------------------------------------------------------
Key: TUSCANY-1493
URL: https://issues.apache.org/jira/browse/TUSCANY-1493
Project: Tuscany
Issue Type: New Feature
Components: Java SDO Implementation
Reporter: bert.robben
We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
- A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
- A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
- We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "bert.robben (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
bert.robben updated TUSCANY-1493:
---------------------------------
Attachment: sdo.zip
sdo-snapshot.zip
First attachment contains the main interfaces and implementation classes for snapshots, and mappers.
Second attachment contains the hibernate integration.
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Attachments: sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539055 ]
Kelvin Goodson commented on TUSCANY-1493:
-----------------------------------------
Kris, thanks for this. It's going to be a couple of days before I can get to looking at it, but I look forward to doing so.
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: agfasdo.tar.gz, sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531727 ]
Kelvin Goodson commented on TUSCANY-1493:
-----------------------------------------
I've been going through the files in preparation for putting them into the code base somewhere, and have been adding apache license headers to the files that have no headers, on the basis of the license you granted when attaching the zip files. There are about 10 files in the archives which have Agfa copyright headers in them (e.g. ExtendablePropertyAccessBuilder.java), saying that . ...
// THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF
// Agfa-Gevaert Group
I don't feel it's right for me to remove those headers, although I guess that would be in the spirit of the submission. Could you please search for files with similar headers to that file, fix the headers as you see fit, and resubmit any files you wish to be included in the submission.
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549058 ]
Kelvin Goodson commented on TUSCANY-1493:
-----------------------------------------
I've just made some observations on the tuscany-user mailing list which should appear in the mailing list archives shortly, under the thread that contains http://www.mail-archive.com/tuscany-user@ws.apache.org/msg02162.html
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: agfasdo.tar.gz, sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529846 ]
Kelvin Goodson commented on TUSCANY-1493:
-----------------------------------------
Bogdan, it's not in the code base yet. I'm looking at it now.
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544782 ]
Kelvin Goodson commented on TUSCANY-1493:
-----------------------------------------
Kris,
I downloaded and manually installed the eclipse core and osgi dependencies at the appropriate level into my maven repository. Currently I'm getting more eclipse missing classes such as IExtension, which I guess is because the eclipse artifacts have transitive dependencies which would be known if maven had installed the artifacts itself. I'm guessing you have a repository in your settings.xml file for maven that can resolve these artifacts automatically. I can continue to dig out jars and manually install them into my repo until all requirements are resolved, but if you happen to be able to point me at a maven repo to do the job automatically that would be great, thanks.
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: agfasdo.tar.gz, sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531744 ]
Kelvin Goodson commented on TUSCANY-1493:
-----------------------------------------
I've added as much as I can to my sandbox in commit http://svn.apache.org/viewvc?rev=581184&view=rev
I've not added anything from the hibernate integration archive due to the licensing issues alluded to earlier.
Two of the files with header issues are part of the generic snapshot code, so they are missing from what I have committed (see the commit comment in http://svn.apache.org/viewvc?rev=581184&view=rev)
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "ant elder (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516672 ]
ant elder commented on TUSCANY-1493:
------------------------------------
This seems pretty cool, in fact just yesterday on the user list another user was asking for exactly this functionality.
There is an issue with the hibernate code unfortunately, it uses the LGPL license and we're not able to uses any code under that license in an Apache project (for the legal details see: http://www.apache.org/legal/3party.html). We can use the framework, just the code that directly references hiberbnate classes needs to be kept separate.
Whats going to be easiest way to progress this, you say you're going to be adding more to it over the next days, should we wait for that before committing this somewhere or would it be easier to have it committed somewhere?
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Attachments: sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Kris De Waele (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kris De Waele updated TUSCANY-1493:
-----------------------------------
Attachment: agfasdo.tar.gz
The attachement agfasdo.tar.gz contains the full source code of our custom sdo implementation, including our data mapping extension.
The included maven pom file might need some tweaking to get it to build.
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: agfasdo.tar.gz, sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Bogdan Stroe (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529793 ]
Bogdan Stroe commented on TUSCANY-1493:
---------------------------------------
Are there any updates on this issue? Is this feature included in the nightly builds? Is it documented somewhere?
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "bert.robben (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516679 ]
bert.robben commented on TUSCANY-1493:
--------------------------------------
I didn't know about the license stuff and Hibernate. I'm sorry about that.
I'll post some more stuff in the next days, so I should wait before committing this somewhere.
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Attachments: sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531723 ]
Kelvin Goodson commented on TUSCANY-1493:
-----------------------------------------
Hi, Thanks for the code. Sorry to take a while to get back to you. I have revisited this a few times to make sure I have a reasonably good feel for it before commenting. I'd love to be able to execute a test program to answer some of the question I have about the code, or at least to see some code that exercises it. Looking at the SnapshotSerializer code I think I'm OK to make the inference that the Type and Property classes used in there are your implementation classes of the SDO concepts, although of course that implementation code is not available. So, given that assumption, I understand that the implementation of your opaque snapshot representation is based on SDOs. It would be interesting to understand the issues you have encountered in using the code; for example, if there are any lossy round-trip transformations that cause problems. It would be great to work towards getting some code running inside the Tuscany code base; it would also be helpful if you could put some more words around any key design concepts and the issues you have encountered and solved, or have yet to solve. How should we proceed? Clearly the code is broken at the moment, given the missing aspects, so it's not suitable for including in the nightly build. I can put it in my sandbox, or I could set up another project under the SDO project, but not include it in the main build.
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1493) Snapshot mapping framework to
convert DataObjects to and from Java objects
Posted by "Kris De Waele (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kris De Waele updated TUSCANY-1493:
-----------------------------------
Kelvin,
apparently there is no public maven repo that hosts these artifacts.
We added the eclipse artifacts to our own repo using (something almost identical to) the maven eclipse plugin ( http://maven.apache.org/plugins/maven-eclipse-plugin/to-maven-mojo.html )
> Snapshot mapping framework to convert DataObjects to and from Java objects
> --------------------------------------------------------------------------
>
> Key: TUSCANY-1493
> URL: https://issues.apache.org/jira/browse/TUSCANY-1493
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SDO Implementation
> Reporter: bert.robben
> Fix For: Java-SDO-Next
>
> Attachments: agfasdo.tar.gz, sdo-snapshot.zip, sdo.zip
>
>
> We're developing 3-tier applications with a swing client, JBoss app server and a couple of databases in the back-end. We use sdo as mechanism to exchange data between our client and our server. On the server side we have a fairly complex implementation based partially on Hibernate pojo's, partially on an inhouse legacy persistency system. The legacy part (although written in Java) is very hard to change. In this environment we often need to convert between data objects and server side objects (typically, but not always at a transition from server to client or vice versa).
> To support this we developed a mapping framework that allows us to convert data between SDO and ordinary Java objects. This framework defines a number of important concepts.
> - A snapshot is an opaque collection of structured data at a given moment in time. It is opaque in the sense that the data inside can't be accessed directly.
> - A Mapper is an interface that defined how data can be accessed from an object. We have implementations for SDO DataObjects, normal Java POJO's (following java beans convention). hibernate pojos, and support for customizing this to access any kind of object (as we need for instance for our legacy objects).
> - We defined a DataAccessService (sorry for the confusing name) that given a mapper and some objects can create a snapshot. Given a snapshot and a mapper it can instantiate new objects. As such we can convert data to and from data objects very easily.
> This framework is part of our in-house developed implementation of the SDO spec. We want to share our code and experience with the open-source community. As such, Frank Budinsky proposed that we make JIRA request for this to start the discussion.
> I'll attach the core classes for this feature to this JIRA. At this moment I'm not making the entire code available because we implemented more than one additional feature (I'll add some more JIRA over the next days) and I'd like to have a more focussed discussion. Also, at this moment in time some smaller parts of implementation (for instance the hibernate integration) are still implemented as a specialization of our SDO implementation. As such they can't be built outside of the rest of our application (which is not open-sourced). However this is just a matter of finding enough time to move them to our sdo component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org