On 06/05/2008, at 11:30 AM, JGL wrote:
Hi All,
I recently discovered Cayenne while searching for an alternative for
Hibernate.
I am very impressed with the easy & intuitive framework Cayenne
provides.
While porting my current Hibernate app to Cayenne, I did run into an
issue
which I'd l
Hi All,
I recently discovered Cayenne while searching for an alternative for
Hibernate.
I am very impressed with the easy & intuitive framework Cayenne provides.
While porting my current Hibernate app to Cayenne, I did run into an issue
which I'd like to seek your help:
In Hibernate, the M side o
Hi there,
great, thanks. Our application runs with the 10.x driver. Oracle has
probably changed some interfaces in the 11.x driver
Matthias
On 05/05/2008, at 4:54 PM, Andrus Adamchik wrote:
Never used the 11.x driver. Let me try running the unit tests with it.
Andrus
On May 5, 2008, at
You don't have to declare the throw clause if it's a RuntimeException.
The method signature doesn't have to change.
On 5/5/08, Scott Anderson <[EMAIL PROTECTED]> wrote:
> > I don't see
> > much benefit to providing a binary-compatible method API that does
> > nothing.
>
> ...
>
> > Another poss
> I don't see
> much benefit to providing a binary-compatible method API that does
> nothing.
...
> Another possibility is to @deprecate the method and have it
> unconditionally throw a RuntimeException telling the developer to
> rewrite using query cache options.
Adding a Throws clause to the met
I was looking through my old emails, and I realized that I still haven't
found a resolution to this. Andrus vaguely mentioned that there might be
a good reason why you aren't allowed to, but I wasn't able to find that
reason.
So, to recap, here's my scenario:
I am normalizing the schema for a req
Just to reiterate, I see no problem with axing it entirely. I don't
think we have to nicely deprecate everything since we're now in 3.0
and it's marked unstable.
However, we should make the need for change obvious. I don't see
much benefit to providing a binary-compatible method API that does
Andrus,
That fixed it. Thanks for the quick response!
Brian
--- Andrus Adamchik <[EMAIL PROTECTED]> wrote:
> I was looking for any clues in the code, nothing concrete... And I
> found it. The recent fix to CAY-785 deprecated and stopped calling
> "Configuration.getDataSourceFactory()" repla
Actually I was going to do the opposite, but since we've set the
backwards compatibility bar for ourselves pretty high in the past, I
guess I am persuaded to go with deprecated-but-don't-cripple approach.
I guess that means also putting a deprecation note in the Modeler next
to refresh chec
I'd like to second the opinion that deprecated still works (until
removed), but is discouraged from use. I believe that is what Andrus
intends, though, given previous API changes.
On Mon, May 5, 2008 at 4:02 PM, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
> I guess my problem is that to me @depr
On May 5, 2008, at 10:39 PM, Mike Kienenberger wrote:
To me, that sounded like you were going to change the behavior rather
than just mark the method as @deprecated.
I was planning to do both. Although we may decide to be gentle about
it and deprecate the method, but preserve the functional
I guess my problem is that to me @deprecate means "it still works like
it used to, but it won't work in a future version and it's time for
you to change your code", but that's not what's going to happen here.
That's why if we're not really @deprecating it but crippling it, then
I'd recommend remov
Maybe I'm simply misunderstanding what you meant by "actually ignoring
it in runtime".
To me, that sounded like you were going to change the behavior rather
than just mark the method as @deprecated.
On 5/5/08, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
> @deprecated is the way we always do it. Th
@deprecated is the way we always do it. That's sort of implied.
Andrus
On May 5, 2008, at 8:26 PM, Mike Kienenberger wrote:
I don't have any opinion on the actual method involved, but when you
remove it, don't have it silently ignore the setting. Either get rid
of it completely (so compilati
The performance of this may not work for your specific situation, but
my java web application allows for the possibility that some external
process may update the database like this:
I created a table: LAST_EXTERNAL_UPDATE with two fields:
ID
LAST_CHANGED
Any external process changes the LAST_CH
I don't have any opinion on the actual method involved, but when you
remove it, don't have it silently ignore the setting. Either get rid
of it completely (so compilation/runtime breaks) or have it continue
to function (@deprecated with BIG warnings in the logs).
I'd hate to be a developer who m
Andrus,
I don't think that there were to be problems, we actually are working with
click 1.4 and cayenne
3.0, but we are having trouble with the deserialization process.
I must aggregate that we aren't very experienced with java, and we would prefer
the framework as it
comes.
Thank you again
H
Any reason why you can't use Cayenne 3.0 with Click? (I know it is
tested with 2.0, but I'd imagine it will happily work with 3.0 as
well...or not?)
Andrus
On May 5, 2008, at 3:36 PM, Hans Poo wrote:
Hi,
I'm using click 1.4 with cayenne 2.04.
The whole problem is this: when i begun worki
Hi,
I'm using click 1.4 with cayenne 2.04.
The whole problem is this: when i begun working with click an cayenne, i
installed/copy the
libraries manually, and used cayenne 3.0.
Latter on, i wanted to use the standard click 1.4 pack (with cayenne 2.04
included), but i was
forced to keep cayenne
Umm, sorry you already said that you don't have doubly mapped class...
So what environment are you using for deployment? I am wondering if
there is some special ClassLoader setup involved.
Andrus
On May 5, 2008, at 11:28 AM, Andrus Adamchik wrote:
Hi Hans,
This may be a genuine error (i.e
for java-to-java invalidation I successfully used OSCache with
JGroups. For non-java apps that change the data there are a few options:
1. A private URL in a webapp that a script can access that would cause
cache invalidation
2. A timer local to the app that checks a special table in DB that
Hi Hans,
This may be a genuine error (i.e. you do have two entities that are
mapped to the same Java class). Although the fact that it goes away in
3.0 makes me wonder if there is a bug in 2.0.4 EntityResolver. In 3.0
it is much more robust to various cross-ClassLoader and arbitrary
namin
Hi,
I have an web application that serves html pages from a databases.
That database is manipulated from a perl program that runs from
within a proftpd ftp server. As a result, users can upload their
html pages via ftp and the web application displays them.
I want to cache the page queries in th
23 matches
Mail list logo
