everytime i edit everythink by hand - i'm working in time-critical business
sector and
if i have wake-up call at two a.m. that somethink goes wrong in night-job there
isn't time
to study what happen in "mega-giga-super-zoo" grafical tool that somethink has
been
broken. i have to study logs and in small amount of time there is need to
correct bug and
run job again. no problem with pure files (doesn't matter if .xml, .csv,...).
maybe to make opinion - my second main business language is assembler.
ok, i'm not so "productive" as if i used graphical tools but this disadvantage
is balanced
in production that in 99% of errors i can in minutes debug error and correct
it. has been
many times waked-up in night that "gui boys" can't find bug...
ok, i'm old-fashioned.
yes, looks like cayene is in some aspects better than hibernate.
On 23.12.2012 1:47, emeka okafor wrote:
About 4 or 5 years ago, when j2ee and spring were all the rage, I thought I was
a ninja because I would spend hours editing spring/beans/hibernate
configurations by hand, and even xslt...until I found a job where I did learn
WebObjects/EOF and it changed my brain forever. It s a shame that there are not
many jobs related to that technology and so one still has to do the jee stuff.
What I am trying to say is that, you did not even give the modeler a try. I
would be surprised if you would xml editing go back to xml after you have
learnt how to use it.
You will have a lot of fun with cayenne.
________________________________
From: Michael Jaruska <[email protected]>
To: [email protected]
Sent: Sunday, December 23, 2012 12:31 AM
Subject: Re: basic tutorial
hmm, i was in hope not to make spam but instead of (short) point to some notes
about using cayenne without modeler but just hand-editing xml files there was
rubbish
about xml and editing them by hand. i'm editing xml by hand for more than 10
years
without problems and there's more efective formats for machines than xml.
btw: in cayenne i'm beginner, hibernate, ibatis etc i'm using for years and
yes, i (and in fact all my colleagues) am editing xml's by hand.
from this point of view, programmers of modeler are programming in wrong way...
On 22.12.2012 15:55, Tony Giaccone wrote:
In fact I would argue that any system that requires you to edit xml by hand
is fundamentally broken (I"m looking at you JPA). XML is meant for machines
not humans, and if you develop an xml dialect to represent something you've
only started your work. Never make your users edit XML. Never.
On Fri, Dec 21, 2012 at 6:21 PM, John Huss <[email protected]> wrote:
This message should be on the user mailing list, not the dev list, so
please reply there.
Cayenne is not primarily intended to be used that way, so there is no
tutorial. It is possible to do, but there's not really a good reason to
for a beginner. Using the modeler prevents from having to know the whole
XML api - instead the screens may it fairly easily to figure out what you
need to do.
Anyway if you want to hand-code the XML you can create a mapping using the
modeler (or find an example) and then see how the XML looks, then follow
the same pattern. There is also a DTD somewhere I believe. But you should
really use the modeler, at least until you get a hang of the basics. Even
if you decide to skip the modeler later, start with it first.
On Fri, Dec 21, 2012 at 5:02 PM, Michael Jaruska
<[email protected]>wrote:
hi folks,
i'm searching for tutorial for using cayene without caynene modeler, i
need
something like "download this jar, write this bean, edit this xml in this
way
and this is how you can access objects from database".
i'm not fun of grafical/ide tools (writing this hope this won't lead into
spam), just like hand-make work.
is there tutorial with this aspect keeping in mind?
please be patient to my beginer question.
michael
