Send eclipselink-users mailing list submissions to
eclipselink-users@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
or, via email, send a message with subject or body 'help' to
eclipselink-users-request@xxxxxxxxxxx
You can reach the person managing the list at
eclipselink-users-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of eclipselink-users digest..."
Today's Topics:
1. Re: Notifications about external database changes
(Philipp Kursawe)
2. Cache Coordingation configuration (cmathrusse)
3. Specify MaxResultSize of "owning" Entity with
@QueryHint(LEFT_FETCH...) in NamedQuery + .setMaxResults() ???
(Mario Sandro Schwarz)
4. Re: Cache Coordingation configuration (Guy Pelletier)
5. Re: Specify MaxResultSize of "owning" Entity with
@QueryHint(LEFT_FETCH...) in NamedQuery + .setMaxResults() ???
(christopher delahunt)
6. Re: Cache Coordingation configuration (Prabaharan Vijayaratnam)
7. Re: Exception inserting into Sybase AsE TEXT field
(James Sutherland)
----------------------------------------------------------------------
Message: 1
Date: Tue, 09 Jun 2009 19:29:23 +0200
From: "Philipp Kursawe" <phil.kursawe@xxxxxxxxx>
Subject: Re: [eclipselink-users] Notifications about external database
changes
To: "EclipseLink User Discussions" <eclipselink-users@xxxxxxxxxxx>
Message-ID: <op.uu9piv0rjiieg5@donnymob>
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
On Tue, 09 Jun 2009 02:33:52 +0200, Sebastien Tardif
<stardif@xxxxxxxxxxxx> wrote:
A fast implementation compatible with caching is that your DB send to
your application a JMS invalidation message containing the table name +
PK modified, likely implemented using triggers. In Oracle DB, it's
relatively easy, because already supporting JMS. Then your application
can match entities by using the table name received.
How would I setup such JMS scenario? Which topics I would need to
subscribe to?
Thanks, for any help,
Phil
------------------------------
Message: 2
Date: Tue, 9 Jun 2009 13:40:55 -0700 (PDT)
From: cmathrusse <Christopher.Mathrusse@xxxxxxxxxx>
Subject: [eclipselink-users] Cache Coordingation configuration
To: eclipselink-users@xxxxxxxxxxx
Message-ID: <23950887.post@xxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
I'm using EclipseLink 1.1.1.v20090430-r4097 with Sybase ASE 15. I'm trying to
configure a Coordinated Cache using JMS. Currently I am using JPA
Annotations for all configuration but I have configured my caches in
persistence.xml. Looking through all the documentation it seems that the
recommended approach for configuring a Coordinated Cache is to use the
ExclipeLink Workbench. This seemed like a lot of lifting to get things to
work correctly but I've begun to venture down this path only to hit issues.
First, Ping SQL. The XML element gets generated as follows:
<toplink:ping-sql>
I think this is a bug as there should be no reference to toplink. (I would
imaging)
Next, when I deploy I get an exception pertaining to the 'server-platform'.
(sunas-9-platform) I looked at the schema for sessions-1.1 and could find no
server-platform defined for this type.
So at this point I guess my question is should I be using the Workbench or
should I be defining a SessionCustomizer to configure the Cache
Coordination?
Thanks...