Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1040591
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T15:14:35+00:00 2026-05-16T15:14:35+00:00

We are in a middle of an migration process of converting EJB2.1 entity beans

  • 0

We are in a middle of an migration process of converting EJB2.1 entity beans to EJB3 we have chosen Hibernate as JPA 1.0 provider in Weblogic.

We would like to disable auto. increment of entity version when persisting. Is it possible to turn of this feature? (as in property or persistence.xml?)

Do JPA 1.0 support pessimistic locking?

Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T15:14:36+00:00Added an answer on May 16, 2026 at 3:14 pm

    Hibernate uses the @Version annotation to denote the versioned field on your entity. By simply removing this annotation the increments to this field will be disabled.

    Pessimistic locking is supported by hibernate

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a migration that's breaking in the middle of a couple of schema
I have inherited a middle tier system with some multi-Threading issues. Two different threads,
I have a middle size query with 500.000 registers from an Oracle to an
I am in the middle of migrating from Linq2Sql to Entity Framework and I
I am in the middle of converting a listview example into a program that
We have a fairly robust system using NHibernate, we're in the middle of migrating
I am in the middle of committing. I have typed up my commit message
I'm in the middle of building a very large enterprise application. I have main
I'm in the middle of converting some code from C++/CLI to C#. One of
If I have two migration files: 20110414132423_insert_bulk_data.rb #1st 20111122105951_add_some_columns.rb #2nd and I run rake

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.