You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Musall Maik <ma...@selbstdenker.ag> on 2016/08/03 18:53:14 UTC
EOModel importer testing
Hi all,
I've got a rather large project to migrate from EOF to Cayenne, and in order to eliminate the manual cleanup steps I'd have to do after each conversion attempt until I'm ready for the final run, I thought I could have a look and try to improve the EOModel importer instead of wasting time fiddling with my one project.
To that end, what is the usual procedure to test changes made against the modeler? Can I run it from within Eclipse? Or do I need to mvn install every time I changed something? (Note that I'm new to both Cayenne and Maven.)
How am I supposed to contribute the changes? Pull request against the github mirror? The website [1] suggest submitting a patch, but that feels so old-school, and the website still explains how to create a patch with subversion, so I guess that's no longer up to date anyway?
Thanks
Maik
[1] https://cayenne.apache.org/submit-patch.html
Re: EOModel importer testing
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 4/08/2016 4:53am, Musall Maik wrote:
> How am I supposed to contribute the changes? Pull request against the github mirror? The website [1] suggest submitting a patch, but that feels so old-school, and the website still explains how to create a patch with subversion, so I guess that's no longer up to date anyway?
Thanks for the heads up. I fixed that page to point to git and github.
http://cayenne.apache.org/how-can-i-help.html
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: EOModel importer testing
Posted by Andrus Adamchik <an...@objectstyle.org>.
Hi Maik,
Glad to hear you are finally trying out Cayenne! :)
>> To that end, what is the usual procedure to test changes made against the
>> modeler? Can I run it from within Eclipse? Or do I need to mvn install
>> every time I changed something? (Note that I'm new to both Cayenne and
>> Maven.)
Yes, you can run Modeler from Eclipse without reassembly. Just use the cross-platform Main class (org.apache.cayenne.modeler.Main). There are no special arguments or any other tricks.
Andrus
> On Aug 3, 2016, at 9:57 PM, John Huss <jo...@gmail.com> wrote:
>
> A pull request is preferred now.
>
> The biggest problem with the importer that I recall was that it was
> completely unaware of prototypes (ERPrototypes) so that basically made it
> worthless for me. Are you having that problem? Reverse-engineering from
> the database itself can work well as an alternative if your names use
> underscores.
>
> John
>
> On Wed, Aug 3, 2016 at 1:53 PM Musall Maik <ma...@selbstdenker.ag> wrote:
>
>> Hi all,
>>
>> I've got a rather large project to migrate from EOF to Cayenne, and in
>> order to eliminate the manual cleanup steps I'd have to do after each
>> conversion attempt until I'm ready for the final run, I thought I could
>> have a look and try to improve the EOModel importer instead of wasting time
>> fiddling with my one project.
>>
>> To that end, what is the usual procedure to test changes made against the
>> modeler? Can I run it from within Eclipse? Or do I need to mvn install
>> every time I changed something? (Note that I'm new to both Cayenne and
>> Maven.)
>>
>> How am I supposed to contribute the changes? Pull request against the
>> github mirror? The website [1] suggest submitting a patch, but that feels
>> so old-school, and the website still explains how to create a patch with
>> subversion, so I guess that's no longer up to date anyway?
>>
>> Thanks
>> Maik
>>
>> [1] https://cayenne.apache.org/submit-patch.html
>>
>>
Re: EOModel importer testing
Posted by Andrus Adamchik <an...@objectstyle.org>.
While I don't have any EOModels to test this, the code looks great to me. In fact I just applied to PR.
Andrus
> On Aug 5, 2016, at 5:19 PM, Musall Maik <ma...@selbstdenker.ag> wrote:
>
> All right,
>
> I think I improved a few minor things, and create a first pull request. I'd like feedback on whether or not this is going in the right direction.
>
> https://github.com/apache/cayenne/pull/103
>
> Thanks
> Maik
>
>> Am 04.08.2016 um 18:07 schrieb Mike Kienenberger <mk...@gmail.com>:
>>
>> Yes, please continue to improve it. I first used it back in 2003, and
>> it's still being used 13 years later.
>>
>> On Thu, Aug 4, 2016 at 4:38 AM, Musall Maik <ma...@selbstdenker.ag> wrote:
>>>
>>>> Am 04.08.2016 um 01:26 schrieb Aristedes Maniatis <ar...@maniatis.org>:
>>>>
>>>> On 4/08/2016 5:27am, Musall Maik wrote:
>>>>> There's still a bunch of details to fix, like TEXT columns (postgresql clobs) ending up as varchar with no length, the parser not being able to cope with unicode umlauts in documentation (similar to CAY-1291 which is also still unsolved), and more.
>>>>
>>>> Perhaps I'm telling you the obvious, but don't overlook the ability to write xslt or just regex against the XML model file in order to tidy up some things.
>>>>
>>>
>>> Of course. But you know, we just had the "From EOF to Cayenne" topic at the WOWODC conference in June, and I guess (hope) a few more people might try to move to Cayenne in the near future. So, the benefit of any work put into the model importer instead of run-once-on-my-project tools is multiplied by the number of users that are using the importer.
>>>
>>> Maik
>>>
>
Re: EOModel importer testing
Posted by Musall Maik <ma...@selbstdenker.ag>.
All right,
I think I improved a few minor things, and create a first pull request. I'd like feedback on whether or not this is going in the right direction.
https://github.com/apache/cayenne/pull/103
Thanks
Maik
> Am 04.08.2016 um 18:07 schrieb Mike Kienenberger <mk...@gmail.com>:
>
> Yes, please continue to improve it. I first used it back in 2003, and
> it's still being used 13 years later.
>
> On Thu, Aug 4, 2016 at 4:38 AM, Musall Maik <ma...@selbstdenker.ag> wrote:
>>
>>> Am 04.08.2016 um 01:26 schrieb Aristedes Maniatis <ar...@maniatis.org>:
>>>
>>> On 4/08/2016 5:27am, Musall Maik wrote:
>>>> There's still a bunch of details to fix, like TEXT columns (postgresql clobs) ending up as varchar with no length, the parser not being able to cope with unicode umlauts in documentation (similar to CAY-1291 which is also still unsolved), and more.
>>>
>>> Perhaps I'm telling you the obvious, but don't overlook the ability to write xslt or just regex against the XML model file in order to tidy up some things.
>>>
>>
>> Of course. But you know, we just had the "From EOF to Cayenne" topic at the WOWODC conference in June, and I guess (hope) a few more people might try to move to Cayenne in the near future. So, the benefit of any work put into the model importer instead of run-once-on-my-project tools is multiplied by the number of users that are using the importer.
>>
>> Maik
>>
Re: EOModel importer testing
Posted by Mike Kienenberger <mk...@gmail.com>.
Yes, please continue to improve it. I first used it back in 2003, and
it's still being used 13 years later.
On Thu, Aug 4, 2016 at 4:38 AM, Musall Maik <ma...@selbstdenker.ag> wrote:
>
>> Am 04.08.2016 um 01:26 schrieb Aristedes Maniatis <ar...@maniatis.org>:
>>
>> On 4/08/2016 5:27am, Musall Maik wrote:
>>> There's still a bunch of details to fix, like TEXT columns (postgresql clobs) ending up as varchar with no length, the parser not being able to cope with unicode umlauts in documentation (similar to CAY-1291 which is also still unsolved), and more.
>>
>> Perhaps I'm telling you the obvious, but don't overlook the ability to write xslt or just regex against the XML model file in order to tidy up some things.
>>
>
> Of course. But you know, we just had the "From EOF to Cayenne" topic at the WOWODC conference in June, and I guess (hope) a few more people might try to move to Cayenne in the near future. So, the benefit of any work put into the model importer instead of run-once-on-my-project tools is multiplied by the number of users that are using the importer.
>
> Maik
>
Re: EOModel importer testing
Posted by Musall Maik <ma...@selbstdenker.ag>.
> Am 04.08.2016 um 01:26 schrieb Aristedes Maniatis <ar...@maniatis.org>:
>
> On 4/08/2016 5:27am, Musall Maik wrote:
>> There's still a bunch of details to fix, like TEXT columns (postgresql clobs) ending up as varchar with no length, the parser not being able to cope with unicode umlauts in documentation (similar to CAY-1291 which is also still unsolved), and more.
>
> Perhaps I'm telling you the obvious, but don't overlook the ability to write xslt or just regex against the XML model file in order to tidy up some things.
>
Of course. But you know, we just had the "From EOF to Cayenne" topic at the WOWODC conference in June, and I guess (hope) a few more people might try to move to Cayenne in the near future. So, the benefit of any work put into the model importer instead of run-once-on-my-project tools is multiplied by the number of users that are using the importer.
Maik
Re: EOModel importer testing
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 4/08/2016 5:27am, Musall Maik wrote:
> There's still a bunch of details to fix, like TEXT columns (postgresql clobs) ending up as varchar with no length, the parser not being able to cope with unicode umlauts in documentation (similar to CAY-1291 which is also still unsolved), and more.
Perhaps I'm telling you the obvious, but don't overlook the ability to write xslt or just regex against the XML model file in order to tidy up some things.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: EOModel importer testing
Posted by Musall Maik <ma...@selbstdenker.ag>.
Hi John,
I tried the reverse-engineering first, but as the database is case insensitive regarding names, almost all entities and attributes came out without the camel casing that I use in the project. Correcting that by hand for 169 entities with a huge number of attributes isn't an option, so I tried the EOModel import. I only use two enum prototypes, both of which aren't Wonder prototypes, so that left far less stuff to clean up.
There's still a bunch of details to fix, like TEXT columns (postgresql clobs) ending up as varchar with no length, the parser not being able to cope with unicode umlauts in documentation (similar to CAY-1291 which is also still unsolved), and more.
Maik
> Am 03.08.2016 um 20:57 schrieb John Huss <jo...@gmail.com>:
>
> A pull request is preferred now.
>
> The biggest problem with the importer that I recall was that it was
> completely unaware of prototypes (ERPrototypes) so that basically made it
> worthless for me. Are you having that problem? Reverse-engineering from
> the database itself can work well as an alternative if your names use
> underscores.
>
> John
>
> On Wed, Aug 3, 2016 at 1:53 PM Musall Maik <ma...@selbstdenker.ag> wrote:
>
>> Hi all,
>>
>> I've got a rather large project to migrate from EOF to Cayenne, and in
>> order to eliminate the manual cleanup steps I'd have to do after each
>> conversion attempt until I'm ready for the final run, I thought I could
>> have a look and try to improve the EOModel importer instead of wasting time
>> fiddling with my one project.
>>
>> To that end, what is the usual procedure to test changes made against the
>> modeler? Can I run it from within Eclipse? Or do I need to mvn install
>> every time I changed something? (Note that I'm new to both Cayenne and
>> Maven.)
>>
>> How am I supposed to contribute the changes? Pull request against the
>> github mirror? The website [1] suggest submitting a patch, but that feels
>> so old-school, and the website still explains how to create a patch with
>> subversion, so I guess that's no longer up to date anyway?
>>
>> Thanks
>> Maik
>>
>> [1] https://cayenne.apache.org/submit-patch.html
>>
>>
Re: EOModel importer testing
Posted by John Huss <jo...@gmail.com>.
A pull request is preferred now.
The biggest problem with the importer that I recall was that it was
completely unaware of prototypes (ERPrototypes) so that basically made it
worthless for me. Are you having that problem? Reverse-engineering from
the database itself can work well as an alternative if your names use
underscores.
John
On Wed, Aug 3, 2016 at 1:53 PM Musall Maik <ma...@selbstdenker.ag> wrote:
> Hi all,
>
> I've got a rather large project to migrate from EOF to Cayenne, and in
> order to eliminate the manual cleanup steps I'd have to do after each
> conversion attempt until I'm ready for the final run, I thought I could
> have a look and try to improve the EOModel importer instead of wasting time
> fiddling with my one project.
>
> To that end, what is the usual procedure to test changes made against the
> modeler? Can I run it from within Eclipse? Or do I need to mvn install
> every time I changed something? (Note that I'm new to both Cayenne and
> Maven.)
>
> How am I supposed to contribute the changes? Pull request against the
> github mirror? The website [1] suggest submitting a patch, but that feels
> so old-school, and the website still explains how to create a patch with
> subversion, so I guess that's no longer up to date anyway?
>
> Thanks
> Maik
>
> [1] https://cayenne.apache.org/submit-patch.html
>
>