Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] Survey: Anybody using EclipseLink in Production?

Database: PostgreSQL
Exisiting Appliction: Yes
Migrated from: custom JDBC based DAO.
Stage: Production for ~6 mo.
Environment: J2SE RCP osgi application. (Thick Client)
Number of Entities: ~100
OSGi: yes
JPA Annotations: Yes, Yes, Yes!
Use Dali: Yes
Sequences: DB Driven
Use Expression framework: no
Use Unit of Work For Change Tracking: Yes
Caveats: Being a thick client we basically disable caching, so we are
unable to report in that area. However we can report it is possible to
bypass shared caches :)

Support from users: good via mailing list
Support from devs: good via mailing list. We've had tons of help from
developers on the list here, even though we don't use Oracle and are
doing somewhat unorthodox things.


On Wed, Sep 10, 2008 at 12:21 PM, Sebastien Tardif <stardif@xxxxxxxxxxxx> wrote:
> My organization is evaluating EclipseLink. One of the question raise
> during risk evaluation is if anybody already uses it and what was their
> experience including how fast it is compared to previous version:
> TopLink 9/10, TopLink Essential.
> To start the survey, I'm providing our setup:
> Number of application: 1
> Existing application: yes
> Migrated from: TopLink 10.x
> Stage: early evaluation, only smoke tested
> Application Server: WebSphere 6.1
> Hardware: Sun Unix, 4 boxes, 1 JVM each
> Database: Oracle 10
> Use ORM: Yes
> Use XML-Java support: Yes
> Number of mappings: 150
> Use SessionBroker: yes, with two children session, pointing to 2
> different DB schemas
> Number of ORM EclipseLink projects (XML files): 3
> Number of XML-Java projects: 3
> Change propagation between servers: No
> Invalidation propagation between servers: Yes
> Propagation using RMI or JMS: JMS
> Use OSGI: No
> Use JPA Mapping: No
> Use proprietary EclipseLink API: Yes
> Use JPA API: No
> Call stored procedure: Yes
> Use flush during UOW: No, but will
> Use conform in unit of work: Yes
> Use DB Sequence: Yes
> Evaluation so far:
> - Easy to migrate session, mapping, and Java code
> - WebSphere integration is not yet coded, so extraction of Oracle JDBC
> connection that is needed by different EclipseLink mechanisms is not
> working
> - JMS invalidation support is still not compatible with J2EE
> specification
> - SessionBroker is still broken
> - Some bugs not existing with TopLink 10.x have been introduced
> - Support on usage via users' forum is good
> - Support on bug via developers' forum is minimal
> - Realistic documentation of supported platform/setup is missing
> - We still not have numbers about performance
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx

Back to the top